uinaf/gh-setup
Set up or align GitHub repo settings, branch/ruleset policy, templates, Actions hardening, Environments, release workflows, and deploy workflows for continuously publishable or deployable repositories.
97
100%
Does it follow best practices?
Impact
96%
1.35xAverage score across 7 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 a strong skill description that clearly enumerates specific GitHub repository setup capabilities, includes natural trigger terms users would employ, and explicitly addresses both what the skill does and when to use it. The inclusion of routing guidance for adjacent concerns (deploy vs. release) is a notable strength that reduces conflict risk with related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: repo settings, branch/ruleset policy, PR and security templates, Actions hardening, GitHub Environments, release workflows, and deploy workflows. These are clearly defined, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Set up or align a repository's GitHub collaboration and delivery surface' with enumerated capabilities) and when ('Use when standardizing GitHub setup for repos, CI/CD, publishing versioned packages, or deploying running apps') with explicit routing guidance for edge cases. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'GitHub', 'repo settings', 'CI/CD', 'branch policy', 'PR templates', 'Actions', 'deploy', 'release workflows', 'publishing versioned packages'. Good coverage of terms a user would naturally use when requesting GitHub repository setup. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around GitHub repository configuration and collaboration infrastructure. The routing instructions ('route app deploy details to deploy references and package publish details to release references') further reduce conflict risk by explicitly delineating boundaries with related skills. | 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 an exceptionally well-structured skill that serves as a clear policy and routing document for GitHub repository setup. It is concise, actionable with specific CLI commands and tool names, has clear multi-step workflows with validation gates, and demonstrates excellent progressive disclosure by routing to specific references only when needed. The output template with an explicit 'settings not checked' disclosure pattern is a particularly strong safety feature.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude's competence with GitHub, Actions, and CI/CD concepts without explaining what they are. Every section earns its place—policy defaults are stated as terse rules, not tutorials. The `gh` CLI probes are practical additions, not padding. | 3 / 3 |
Actionability | Provides concrete `gh` CLI commands for inspecting repo state, specific file paths to check, explicit hard defaults for Actions security (e.g., no `pull_request_target` for code execution, pin to commit SHAs), named tools (`actionlint`, `zizmor`), and a concrete output template. The guidance is specific and directly executable. | 3 / 3 |
Workflow Clarity | The 'Start Here' section provides a clear 5-step sequence with explicit validation checkpoints: inspect before changing, check live settings before recommending, classify the repo, verify readiness proof before wiring, and keep docs current. Step 4 explicitly pauses work if readiness proof is missing—a feedback loop for risky operations. The release and deploy routes each show clear pipeline shapes with sequenced stages. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a concise overview with well-signaled one-level-deep references to specific topics (release workflows, deploy environments, Actions security, templates, repo settings, etc.). Each section tells you when to read the reference and what it covers. Navigation is clear and references are contextually placed. | 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