orchestrating-deployment-pipelines

Deploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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 lean, well-structured reference with a clear sequenced workflow and explicit validation/rollback feedback loops, but its main instructions stay at a planning level without executable code and it fails to point readers to the bundled scripts and asset templates.

Suggestions

Add concrete, executable commands or snippets to the Instructions (e.g. kubectl/argo rollouts commands) rather than leaving steps at 'Generate manifests' / 'Implement checks'.

Reference the bundle files explicitly from the body, e.g. 'See assets/pipeline_template.yaml for a starter manifest' and 'Run scripts/init_pipeline.py to scaffold a pipeline', so the bundled materials are one level deep and discoverable.

Reconcile the scripts/README (which lists validate_config.py, deploy.sh, rollback.sh as unchecked) with what actually ships, or note which are templates vs. implemented.

Dimension	Reasoning	Score
Conciseness	The body is lean and information-dense across well-scoped sections (Prerequisites, numbered Instructions, Error Handling table, Examples, Resources) without explaining concepts Claude already knows, and every section earns its place.	3 / 3
Actionability	Steps name specific tools and thresholds (Flagger, Argo Rollouts, '5-10% of traffic', 'error rate exceeds 1%') and the error table gives concrete commands, but the Instructions themselves stay at a planning level ('Generate deployment manifests', 'Implement pre-deployment checks') with no executable code or commands in the main flow.	2 / 3
Workflow Clarity	The 9-step sequence is clearly ordered with explicit validation checkpoints (pre-deployment checks, 15-minute canary monitoring, post-deployment verification) and an explicit feedback loop (rollback when error rate exceeds 1% or P99 latency doubles), matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	The body is organized into clear sections, but the provided bundle files (scripts/init_pipeline.py, assets/pipeline_template.yaml, assets/example_config.yaml) are never referenced or signaled from the body, and the 'Resources' section only lists external URLs, so navigation to bundled material is missing.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 covers both what the skill does and when to use it with explicit trigger phrases, but is weakened by broken grammar, redundant padding, second-person voice, and limited trigger variation coverage.

Suggestions

Rewrite in third person and fix the broken opener, e.g. 'Deploys and orchestrates multi-stage CI/CD pipelines. Use when deploying applications, creating deployment pipelines, or automating CI/CD rollouts.'

Remove redundant padding ('comprehensive guidance and automation') and add more natural trigger variations such as 'roll out', 'release', 'set up CI/CD', and 'deploy to staging/production'.

Sharpen the 'what' with concrete actions (build, test, approve, promote, canary, rollback) rather than abstract 'automation and orchestration'.

Dimension	Reasoning	Score
Specificity	The description names the domain and a few action phrases ('deploy application', 'create pipeline', 'automate deployment') but pads them with redundant vagueness ('comprehensive guidance and automation'); the second-person voice ('you need to work with') triggers the -1 specificity penalty, dropping it from a base of 2 to 1.	1 / 3
Completeness	It explicitly answers both what ('deployment automation and orchestration') and when ('Use when you need to work with deployment and CI/CD' plus an explicit 'Trigger with phrases like...' clause), matching the both-what-and-when-with-explicit-triggers anchor.	3 / 3
Trigger Term Quality	It lists a few natural phrases ('deploy application', 'create pipeline', 'automate deployment', 'deployment and CI/CD') but misses common variations users would say ('roll out', 'release', 'deploy to staging/prod', 'set up CI/CD'), so coverage is incomplete.	2 / 3
Distinctiveness Conflict Risk	Deployment/CI/CD orchestration is a distinct niche, but triggers like 'deploy application' and 'create pipeline' are generic enough to overlap with other DevOps skills, so it is somewhat specific but not conflict-free.	2 / 3
	Total	8 / 12 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

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