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.
Install with Tessl CLI
npx tessl i github:dwmkerr/claude-toolkit --skill project-setup90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 well-structured skill description with excellent trigger terms and completeness. The explicit 'Use when...' clause with multiple natural language variations is a strong point. The main weakness is the vague 'standard configuration' phrase which doesn't specify what concrete actions the skill performs.
Suggestions
Expand 'standard configuration' to list specific actions (e.g., 'Creates README, .gitignore, license file, and configures branch settings')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub project) and one action (create with standard configuration), but doesn't list multiple specific concrete actions like what 'standard configuration' includes (e.g., README, .gitignore, license, branch protection). | 2 / 3 |
Completeness | Clearly answers both what ('Create a new GitHub project with standard configuration') and when ('Use when user asks to...') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'create a project', 'set up a new repo', 'initialize a repository', 'start a new GitHub project'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub project creation with distinct triggers. The combination of 'GitHub', 'repo', 'repository', and 'project' creation makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent actionability and conciseness. The commands are specific, executable, and organized logically. The main weakness is the lack of validation steps between API calls - if branch protection or Pages setup fails, there's no guidance on detecting or recovering from errors.
Suggestions
Add validation commands after each API call (e.g., `gh api repos/dwmkerr/<repo-name> --jq '.allow_squash_merge'` to verify settings applied)
Include error handling guidance for common failures like 'Pages already enabled' or 'Ruleset name already exists'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the necessary commands and configuration without explaining what GitHub, repos, or branch protection are. Every section serves a clear purpose. | 3 / 3 |
Actionability | Fully executable bash commands throughout with specific gh CLI syntax, API endpoints, and exact flags. The LICENSE and README templates are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints to verify each step succeeded before proceeding. Missing error handling for API calls that might fail (e.g., Pages already enabled, ruleset conflicts). | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections: overview of what gets created, then step-by-step process, then example usage. Appropriate length for a single-file skill with no need for external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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 | |
- Reviewed
Table of Contents
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.