CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.35x
Quality

100%

Does it follow best practices?

Impact

96%

1.35x

Average score across 7 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

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 routing and policy document for GitHub repository setup. It efficiently classifies repos, provides concrete inspection commands, establishes hard security defaults, and delegates detailed implementation to well-organized references. The content is concise yet comprehensive, with strong workflow sequencing and appropriate progressive disclosure.

DimensionReasoningScore

Conciseness

The content is lean and efficient throughout. It assumes Claude's competence with GitHub concepts, avoids explaining what PRs, Actions, or environments are, and every section earns its place by providing specific policy defaults, concrete CLI commands, or routing decisions. No filler or unnecessary context.

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), clear classification criteria, and a concrete output format example. 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 (step 4: pause GitHub wiring until readiness proof exists). The release and deploy routes show clear pipeline shapes with sequenced stages. The output section includes a verification step and explicit instruction to flag when live settings weren't checked, serving as a feedback loop against false confidence.

3 / 3

Progressive Disclosure

Excellent progressive disclosure structure. The main skill provides a concise overview with clear routing to specific references (release-workflows.md, deploy-environments.md, actions-security.md, etc.) that are one level deep and well-signaled. Each route section tells the reader exactly which references to consult and when, avoiding monolithic content while maintaining navigability.

3 / 3

Total

12

/

12

Passed

Description

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, well-crafted description that clearly enumerates specific GitHub-related capabilities, includes natural trigger terms users would employ, and explicitly states both what the skill does and when to use it. The routing guidance at the end is a particularly effective touch for reducing overlap with adjacent deploy and release skills.

DimensionReasoningScore

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: repo settings, branch/ruleset policy...') and when ('Use when standardizing GitHub setup for repos, CI/CD, publishing versioned packages, or deploying running apps'). Also includes routing guidance for disambiguation.

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 across GitHub collaboration and delivery concerns.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche around GitHub repository configuration and delivery infrastructure. The explicit routing instructions ('route app deploy details to deploy references and package publish details to release references') further reduce conflict risk by delineating boundaries with related skills.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents