deployment-patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

78%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 reference skill with executable Dockerfiles, CI/CD pipelines, probes, and checklists, organized under clear headers. Its main weaknesses are repetitive inline code examples and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Move the per-language Dockerfiles (Node/Go/Python) into separate reference files under references/ and keep one representative example plus a pointer in SKILL.md to reduce repetition and token cost.

Extract the full GitHub Actions workflow and Kubernetes probe YAML into a references/ file, leaving a concise pipeline-stages summary and a clearly signaled link inline.

Add an explicit validate→fix→retry feedback loop for the deployment/rollback workflow (e.g., deploy staging → run smoke tests → if failures, roll back and re-investigate) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Prose and checklists are lean and assume competence, but three near-identical full multi-stage Dockerfiles (Node, Go, Python) plus ASCII rollout diagrams add repetition that could be trimmed, placing it just below the lean/efficient top anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready artifacts — complete multi-stage Dockerfiles, a GitHub Actions workflow, Kubernetes probes, TypeScript health-check code, zod env validation, and rollback commands — covering the common deployment cases.	5 / 5
Workflow Clarity	Pipeline stages are clearly sequenced with a smoke-test checkpoint between staging and production, and the production-readiness and rollback checklists act as validation; however there is no explicit validate→fix→retry feedback loop for the deployment process itself.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a 430-line monolithic SKILL.md; content that could live in separate reference files (per-language Dockerfiles, the full CI/CD YAML) is inlined, so structure is present but content that should be split is not separated.	3 / 5
	Total	16 / 20 Passed

Description

92%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 a comprehensive set of deployment capabilities and provides an explicit 'Use when' trigger clause. The only gap is slightly incomplete coverage of natural trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists' — covering the deployment domain comprehensively, matching the anchor for several specific concrete actions.	5 / 5
Completeness	Explicitly states both what it does (the capability list) and when to use it ('Use when setting up deployment infrastructure or planning releases') with concrete trigger phrases, satisfying the top anchor.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('CI/CD', 'Docker', 'health checks', 'rollback', 'deployment infrastructure', 'planning releases') but omits common variations like 'deploy my app', 'ship to production', or 'Kubernetes/k8s', so it is good but not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear deployment/CI-CD niche scoped to web applications with distinct triggers, giving it minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/deployment-patterns/SKILL.md
Commit: d8409a4

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.