Name: project-setup
Rating: 64.8 (1 reviews)
Author: dwmkerr

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

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/dwmkerr/skills/project-setup/SKILL.md

Quality

Content

72%

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

This is a solid, actionable skill with fully executable commands for setting up a GitHub repository with specific organizational conventions. Its main weakness is the lack of validation checkpoints between steps (e.g., verifying API calls succeeded) and some verbosity in areas like the full MIT license text and the release-please version strategy explanation. The workflow structure and progressive disclosure are well-handled for a standalone skill.

Suggestions

Add validation checkpoints after key API calls, e.g., `gh api repos/dwmkerr/<repo-name> --jq '.allow_squash_merge'` to verify settings were applied correctly

Trim the version strategy explanation for release-please to 1-2 lines; the detailed rationale about version number burning is unnecessary context for Claude

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete commands, but includes some unnecessary verbosity: the full MIT license text is boilerplate Claude could generate, the version strategy explanation for release-please is somewhat lengthy, and the example usage section at the end partially repeats the workflow. However, most content earns its place as project-specific configuration.	2 / 3
Actionability	Every step provides fully executable, copy-paste-ready bash commands and file contents. The gh CLI commands are specific with exact flags, API endpoints, and field names. The README template includes a concrete example. This is highly actionable.	3 / 3
Workflow Clarity	Steps are clearly numbered and sequenced, and the optional step (Release Please) is well-signaled. However, there are no validation checkpoints — no verification that the repo was created successfully, that branch protection was applied correctly, or that GitHub Pages was enabled. For a multi-step process involving API calls that can fail, explicit validation steps are missing.	2 / 3
Progressive Disclosure	For a skill with no bundle files, the content is well-organized with clear section headers, a summary of what gets created upfront, and logical progression from creation through configuration to commit. The optional Release Please section is appropriately marked. The structure is easy to navigate.	3 / 3
	Total	10 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has strong completeness with explicit 'Use when' triggers and good natural language trigger terms that users would actually say. Its main weakness is the vagueness of 'standard configuration' — it doesn't specify what concrete actions are performed (e.g., creating README, .gitignore, license, branch protection rules), which limits both specificity and distinctiveness.

Suggestions

Replace 'standard configuration' with specific actions like 'Creates README, .gitignore, LICENSE, and initial directory structure' to improve specificity.

Add distinguishing details about what kind of GitHub project setup this covers (e.g., language-specific templates, CI/CD setup) to reduce potential overlap with other repository or scaffolding skills.

Dimension	Reasoning	Score
Specificity	Names the domain (GitHub project) and one action (create with standard configuration), but doesn't list specific concrete actions like initializing git, creating README, setting up .gitignore, configuring CI, etc. 'Standard configuration' is vague.	2 / 3
Completeness	Clearly answers both what ('Create a new GitHub project with standard configuration') and when ('Use when user asks to "create a project", "set up a new repo", "initialize a repository"') with explicit trigger phrases.	3 / 3
Trigger Term Quality	Includes natural phrases users would actually say: 'create a project', 'set up a new repo', 'initialize a repository', 'new GitHub project'. Good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Reasonably specific to GitHub project creation, but could overlap with general git skills, repository management skills, or project scaffolding skills. 'Standard configuration' is ambiguous and doesn't clarify what makes this distinct from other project setup tools.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: dwmkerr/claude-toolkit
Commit: 5934476

Reviewed: 2 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.