pase-produccion

Full production deployment pipeline: merge development to main, run /test-all fixing all errors, commit, push to trigger GitHub Actions, and monitor the workflow until deployment completes. Use when the user says "pase a producción", "hagamos un pase", "deploy to production", "pasamos a prod", "subamos a producción", or "vamos a producción".

Quality

94%

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

Quality

Content

88%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, well-sequenced deployment runbook with strong validation gates and feedback loops. Its main weaknesses are minor time-sensitive tokens that hurt conciseness and a monolithic structure that could benefit from splitting detailed reference material into bundle files.

Suggestions

Move the '2026-04-27' historical failure context and any model-version stamp in the commit template into a deprecated/old-patterns note or remove them to improve conciseness.

Extract the CI-parity failure table and the E2E smoke troubleshooting catalog into separate reference files (e.g., references/ci-parity-failures.md, references/e2e-troubleshooting.md) and link them from the body.

Tighten the Fase 3 rationale prose ('Por qué este gate es no-negociable') to a one-line pointer to the reference, keeping only the actionable gate instructions inline.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven assuming Claude's competence, but embeds minor time-sensitive details (the '2026-04-27' failure date and a 'Claude Opus 4.6' model version in the commit template) outside any deprecated/old-patterns section, which could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready bash and gh commands at every phase (git merge, npx playwright test, gh run view, ci-parity.sh) covering the common deploy cases fully.	5 / 5
Workflow Clarity	A clear six-phase sequence with explicit BLOCKER validation gates (3a/3b), iteration caps ('Máximo 3 iteraciones'), feedback loops (error -> fix -> re-run), and a safety-rules checklist — strong validation for a destructive production operation.	5 / 5
Progressive Disclosure	Well-organized into clearly headed phases with no nested or broken references, but no bundle files exist and some inlined material (the CI-parity failure table and E2E troubleshooting catalog) could be split into reference files.	4 / 5
	Total	18 / 20 Passed

Description

100%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, complete, and rich with natural trigger phrases in third-person voice, hitting the top anchor on every dimension. It clearly communicates both the capability and the exact conditions for invocation.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ('merge development to main, run /test-all fixing all errors, commit, push to trigger GitHub Actions, and monitor the workflow'), giving comprehensive coverage of the pipeline.	5 / 5
Completeness	Explicitly answers both what (full production deployment pipeline with concrete steps) and when ('Use when the user says...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides six natural user phrases including synonyms ('pase a producción', 'hagamos un pase', 'deploy to production', 'pasamos a prod', 'subamos a producción', 'vamos a producción'), matching the comprehensive-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear production-deployment niche with project-specific triggers, making conflict with other skills minimal.	5 / 5
	Total	20 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: alpacapurpura/luana-method
Path: claude/skills/pase-produccion/SKILL.md
Commit: caa08df

Reviewed: ~21 hours 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.