Set up a dev environment in an existing worktree (make dev + copy secrets)
77
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
32%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 provides a basic understanding of the skill's purpose but is too terse and lacks explicit trigger guidance. It names specific technical actions but doesn't explain when Claude should choose this skill over others, which is critical for skill selection from a large pool.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to set up a new worktree, initialize development environment, or needs to configure secrets for local development'
Expand the capability description to clarify what 'make dev' accomplishes and what types of secrets are copied (e.g., 'Runs make dev to install dependencies and copies environment secrets from a template')
Include natural trigger terms users might say such as 'local setup', 'development configuration', 'env setup', or 'initialize project'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names specific actions ('make dev', 'copy secrets') and domain (dev environment, worktree), but lacks comprehensive detail about what these actions entail or what the full setup process involves. | 2 / 3 |
Completeness | Describes what it does (set up dev environment) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms ('dev environment', 'worktree', 'secrets') that users might say, but missing common variations like 'development setup', 'local environment', 'configure', or 'initialize'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'worktree' and 'make dev + copy secrets' is fairly specific to a particular workflow, but 'dev environment' is generic enough to potentially conflict with other setup-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted skill that demonstrates token efficiency while remaining fully actionable. It provides exact commands, clear error handling, and a structured reporting format. The skill appropriately delegates complexity to the setup script while giving Claude everything needed to interpret results and communicate with the user.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what worktrees are or how bash scripts work. The content is lean and assumes Claude's competence. | 3 / 3 |
Actionability | Provides the exact command to run with clear placeholder syntax. The reporting section gives specific output patterns to look for and exact response format to use. | 3 / 3 |
Workflow Clarity | Clear two-step sequence with explicit error handling ('If it fails, report the error and stop'). The validation is built into the script, and the skill correctly instructs to parse output for verification. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections. No external references needed; complexity is appropriately delegated to the setup script itself. | 3 / 3 |
Total | 12 / 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 | |
Table of Contents
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.