deployment-patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

Quality

87%

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

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable, well-sequenced deployment reference with complete executable examples and clear pipeline gating, but it is a monolithic single file with no progressive disclosure to separate reference materials despite its length.

Suggestions

Move the per-language Dockerfiles and/or the full CI/CD YAML into reference files (e.g. references/dockerfiles.md, references/cicd.md) and link to them from a concise overview to improve progressive disclosure.

Replace the placeholder deploy step (currently just 'echo Deploying') with a concrete, validated deploy-and-verify snippet to strengthen the production workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is dense actionable reference material — complete Dockerfiles, pipeline YAML, probes, and checklists — with no conceptual padding explaining basics Claude already knows; not 2 because there is no extraneous explanation, justifiably broad for the topic.	3 / 3
Actionability	Provides fully executable, copy-paste-ready artifacts: multi-stage Dockerfiles for Node/Go/Python, a complete GitHub Actions workflow, TypeScript health checks, k8s probes, and a zod env schema.	3 / 3
Workflow Clarity	Pipeline stages are explicitly sequenced (lint → typecheck → tests → build → staging → smoke test → prod) with job gating (`needs:`) and validation via smoke tests plus rollback and production-readiness checklists.	3 / 3
Progressive Disclosure	No bundle files exist and the 420-line body keeps everything inline — three full Dockerfiles, the complete CI/CD YAML, and detailed checklists that could be split into one-level-deep references; well-sectioned but not split.	2 / 3
	Total	11 / 12 Passed

Description

82%

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 specific, third-person description that names a clear deployment/CI-CD niche and natural trigger terms, but it omits an explicit 'Use when...' trigger clause, capping completeness at 2.

Suggestions

Append an explicit trigger clause, e.g. 'Use when setting up CI/CD pipelines, containerizing apps with Docker, planning blue-green/canary deployments, or preparing a production release.'

Add common natural variations users might say (e.g. 'rollback', 'zero-downtime deploy', 'production readiness') to reinforce trigger_term_quality and reduce conflict risk.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities — 'Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly states what the skill covers but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Uses natural terms a user would say — 'CI/CD pipeline', 'Docker containerization', 'health checks', 'rollback', 'deployment' — with good coverage rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a distinct deployment/CI-CD niche with specific terminology unlikely to trigger for unrelated skills; not below 2 because the domain is clearly bounded, not above because there is no explicit trigger clause.	3 / 3
	Total	11 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: skills/deployment-patterns/SKILL.md
Commit: dfbf946

Reviewed: about 1 hour 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.