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

70%

Does it follow best practices?

Impact

91%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/cicd-automation/skills/deployment-pipeline-design/SKILL.md

The canonical home for this skill is deployment-pipeline-design in wshobson/agents

Quality

Content

55%Weight 40%Scale 1-5

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

The skill is rich with executable, concrete examples and a clear pipeline sequence, but it over-inlines material that belongs in referenced bundle files, cites bundle files that are missing, and lacks explicit validate/fix/retry feedback loops for its destructive deployment operations.

Suggestions

Create the referenced bundle files (references/pipeline-orchestration.md, assets/approval-gate-template.yml) or remove the dangling references, and move the large inline pipeline YAML and per-strategy examples into them so SKILL.md stays a lean overview.

Add explicit validation checkpoints with feedback loops to destructive workflows, e.g. after production deploy run health checks and on failure automatically rollback then alert (a concrete 'validate -> rollback -> notify' sequence).

Trim the general-knowledge 'Best Practices' list and 'Characteristics' bullets to only the non-obvious, skill-specific guidance to reduce token load.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with code blocks doing the heavy lifting, but the 'Best Practices' list, characteristics bullets, and the full inline multi-stage pipeline example restate knowledge Claude already has; the body could be trimmed to essentials without losing value.	3 / 5
Actionability	Provides mostly executable, concrete YAML/bash snippets across approval gates, deployment strategies, rollback, and orchestration, with only minor gaps (e.g. placeholder deploy commands and unspecified secrets setup).	4 / 5
Workflow Clarity	The pipeline stages are clearly sequenced and rollback/health-check checkpoints appear, but destructive operations (production deploys, rollbacks, blue-green switches) lack an explicit validate->fix->retry feedback loop; per the rubric this caps the score at 3.	3 / 5
Progressive Disclosure	Although the body references two bundle paths ('references/pipeline-orchestration.md', 'assets/approval-gate-template.yml'), those bundle directories do not exist, and large reference-grade material (full pipeline YAML, all strategy examples) is inlined in SKILL.md rather than split out.	2 / 5
	Total	12 / 20 Passed

Description

85%Weight 40%Scale 1-5

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, well-formed description that clearly states concrete capabilities and provides explicit 'Use when' trigger guidance in third-person voice. It would benefit from a few more natural synonyms (CI/CD, deploy, release) and slightly tighter distinctiveness from sibling CI-implementation skills.

Suggestions

Add common synonyms and file/extension cues to trigger terms, e.g. 'CI/CD pipelines, deploys, releases, .github/workflows or .gitlab-ci.yml files'.

Sharpen distinctiveness by framing it as architecture/design only and explicitly deferring implementation to sibling skills (e.g. 'Use github-actions-templates for implementation details').

Replace the slightly abstract 'deployment orchestration' with a more concrete action like 'coordinate multi-environment deploys and rollbacks'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('approval gates, security checks, deployment orchestration') covering the CI/CD domain, though deployment orchestration is somewhat abstract, leaving minor coverage gaps compared to a comprehensive action list.	4 / 5
Completeness	Clearly answers 'what' ('Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration') and 'when' with an explicit 'Use when...' clause listing three concrete trigger scenarios.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('architecting deployment workflows', 'setting up continuous delivery', 'implementing GitOps practices') with good keyword coverage, but misses common synonyms like 'CI/CD pipeline', 'deploy', or 'release management'.	4 / 5
Distinctiveness Conflict Risk	The GitOps and approval-gate framing carves a fairly distinct niche, but it could still overlap with related implementation skills like github-actions-templates or gitlab-ci-patterns for pipeline-setup requests.	4 / 5
	Total	17 / 20 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
Path: tests/ext_conformance/artifacts/agents-wshobson/cicd-automation/skills/deployment-pipeline-design/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours 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.