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

69%

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

72%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 content is highly actionable with comprehensive executable examples and good conciseness, but its workflow clarity is held back by absent explicit validation feedback loops on destructive operations, and progressive disclosure suffers from all material being inlined in a single long file.

Suggestions

Add explicit validate→fix→retry steps inside the CI/CD deploy and rollback workflows (e.g., run smoke tests after staging deploy, gate production on passing checks, verify rollout status after 'kubectl rollout undo').

Move the per-language Dockerfiles and the full GitHub Actions pipeline into bundle reference files (e.g., references/dockerfiles.md, references/cicd.yml), keeping SKILL.md as an overview with one-level-deep pointers.

Trim the repeated 'Pros/Contras/Usar cuando' blocks or compress them into a single comparison table to reduce redundancy across deployment strategies.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence — code blocks and checklists are dense and useful — with only minor over-explanation such as 'Toda la configuración mediante variables de entorno — nunca en el código'.	4 / 5
Actionability	Fully executable, copy-paste-ready material across the common cases: multi-stage Dockerfiles for Node/Go/Django, a complete GitHub Actions pipeline, kubectl/vercel/railway rollback commands, TypeScript health checks, K8s probes, and zod env validation.	5 / 5
Workflow Clarity	Sequences exist (CI/CD stages, rollback, production checklist), but destructive/batch operations like DB migrations, 'kubectl rollout undo', and production deploys lack explicit validate→fix→retry feedback loops within the workflow, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	Section organization is decent, but a ~428-line SKILL.md inlines substantial material (three full Dockerfiles, a complete pipeline, multi-section checklists) that has no bundle files to split into; the simple-skill exception does not apply at this length.	3 / 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 is specific and uses natural trigger terms for a well-scoped deployment skill, but it omits an explicit 'Use when...' clause, which limits its completeness to the rubric's cap of 3.

Suggestions

Append an explicit 'Úsalo cuando…' clause naming concrete trigger scenarios (configurar pipelines, contenedorizar una app, preparar un lanzamiento a producción) to lift completeness toward 5.

Add a couple of natural synonyms/extensions users might say (e.g. 'despliegue continuo', 'release', '.yml pipelines') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — 'patrones de pipeline CI/CD', 'contenedorización Docker', 'health checks', 'estrategias de rollback', 'listas de verificación de preparación para producción' — with only minor generic phrasing around 'flujos de trabajo de despliegue'.	4 / 5
Completeness	The 'what' is clearly stated via a list of capabilities, but there is no explicit 'Use when...' or equivalent trigger clause — only an implied 'when' — which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Good coverage of natural terms users would say (despliegue, pipeline CI/CD, Docker, health checks, rollback, producción), but a few natural synonyms and variations are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a specific deployment/CI-CD niche with distinct triggers and minimal overlap risk with unrelated skills, though it could slightly overlap with adjacent DevOps skills.	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: 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.