Name: deployment-pipeline-design
Rating: 54.400000000000006 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

deployment-pipeline-design

Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/deployment-pipeline-design/SKILL.md

The canonical home for this skill is deployment-pipeline-design in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

63%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 body is a strong, concrete catalog of CI/CD patterns with executable code and a sensible stage sequence including verification and rollback. Its main weaknesses are generic boilerplate instructions, heavily inlined examples that should be split into reference files, and broken/inconsistent file references.

Suggestions

Remove the generic 'Instructions' and 'Do not use this skill when' boilerplate that does not add deployment-specific guidance.

Split the large pattern code blocks into the referenced bundle files (e.g., references/pipeline-orchestration.md, assets/approval-gate-template.yml) and actually ship those files, fixing the 'resources/' vs 'references/' inconsistency.

Add an explicit validation/verification checkpoint step (e.g., 'kubectl rollout status' + health check) as a named workflow step rather than only as an example block.

Dimension	Reasoning	Score
Conciseness	The bulk is lean, executable code, but generic boilerplate like 'Clarify goals, constraints, and required inputs / Apply relevant best practices and validate outcomes' and the vacuous 'Do not use this skill when' bullets restate what Claude already knows and could be trimmed.	3 / 5
Actionability	Provides multiple concrete, largely executable examples (GitHub Actions, GitLab CI, Azure Pipelines, Kubernetes manifests, Argo Rollouts, Python feature flags, bash rollback), with only minor gaps such as placeholder '# Deployment commands' and example URLs.	4 / 5
Workflow Clarity	The Detailed Stage Breakdown gives a clear sequence (Source -> Build -> Test -> Staging -> Approval -> Production -> Verification -> Rollback) with validation/rollback checkpoints present, though it is presented as a pattern catalog rather than one enforced procedural workflow.	4 / 5
Progressive Disclosure	Section headers provide reasonable structure, but ~365 lines of inlined pattern examples belong in separate files, and the cited references are inconsistent ('resources/' vs 'references/') and point to files that do not exist in the bundle, so references are not reliably signaled.	3 / 5
	Total	14 / 20 Passed

Description

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

The description clearly identifies the domain and a couple of concrete facets, but it reads as a topic statement rather than a capability list and omits any explicit trigger guidance. Adding a 'Use when...' clause and concrete action verbs would raise specificity and completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when designing CI/CD pipelines, configuring approval gates, or choosing deployment strategies').

Replace the abstract 'Architecture patterns for' framing with concrete action verbs (e.g., 'Designs, sequences, and validates multi-stage CI/CD pipelines...').

Include common synonyms and tool-specific terms (GitHub Actions, GitLab CI, Argo Rollouts) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('multi-stage CI/CD pipelines') plus a couple of concrete facets ('approval gates', 'deployment strategies'), but 'Architecture patterns' is abstract rather than a list of concrete actions, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It states clearly what the skill covers ('Architecture patterns for multi-stage CI/CD pipelines...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.	3 / 5
Trigger Term Quality	Includes several natural terms a DevOps user would say ('CI/CD pipelines', 'approval gates', 'deployment strategies', 'multi-stage'), giving good keyword coverage, though common synonyms and file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	The niche (CI/CD pipeline design with approval gates and deployment strategies) is fairly distinct with minimal conflict risk, though it could overlap slightly with closely related skills like github-actions-templates.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/deployment-pipeline-design/SKILL.md
Commit: 57c135b

Reviewed: 3 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.