deployment-pipeline-design

Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.

1.12x

Quality

—

Does it follow best practices?

Impact

91%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with concrete, executable pipeline code across multiple platforms. Its main weaknesses are missing validation checkpoints for destructive deployment workflows and broken progressive-disclosure references to non-existent bundle files, plus some verbosity in catalog-style sections.

Suggestions

Add explicit validation gates (e.g., 'Only promote to production after health checks pass') before production deploy and rollback steps to lift workflow_clarity.

Either create the referenced `references/pipeline-orchestration.md` and `assets/approval-gate-template.yml` files, or remove the dangling references, so progressive disclosure points to real content.

Trim the generic 'Pipeline Best Practices' and 'Key Pipeline Metrics' lists, which restate concepts Claude already knows, to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete code blocks throughout, but the ~360-line length and catalog-style 'Best Practices' and 'Key Pipeline Metrics' lists add content Claude largely already knows and could be trimmed.	2 / 3
Actionability	Provides fully executable, copy-paste-ready YAML (GitHub Actions, GitLab CI, Azure Pipelines, Kubernetes, Argo Rollouts) and bash commands with specific tools like trivy and kubectl rollouts.	3 / 3
Workflow Clarity	The standard pipeline flow and stage breakdown are well sequenced, but destructive production deploys and rollbacks lack explicit validation-then-proceed checkpoints; the automated-rollback health check exists but is not framed as a mandatory gate.	2 / 3
Progressive Disclosure	The body references `references/pipeline-orchestration.md` and `assets/approval-gate-template.yml`, but those directories and files do not exist, so the signaled references are broken and navigation is ineffective.	1 / 3
	Total	8 / 12 Passed

Description

77%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with a clear 'Use when' trigger clause and concrete named capabilities. It could be improved by adding more natural, user-spoken trigger variations and tightening distinctiveness from adjacent deployment skills.

Suggestions

Add natural user-spoken trigger terms like 'deploy,' 'release pipeline,' 'CD setup,' or 'set up deployments' alongside the technical phrasing.

Sharpen distinctiveness by narrowing the trigger scope so it is less likely to overlap with generic release-management or secrets-management skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—'multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration'—naming specific capabilities rather than vague language.	3 / 3
Completeness	Clearly states what it does (designs pipelines with approval gates, security checks, orchestration) and when to use it via an explicit 'Use when...' clause covering three scenarios.	3 / 3
Trigger Term Quality	Triggers like 'architecting deployment workflows,' 'setting up continuous delivery,' and 'implementing GitOps practices' are relevant but lean technical; missing common user variations such as 'deploy,' 'release pipeline,' or 'CD setup.'	2 / 3
Distinctiveness Conflict Risk	The CI/CD and GitOps niche is fairly distinct, but the broad trigger 'setting up continuous delivery' could overlap with related deployment or release-management skills.	2 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: abece4a

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.