uinaf/gh-release-pipeline
Set up or align a GitHub Actions release pipeline for a versioned package, library, CLI, or marketplace action. Use when standardizing repos around the verify-then-release shape: push to main → guardrails → semantic-release tags + publishes → version-bump commit back to main with [skip ci].
99
100%
Does it follow best practices?
Impact
98%
1.55xAverage score across 4 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates what the skill does, when to use it, and how it differs from a closely related skill. It uses concrete, natural trigger terms and describes a specific workflow pattern in enough detail for accurate skill selection. The explicit contrast with `gh-deploy-pipeline` is a strong distinguishing feature.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: setting up GitHub Actions release pipeline, verify-then-release shape, semantic-release tags + publishes, version-bump commit with [skip ci], publishing versioned artifacts to a registry. Very detailed about the workflow shape. | 3 / 3 |
Completeness | Clearly answers both what ('Set up or align a GitHub Actions release pipeline for a versioned package, library, CLI, or marketplace action') and when ('Use when standardizing repos around the verify-then-release shape'). Also explicitly distinguishes from a related skill (`gh-deploy-pipeline`) with a clear boundary: 'use for publishing versioned artifacts to a registry, not deploying a running service.' | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms: 'GitHub Actions', 'release pipeline', 'versioned package', 'library', 'CLI', 'marketplace action', 'semantic-release', 'registry', 'publishing', '[skip ci]'. These are terms users would naturally use when asking about CI/CD release workflows. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit differentiation from the companion `gh-deploy-pipeline` skill. The focus on 'versioned artifacts to a registry' vs 'deploying a running service' creates a clear boundary. The specific workflow shape (semantic-release, version-bump commit) further narrows the niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently communicates a complex CI/CD pipeline pattern. It balances brevity with completeness — providing enough inline config to anchor understanding while delegating target-specific details to well-signaled reference files. The guardrails section is particularly strong, calling out the most dangerous failure modes (infinite retrigger, dual pipelines, weakened gates) with clear prohibitions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No explanation of what GitHub Actions or semantic-release is — it jumps straight into the pipeline shape, workflow steps, and concrete config. The ASCII diagram is an efficient way to convey the architecture. | 3 / 3 |
Actionability | Provides executable YAML and JSON config snippets, specific environment variable names, concrete commit message formats, and a clear 10-step workflow with specific file paths and commands. The guidance is copy-paste ready where it matters and delegates target-specific details to reference files. | 3 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced with explicit validation in step 9 (end-to-end validation confirming tag, release, artifact, and bump commit) and a troubleshooting fallback in step 10. The guardrails section adds important constraints about infinite loop prevention and gate integrity. The feedback loop of 'watch → confirm → cross-check troubleshooting' is well-defined. | 3 / 3 |
Progressive Disclosure | Excellent structure: concise overview with pipeline shape, then workflow steps, then minimal inline examples, with clear one-level-deep references to targets.md, workflows.md, semantic-release.md, and troubleshooting.md. The Examples section explicitly instructs to load detailed content only after the package type is known. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents