CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

An actionable, token-efficient overview with executable examples and clean progressive disclosure to real reference files. Its main gap is missing explicit validation feedback loops for destructive or batch operations like database migrations.

Suggestions

Add an explicit validate→fix→retry checkpoint sequence for destructive operations such as database migrations (e.g., verify backward-compatibility, run undo script, re-verify) to lift workflow clarity.

Turn the canary promotion troubleshooting entry into a numbered diagnosis workflow with a validation step (confirm AnalysisTemplate returns data, check inconclusiveLimit, re-run) rather than a prose explanation.

Provide a short end-to-end pipeline design workflow (define inputs → choose strategy → set gates → define rollback → validate) so the multi-step process has an explicit ordered checklist.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence and adds domain-specific value Claude won't reliably hold (Argo inconclusiveLimit, GitHub environment protection settings, layer-cache ordering), with little padding explaining basics.

3 / 3

Actionability

Provides fully executable, copy-paste-ready snippets — Argo Rollouts YAML with inconclusiveLimit, a reordered Dockerfile, and versioned migration undo scripts — plus concrete UI paths.

3 / 3

Workflow Clarity

Framing via Input/Output and When-to-Use plus diagnosis-to-fix troubleshooting entries is clear, but destructive operations like migrations and canary promotion lack explicit validate→fix→retry feedback checkpoints, capping clarity at 2.

2 / 3

Progressive Disclosure

The body is a well-organized overview that signals one-level-deep references to real files (references/details.md and references/advanced-strategies.md) with brief content descriptions, splitting detail appropriately.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that covers concrete capabilities, natural trigger terms, and an explicit 'Use when' clause. It is concise, distinct, and free of fluff or over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete actions including 'approval gates, security checks, and deployment orchestration' plus canary rollout, multi-environment promotion, and debugging failed gates, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers both what ('Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration') and when via an explicit 'Use this skill when...' clause with several triggers.

3 / 3

Trigger Term Quality

Includes natural phrases users would say such as 'zero-downtime deployment pipelines', 'canary rollout strategies', and 'CI/CD', giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear CI/CD deployment-pipeline niche with distinct triggers (canary, promotion workflows, failed gates), making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.