setup

Get a new developer up and running with the Chops codebase — prerequisites, build, architecture, and common tasks.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/setup/SKILL.md

Quality

Content

86%Weight 40%Scale 1-3

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

A tightly written, highly actionable setup guide that earns its tokens with project-specific commands and architecture pointers. The main gap is workflow clarity: prerequisites and build steps lack explicit validation checkpoints and a build-success feedback loop.

Suggestions

Add explicit validation checkpoints, e.g. after Step 2 verify 'Chops.xcodeproj' was generated and after Step 3 confirm the build succeeded before orienting the developer.

Include a build-failure feedback loop ('If the build fails, re-run xcodegen generate, then rebuild') to mirror the explicit-retry guidance seen in the prerequisites step.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense with project-specific facts (file paths, commands, design decisions) that Claude could not infer, with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	It provides copy-paste-ready commands ('sw_vers -productVersion', 'xcodegen generate', 'xcodebuild -scheme Chops -configuration Debug build') plus exact file paths and concrete instructions for each common task.	3 / 3
Workflow Clarity	Steps are numbered and sequenced, but Step 1 (prerequisites) and Step 2 (generate) have no validation checkpoint, and the 'no test suite' workflow lacks an explicit validate-after-build feedback loop despite build being a risky pass/fail operation.	2 / 3
Progressive Disclosure	No bundle files exist and none are needed; the content is a single self-contained, well-organized skill under 50 effective lines with clear sections (Instructions, Common tasks, Important Rules), which satisfies the simple-skill scoring note.	3 / 3
	Total	11 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 specific, domain-scoped onboarding description that clearly conveys what it does and is unlikely to conflict with other skills. Its main weakness is the absence of an explicit 'when to use' trigger clause, which caps completeness and leaves trigger-term quality at mid-range.

Suggestions

Add an explicit trigger clause such as 'Use when a new contributor needs to set up the Chops development environment or orient to the codebase.'

Include natural user phrasings ('set up Chops', 'build Chops', 'Chops onboarding') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the Chops codebase domain and multiple concrete action areas — 'prerequisites, build, architecture, and common tasks' — going beyond vague language to list several specific capabilities.	3 / 3
Completeness	It clearly answers 'what' (get up and running: prerequisites, build, architecture, common tasks) but has no explicit 'Use when...' or trigger clause, so 'when' is only implied.	2 / 3
Trigger Term Quality	It contains relevant onboarding terms a user might say ('new developer', 'build', 'prerequisites'), but lacks natural trigger phrasing and common variations like 'set up Chops' or 'onboard to Chops'.	2 / 3
Distinctiveness Conflict Risk	It is tightly scoped to the named 'Chops codebase', giving it a clear niche that is unlikely to trigger for or conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Shpigford/chops
Path: .claude/skills/setup/SKILL.md
Commit: 1a1ff0d

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