setup-worktree
Set up a new git worktree for this repo by copying gitignored files (bin/) and building server assets so pnpm dev works without errors
85
77%
Does it follow best practices?
Impact
100%
2.43xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/setup-worktree/SKILL.mdQuality
Discovery
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.
This is a well-crafted, specific description that clearly communicates concrete actions for a niche workflow. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The natural trigger terms are strong and the specificity makes it highly distinguishable from other skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to set up a new worktree, create a parallel working directory, or needs a fresh worktree environment for this repo.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: setting up a git worktree, copying gitignored files (bin/), building server assets, and ensuring pnpm dev works without errors. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (set up git worktree, copy gitignored files, build server assets), but lacks an explicit 'Use when...' clause. The purpose is implied by the actions but not stated as a trigger condition. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'git worktree', 'gitignored files', 'bin/', 'building server assets', 'pnpm dev'. These are terms a developer would naturally use when needing this specific workflow. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining git worktrees with gitignored file copying and pnpm dev setup. Very unlikely to conflict with other skills due to the unique combination of triggers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, actionable setup skill with concrete commands and clear sequencing. The main weaknesses are minor redundancy (the 'Why' table duplicates inline explanations) and the lack of an explicit verification step to confirm the worktree is ready for development. Overall it's a well-structured skill that accomplishes its purpose.
Suggestions
Add a final verification step (e.g., 'Run `pnpm dev` and confirm the server starts without errors') to close the workflow loop.
Remove the 'Why each step is needed' table since each step already has inline context, or remove the inline explanations and keep only the table — avoid duplicating the rationale in both places.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Why each step is needed' table at the end is somewhat redundant since each step already has inline explanations. The 'Purpose' section also restates what the description already conveys. However, it's not egregiously verbose. | 2 / 3 |
Actionability | Every step has concrete, copy-paste-ready bash commands. The worktree path extraction is fully executable with the awk command, and the build command is specific. Claude can follow these without ambiguity. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logical, but there's no validation checkpoint — e.g., verifying that .env was copied successfully, confirming build:server completed without errors, or actually running `pnpm dev` to verify the setup works. For a setup workflow, a final verification step would be important. | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized with clear sections (Purpose, Steps, Why table) and doesn't need to be split across files. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- temporalio/ui
- Commit
01161e2
- 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.