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

92%

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

85%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 body is highly actionable with a well-sequenced, validated multi-phase workflow. Its main weakness is structure: at ~265 lines with detailed troubleshooting inlined and no bundled reference files, it underuses progressive disclosure.

Suggestions

Move the CI Parity table (Fase 3b) and the E2E smoke troubleshooting list into bundled reference files (e.g. references/ci-parity.md, references/e2e-troubleshooting.md) and link to them one level deep, keeping SKILL.md as a pipeline overview.

Relocate time-sensitive specifics (the '2026-04-27' date reference and the 'Co-Authored-By: Claude Opus 4.6 (1M context)' line) into a 'Historical context / old patterns' section so they do not age the skill or pad the main flow.

Consolidate the duplicated reporting templates (the reportar blockquotes in Fases 1 and 5 and the final summary table) into a single shared report format to reduce repetition.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and project-specific (CI-parity table, error protocol, safety rules earn their tokens), but duplicated reporting templates and a time-sensitive date ('2026-04-27') outside a deprecated section could be trimmed.	4 / 5
Actionability	Copy-paste-ready commands throughout (git/gh, 'npx playwright test --project=smoke', 'bash scripts/ci-parity.sh') plus specific failure-mode fixes covering the common cases.	5 / 5
Workflow Clarity	Phases 1-6 are clearly sequenced with explicit validation checkpoints ('NO pushear todavía', blockers 3a/3b), feedback loops (error-correction protocol, max 3 iterations), and a safety checklist.	5 / 5
Progressive Disclosure	A single ~265-line self-contained file with no bundled reference files; detailed CI-parity and E2E troubleshooting content that could be split into references is inlined.	3 / 5
	Total	17 / 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 strong: it concisely states the pipeline's concrete actions and gives explicit, natural trigger phrases in both Spanish and English. Both the 'what' and 'when' are clearly answered with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('merge development to main, run /test-all fixing all errors, commit, push to trigger GitHub Actions, and monitor the workflow until deployment completes') with comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (full production deployment pipeline with concrete actions) and 'when' ('Use when the user says...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides exact natural phrases users would say across two languages ('pase a producción', 'hagamos un pase', 'deploy to production', 'pasamos a prod', 'subamos a producción', 'vamos a producción'), including synonyms.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (production deploy pipeline) with distinct Spanish/English triggers and minimal overlap risk with other skills.	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/ap_sales_agent
Path: .claude/skills/pase-produccion/SKILL.md
Commit: d31f7bc

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