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.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/deployment-pipeline-design/SKILL.md

Quality

Content

71%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 highly actionable, code-rich skill body with clear pipeline sequencing and a rollback feedback loop. Its main weaknesses are generic boilerplate sections that waste tokens and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Remove or replace the generic 'Instructions' and 'Purpose' sections and the filler 'Do not use this skill when' bullets with domain-specific guidance, since they restate the description and add no pipeline-specific value.

Split the large inline examples (full multi-stage pipeline, per-deployment-strategy manifests) into reference files under references/ and link to them from a concise overview, enabling progressive disclosure.

Tighten the 'Characteristics' bullet lists under each deployment strategy to the one or two decision-relevant tradeoffs rather than restating well-known properties.

Dimension	Reasoning	Score
Conciseness	Code examples are lean, but generic boilerplate sections ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices', the Purpose restatement, and the filler 'Do not use this skill when' bullets) pad the file with content Claude already knows and could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready executable examples across GitHub Actions, GitLab CI, Azure Pipelines, Kubernetes, Argo Rollouts, and a full end-to-end production pipeline, covering the common deployment cases concretely.	5 / 5
Workflow Clarity	The pipeline stage flow and 9-step breakdown give a clear sequence, and the automated-rollback example includes a health-check loop with `if: failure()` rollback as a validation checkpoint; only minor validation gaps remain in the generic Instructions section.	4 / 5
Progressive Disclosure	The file is well-sectioned but ~360 lines are monolithically inlined with no bundle references — the full multi-stage pipeline example and per-strategy manifests are content that could live in separate reference files but instead sit inline.	3 / 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, third-person description that clearly states capabilities and explicit use-when triggers with good natural keywords. It is held back only by slightly abstract phrasing in one capability and minor overlap with sibling implementation skills.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete capability areas — 'approval gates, security checks, and deployment orchestration' — but 'deployment orchestration' stays somewhat abstract, leaving minor coverage gaps rather than full enumeration.	4 / 5
Completeness	Explicitly answers both what ('Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration') and when ('Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural trigger coverage with 'architecting deployment workflows', 'setting up continuous delivery', and 'implementing GitOps practices', though a few common synonyms (e.g. 'CI/CD pipeline', 'release automation') are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear architecture/design niche distinct from implementation-template skills, but the related skills it names (github-actions-templates, gitlab-ci-patterns) create minor overlap risk on the implementation boundary.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/deployment-pipeline-design/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.