CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deployment-pipeline-design

Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-organized overview with genuinely useful, executable troubleshooting content and real progressive disclosure to two substantive reference files. The main weakness is the absence of an explicit sequenced design workflow with validation checkpoints in the body — the pipeline sequence and pattern depth are delegated to the reference file — plus minor redundancy between the intro, Purpose section, and frontmatter description.

Suggestions

Add an explicit numbered design workflow in the body (e.g., gather inputs → select rollout strategy → define gates → configure health checks → define rollback triggers) with validation checkpoints between stages, so the sequence doesn't depend entirely on references/details.md.

Include one compact inline example of a core deliverable (e.g., a minimal canary AnalysisTemplate or gate threshold definition) so the primary design guidance is actionable without opening the reference file.

Trim the opening line and Purpose section, which restate the frontmatter description, and make the references/details.md pointer a markdown link with a brief contents summary to match the advanced-strategies.md pointer style.

DimensionReasoningScore

Conciseness

The body is mostly efficient — troubleshooting entries cover non-obvious gotchas (Argo inconclusiveLimit, Docker layer ordering, additive migrations) without teaching basics — but the intro line and Purpose section restate the frontmatter description ("Architecture patterns for multi-stage CI/CD pipelines with approval gates...", "balance speed with safety"), which is minor over-explanation that could be trimmed.

4 / 5

Actionability

Concrete, executable guidance is present: a complete Argo Rollouts AnalysisTemplate YAML, a Dockerfile layer-ordering fix, a migration undo-script convention, and an exact GitHub settings path ("Settings → Environments → production → Required reviewers"). It falls short of fully copy-paste-ready coverage because the skill's core deliverables (canary weights, gate thresholds, stage definitions) are described only abstractly in Input/Output with no inline example.

4 / 5

Workflow Clarity

The body presents a reference architecture (inputs, outputs, when-to-use, troubleshooting) rather than an explicit sequenced design workflow — the stage sequence lives only in references/details.md — and validation/verification is discussed (deep readiness checks, smoke tests, analysis failure conditions) but scattered rather than sequenced as checkpoints, matching 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The bundle structure is solid: a ~106-line overview pointing to two real, substantive references (details.md at 399 lines, advanced-strategies.md at 630 lines), one level deep, each signaled with content descriptions and read-when guidance ("Read that file when the navigation tier above is insufficient"). Minor gaps: the details.md pointer is inline code rather than a markdown link (inconsistent with the advanced-strategies.md pointer), and the Troubleshooting section carries worked-example depth that arguably belongs in the detail tier.

4 / 5

Total

15

/

20

Passed

Description

83%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 description: third-person voice, explicit what and when clauses, and multiple natural trigger phrases spanning design, implementation, and debugging scenarios. The only gaps are a few missing common synonyms (blue-green, rollback) and slightly abstract terms like "deployment orchestration".

DimensionReasoningScore

Specificity

"Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration" lists several concrete capabilities (approval gates, security checks, orchestration), but "deployment orchestration" and "security checks" are less concrete than a fully specific action list, matching the 'several specific actions; minor gaps' anchor rather than comprehensive coverage.

4 / 5

Completeness

Both parts are explicit: the what ("Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration") and the when ("Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies... or debugging failed deployment gates") with four concrete trigger scenarios, matching the anchor for clearly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "zero-downtime deployment pipelines", "canary rollout strategies", "multi-environment promotion workflows", "deployment gates", "CI/CD" — but common variations like blue-green, rolling deploy, and rollback are missing, fitting 'good keyword coverage; a few natural terms missing' rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The pipeline-design niche with rollout strategies and approval gates is clearly distinguishable, though it could overlap with closely related platform-implementation skills (the body itself lists github-actions-templates and gitlab-ci-patterns as neighbors), matching 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/cicd-automation/skills/deployment-pipeline-design/SKILL.md

Reviewed

Table of Contents

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.