deployment-patterns

Flujos de trabajo de despliegue, patrones de pipeline CI/CD, contenedorización Docker, health checks, estrategias de rollback y listas de verificación de preparación para producción de aplicaciones web.

Quality

65%

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 ./docs/es/skills/deployment-patterns/SKILL.md

Quality

Content

65%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 strong, highly actionable reference with minimal fluff: concrete Dockerfiles, CI pipelines, probes, and readiness checklists dominate. Its weaknesses are organizational and process-related — everything is inlined in one long file, and deployment/rollback flows lack explicit validation checkpoints and error-recovery loops.

Suggestions

Move the per-stack Dockerfiles and the full GitHub Actions pipeline into reference files (e.g. references/dockerfiles.md, references/ci-pipeline.md), keeping only the pattern and a pointer in SKILL.md.

Add an explicit ordered deployment workflow with validation gates (e.g. deploy to staging → run smoke tests → only on green, promote to production → verify health endpoint, else rollback), including an error-recovery loop.

Trim the ASCII diagrams for rolling/blue-green/canary — Claude already knows these strategies — and keep only the pros/cons/'usar cuando' decision guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and code/checklist-driven with almost no padded prose, matching the 'efficient; minor instances of over-explanation' anchor. The ASCII diagrams for rolling/blue-green/canary re-explain deployment concepts Claude already knows and could be trimmed, keeping it below the anchor-5 'every token earns its place' bar.	4 / 5
Actionability	Mostly executable, copy-paste-ready guidance: three complete Dockerfiles, a full GitHub Actions pipeline, K8s probe YAML, zod env validation, and concrete rollback commands. Minor gaps keep it at anchor 4: the health-check TypeScript references undefined 'db', 'checkRedis', 'checkExternalApi' and the 'HealthCheck' type, and the deploy step is a platform placeholder.	4 / 5
Workflow Clarity	Sequencing is present (pipeline stages 'lint → ... → staging → smoke tests → producción' plus pre-deploy checklists), but there are no explicit validation checkpoints or error-recovery loops guiding an actual deployment or rollback. Since deployment/rollback are risky operations without validate-then-proceed guidance, the anchor-3 'checkpoints missing or implicit' fit is better than anchor 4.	3 / 5
Progressive Disclosure	Sections are clearly headed and easy to navigate ('## Estrategias de Despliegue', '## Docker', '## Pipeline CI/CD'), but the ~420-line body inlines content that clearly belongs in separate reference files — three full per-stack Dockerfiles and a complete CI pipeline YAML — with no bundle files at all. This matches the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	14 / 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.

A solid, specific description that names the domain and its concrete sub-areas in third-person voice without padding. Its main weakness is the complete absence of a 'Use when...' trigger clause, which caps completeness and slightly weakens its usefulness for skill triggering.

Suggestions

Append an explicit trigger clause, e.g. 'Usar cuando se configuran pipelines de CI/CD, se contenedorizan aplicaciones, se planifica un despliegue a producción o se prepara un rollback.'

Convert topic nouns into third-person action verbs ('Configura pipelines de CI/CD, contenedoriza aplicaciones con Docker, implementa health checks') to strengthen specificity.

Add common trigger synonyms such as 'release'/'lanzamiento', 'Kubernetes'/'k8s' and 'preparación para producción'/'production readiness' for broader natural-term coverage.

Dimension	Reasoning	Score
Specificity	Lists six concrete areas ('patrones de pipeline CI/CD', 'contenedorización Docker', 'estrategias de rollback', 'listas de verificación de preparación para producción') but as topic nouns without action verbs, falling short of the anchor-5 'multiple specific concrete actions' example. It is clearly above anchor 3, which expects only 1-2 concrete actions.	4 / 5
Completeness	The 'what' is clear and comprehensive, but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3, which is exactly the anchor for 'clear what, when missing'.	3 / 5
Trigger Term Quality	Good natural keyword coverage users would actually say: 'despliegue', 'CI/CD', 'Docker', 'health checks', 'rollback', 'producción'. A few natural terms are missing ('release'/'lanzamiento', 'Kubernetes'/'k8s', 'pipeline'), placing it at anchor 4 rather than the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The deployment/production-readiness niche is coherent with distinct triggers (Docker, CI/CD, rollback, health checks), so it is mostly distinguishable. Minor overlap risk remains with closely related skills such as a dedicated Docker or CI skill, matching anchor 4 rather than the minimal-conflict anchor 5.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/es/skills/deployment-patterns/SKILL.md
Commit: c70874f

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.