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

80%

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/devops/deployment-pipeline-orchestrator/skills/orchestrating-deployment-pipelines/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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-sequenced runbook with strong validation checkpoints and a rollback feedback loop, but it stops short of executable examples and ignores its own bundle. The bundled template, example config, and init script are directly relevant yet unreferenced, and the bundle READMEs advertise files that are missing.

Suggestions

Reference the existing bundle assets inline, e.g. "Start from `assets/pipeline_template.yaml`" and "See `assets/example_config.yaml` for a filled-in configuration", so the available detailed materials are actually reachable.

Add at least one copy-paste-ready artifact (a minimal Kubernetes canary manifest or a GitHub Actions/Argo Rollouts workflow snippet) so the concrete thresholds become executable rather than descriptive.

Fix the bundle READMEs so they list only files that exist (remove validate_config.py, deploy.sh, rollback.sh, sample_scripts/), or add the missing files, to keep navigation honest.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized into short lists, a compact error table, and examples; it assumes Claude's competence and never explains concepts Claude already knows (no "what is Kubernetes" padding), matching the anchor 3 "every token earns its place" bar.	3 / 3
Actionability	Guidance is concrete and specific (canary at 5-10% for 15 minutes, rollback if error rate exceeds 1% or P99 latency doubles, and executable commands like `kubectl logs` and `docker manifest inspect`), but there are no complete executable manifest/workflow examples and the body never references the bundled `pipeline_template.yaml`/`example_config.yaml` that would make it copy-paste ready, fitting anchor 2's "concrete guidance but incomplete."	2 / 3
Workflow Clarity	The 9-step sequence is clearly ordered with explicit validation checkpoints (pre-deployment checks, canary monitoring, post-deployment verification) and a real feedback loop (automatic rollback on threshold breach) plus an error-handling table for recovery, matching anchor 3; the destructive production-deploy context has the required validation, so no cap at 2 applies.	3 / 3
Progressive Disclosure	The body is organized into clear sections but never signals or references the existing bundle files (template, example config, init script), the `references/` directory contains only a stub README, and the `scripts/`/`assets/` READMEs list files that do not exist (validate_config.py, deploy.sh, rollback.sh, sample_scripts/), matching anchor 2's "references present but not clearly signaled" and poor bundle organization.	2 / 3
	Total	10 / 12 Passed

Description

82%Weight 40%Scale 1-3

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 answers both what and when with explicit, natural trigger phrases, but the capability statement is vague and repetitive ("automation... automation") and the grammar of the opening "Deploy use when" clause is broken. The niche is moderately clear but broad enough to risk overlap with adjacent devops skills.

Suggestions

Replace the abstract "deployment automation and orchestration with comprehensive guidance and automation" with concrete actions, e.g. "Generate Kubernetes manifests, configure canary/blue-green rollouts, and wire automated rollback into CI/CD pipelines."

Fix the broken opening to a clean third-person trigger clause, e.g. "Use when the user asks to deploy an application, create a CI/CD pipeline, or automate multi-stage rollouts."

Narrow the trigger terms to reduce conflict risk, adding distinctive phrases like "canary rollout", "blue-green deployment", or "Argo Rollouts" that separate this skill from generic devops/CI-CD skills.

Dimension	Reasoning	Score
Specificity	The description names the domain and action verbs ("deployment automation and orchestration") but these are abstract rather than the multiple concrete actions (e.g. generate manifests, configure canary, trigger rollback) that anchor 3 requires; it is still more concrete than the no-action anchor 1.	2 / 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), satisfying the anchor 3 bar of explicit triggers for both; the use-when clause is present so the cap-at-2 guideline does not apply.	3 / 3
Trigger Term Quality	It explicitly lists natural trigger phrases a user would say ("deploy application", "create pipeline", "automate deployment") alongside "deployment and CI/CD", giving good coverage of natural terms rather than the single bare keyword of anchor 2.	3 / 3
Distinctiveness Conflict Risk	The deployment/CI-CD domain is only somewhat specific and phrases like "deploy application" and "automate deployment" are broad enough to overlap with generic devops, Kubernetes, or CI/CD skills, matching anchor 2's "could still overlap with similar skills" rather than a clearly distinct niche.	2 / 3
	Total	10 / 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
Path: plugins/devops/deployment-pipeline-orchestrator/skills/orchestrating-deployment-pipelines/SKILL.md
Commit: c4eafaf

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