CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup

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

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

The content is highly actionable with concrete commands and project-specific paths, and the workflow is clearly sequenced with a prerequisite checkpoint. It is held back only by minor redundancy in the rules section and the absence of a post-build validation step.

Suggestions

Add an explicit post-build verification step (e.g. 'Confirm the build succeeded with no errors before orienting the developer') to close the workflow_clarity validation gap.

De-duplicate the 'project.yml is the source of truth' and 'no test suite' rules, which appear both inline in Steps/design decisions and again in Important Rules — keep them in one place and reference them.

Consider moving the detailed architecture overview and scanned-tool-paths table into a separate reference file with a one-line pointer, to improve progressive disclosure for this ~85-line skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it gives commands and project-specific file paths without explaining what SwiftData or Xcode is — but the 'Important Rules' section repeats constraints already stated in Step 2 and the design decisions, a minor instance of redundancy that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (`sw_vers -productVersion`, `xcodegen generate`, `xcodebuild -scheme Chops -configuration Debug build`) and concrete file paths for every architectural component, covering the common onboarding cases.

5 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with a stop-checkpoint in Step 1 ('If any are missing, tell the user what to install and stop'), but there is no explicit verification after the build step or error-recovery feedback loop, leaving a minor validation gap.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Steps, Common tasks, Important Rules) with no nested or buried references, but everything is inlined in a single ~85-line file with no external references; the architecture and scanned-tool-path detail could arguably be split out, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 is specific and clearly distinct, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding trigger guidance would move it from good to comprehensive.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when a new contributor needs to set up the Chops development environment or onboard to the codebase.'

Consider natural synonyms like 'onboard' and 'set up the environment' to broaden trigger-term coverage.

Reframe the dash-listed topics as concrete verbs (e.g. 'check prerequisites, generate the Xcode project, build, and orient to the architecture') to lift specificity toward 5.

DimensionReasoningScore

Specificity

Names the onboarding domain and lists several concrete coverage areas — 'prerequisites, build, architecture, and common tasks' — which is more than 1-2 actions but expressed as topics rather than fine-grained verbs, leaving minor gaps versus a fully comprehensive action list.

4 / 5

Completeness

The 'what' is clear ('Get a new developer up and running... prerequisites, build, architecture, and common tasks') but there is no explicit 'Use when...' trigger clause, so 'when' is only weakly implied, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains good natural keywords a user might say ('new developer', 'up and running', 'codebase', 'build', 'prerequisites'), but misses common synonyms like 'onboard' or 'set up the environment'.

4 / 5

Distinctiveness Conflict Risk

It names a specific codebase ('the Chops codebase') and a narrow niche (developer onboarding), giving it distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

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.