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.

82

1.08x
Quality

95%

Does it follow best practices?

Impact

77%

1.08x

Average score across 8 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is dense, actionable, and well-sequenced with explicit validation checkpoints. Its one real weakness is progressive disclosure: all 11 referenced detail files are missing from the bundle, breaking the structure the overview promises.

Suggestions

Add the missing references/*.md files (release-workflows, release-targets, semantic-release, release-troubleshooting, deploy-workflows, deploy-environments, deploy-secrets, deploy-troubleshooting, repo-settings, templates, actions-security) or remove the links—the overview currently routes to 11 non-existent files.

If shipping without the detail files, inline the minimum needed policy per section so the skill is usable standalone rather than depending on absent references.

DimensionReasoningScore

Conciseness

Lean, directive prose that assumes domain knowledge—terse policy bullets and concrete probes without explaining what GitHub, PRs, or Actions are—so every token earns its place.

3 / 3

Actionability

Provides copy-paste `gh repo view`/`gh api` probes, exact file paths to inspect, and specific hardening defaults (pin to full commit SHAs, run actionlint and zizmor, default permissions to read-only).

3 / 3

Workflow Clarity

The 'Start Here' steps are clearly sequenced with explicit validation checkpoints—pause GitHub wiring until the repo has durable readiness proof, and never present inferred live settings as confirmed.

3 / 3

Progressive Disclosure

The body is well-organized with clearly signaled one-level-deep reference links, but the referenced references/*.md files do not exist in the bundle, so navigation dead-ends and the promised detail is absent.

2 / 3

Total

11

/

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.

A strong, well-scoped description that names concrete capabilities, includes natural trigger terms, and explicitly pairs 'what' with 'when'. The routing clauses further sharpen its niche and reduce conflict risk. It uses third-person voice throughout, so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—'repo settings, branch/ruleset policy, PR and security templates, Actions hardening, GitHub Environments, release workflows, and deploy workflows'—matching the multi-action anchor rather than vague language.

3 / 3

Completeness

Explicitly states what it does (set up/align a repo's GitHub collaboration and delivery surface) and when to use it ('Use when standardizing GitHub setup...'), satisfying both the what and the when with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural triggers like 'standardizing GitHub setup for repos', 'CI/CD', 'publishing versioned packages', and 'deploying running apps' mirror phrasings users would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to GitHub policy and workflow shape with explicit routing of deploy and release details to separate references, reducing overlap with adjacent infrastructure or deploy skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 16 missing

Warning

referenced_paths_exist

Referenced path issues: 16 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents