deployment-procedures

Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

Quality

66%

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 ./.agents/skills/deployment-procedures/SKILL.md

Quality

Content

66%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 skill body is a well-structured, token-efficient set of decision trees, tables, and a clear phased deployment workflow with rollback triggers. Its main weakness is actionability: it teaches principles and lists commands rather than giving fully executable, copy-paste procedures.

Suggestions

Add at least one concrete, copy-paste-ready deployment example per platform family (e.g. an actual `vercel --prod` or `kubectl set image ... && kubectl rollout status`) rather than only naming the method.

Make the 5-phase workflow's validation gates explicit steps (e.g. 'Verify: curl health endpoint, expect 200; else rollback') instead of table-row principles.

Consider a short references/ file for per-platform runbooks so the main SKILL.md stays a lean overview while detailed commands live one level deeper.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and compact decision trees that assume Claude's intelligence, with only minor restatement (e.g. the repeated 'THINK, not scripts' framing) that could be trimmed.	4 / 5
Actionability	Guidance is concrete in structure (named platforms, named commands like 'kubectl rollout undo') but largely framed as principles and tables rather than executable, copy-paste-ready procedures, matching the pseudocode-level anchor.	3 / 5
Workflow Clarity	The 5-phase PREPARE/BACKUP/DEPLOY/VERIFY/CONFIRM-or-ROLLBACK sequence is clearly ordered with explicit checkpoints and a rollback trigger, though some validation gates are stated as principles rather than enforced steps.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed numbered sections with no bundle files to over-inline; it stops short of 5 only because there are no one-level-deep references to detailed materials for platform-specific procedures.	4 / 5
	Total	15 / 20 Passed

Description

66%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 states what the skill does and provides an explicit use-when trigger, with natural deployment-related keywords. It is solid but not fully comprehensive in concrete actions and trigger synonyms.

Suggestions

List more specific concrete actions (e.g. 'zero-downtime rollouts, canary releases, blue-green deploys, health-check verification') to lift specificity.

Add common synonyms and concrete tool/extension triggers (e.g. 'Vercel/Netlify redeploy', 'kubectl rollout undo', 'PM2 reload') to broaden trigger coverage.

Tighten the when_to_use clause to cover 'debugging a failed deploy' or 'planning a deployment strategy' in addition to CI/CD setup.

Dimension	Reasoning	Score
Specificity	Names the domain and a few concrete actions ('Safe deployment workflows, rollback strategies, and verification'), but the actions are generic categories rather than the multiple specific concrete actions a 5 requires.	3 / 5
Completeness	The 'what' is clear (deployment principles and decision-making) and an explicit 'when_to_use' trigger clause is present; the 'when' is concrete but slightly narrow, so it stops short of the fully comprehensive 5.	4 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('deploying to production', 'rollback strategies', 'CI/CD pipelines'), though it misses common synonyms and concrete tool or extension names.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (production deployment / rollback / CI-CD) with distinct triggers, with only minor overlap risk against general ops or CI skills.	4 / 5
	Total	15 / 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
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: vudovn/ag-kit
Path: .agents/skills/deployment-procedures/SKILL.md
Commit: 211561c

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