project-setup

Create a new GitHub project with standard configuration. Use when user asks to "create a project", "set up a new repo", "initialize a repository", or wants to start a new GitHub project.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

A highly actionable, token-efficient setup guide with concrete executable commands and justified operational notes. It loses points on workflow clarity for lacking validation/verification checkpoints on irreversible repo operations, and on progressive disclosure for keeping all ~180 lines inline with no external references.

Suggestions

Add explicit verification checkpoints after destructive/batch steps, e.g. run 'gh repo view <repo-name>' to confirm creation and 'gh api .../rulesets' to confirm the ruleset before pushing.

Move the verbatim MIT license and/or the detailed release-please configuration into reference files (e.g. references/LICENSE.txt, references/release-please.md) and link to them one level deep to reduce inline bulk and improve progressive disclosure.

Add a brief error-recovery note for the repo-create and pages POST steps so failures have a defined retry path.

Dimension	Reasoning	Score
Conciseness	The body is nearly all operational gh CLI commands, complete config files, and the verbatim MIT license; explanatory notes (e.g. the release-please pre-1.0 flag behavior, the org-level 409 conflict) are non-obvious failure-mode knowledge rather than concepts Claude already knows.	3 / 3
Actionability	It provides fully executable, copy-paste-ready gh CLI commands, complete JSON configs, the LICENSE content, and a README pattern with a worked example using appropriate <repo-name> placeholders.	3 / 3
Workflow Clarity	Steps 1-7 are clearly sequenced, but this batch/irreversible workflow (repo creation, settings mutation, branch protection, push) has no explicit validation or verification checkpoints or error-recovery loops, which caps the score per the destructive/batch-operations guideline.	2 / 3
Progressive Disclosure	No bundle files exist and all content is inline in a single ~180-line file; sections are well-organized, but the skill exceeds 50 lines and contains inline content (full license, detailed release-please config) that could be split into one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 description: third-person voice, explicit 'Use when' triggers with natural user phrasings, and a clear what/when structure. Its only weakness is the vague 'standard configuration' phrase, which understates the concrete actions the skill performs.

Suggestions

Replace 'with standard configuration' with a short enumeration of the key actions, e.g. 'with branch protection, MIT license, GitHub Pages, and Release Please' to lift specificity.

Consider adding 'new repository' or 'scaffold' as additional natural trigger variations users may say.

Dimension	Reasoning	Score
Specificity	Phrases 'Create a new GitHub project with standard configuration' name a concrete domain and action, but 'standard configuration' is vague and does not enumerate the specific concrete actions (branch protection, license, pages) that the skill actually performs.	2 / 3
Completeness	It explicitly answers what ('Create a new GitHub project with standard configuration') and when via an explicit 'Use when...' clause with concrete triggers, satisfying both halves.	3 / 3
Trigger Term Quality	The quoted triggers 'create a project', 'set up a new repo', 'initialize a repository', and 'start a new GitHub project' are natural phrasings a user would actually say, with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The 'new GitHub project/repo' niche with these specific setup triggers is distinct and unlikely to fire for unrelated skills, though it could marginally overlap with generic git skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: dwmkerr/claude-toolkit
Commit: 5432a9f

Reviewed: 3 days 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.