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

2.43x

Quality

—

Does it follow best practices?

Impact

100%

2.43x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Quality

Content

87%

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

A tight, highly actionable skill body with well-organized sections and executable commands. The only gap is the absence of explicit validation checkpoints between steps, which would make the workflow more robust.

Suggestions

Add a quick verification after the copy and build steps — e.g., confirm `[ -f .env ]` after copying and that `server/ui/assets/` exists after `pnpm build:server` — to create explicit checkpoints.

Note what to do if `pnpm build:server` fails (e.g., run `pnpm install` first) so there is a light feedback loop for the riskiest step.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: short Purpose, three numbered steps with copy-paste commands, and a compact 'Why' table — every section earns its place and no tokens explain concepts Claude already knows.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (`git worktree list`, the `MAIN=...; cp $MAIN/.env ./.env` block, `pnpm build:server`) with concrete specifics like the build path, matching the 'fully executable' anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced and a success signal is given ("pnpm dev should now start without errors"), but there is no validation/checkpoint to confirm each step succeeded (e.g., verifying .env was copied or that assets were built), so checkpoints are implicit rather than explicit.	2 / 3
Progressive Disclosure	A simple single-purpose skill under 50 lines with no need for external references; it is well-organized into Purpose, Steps, and a Why table, which per the simple-skills note earns a 3.	3 / 3
	Total	11 / 12 Passed

Description

67%

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, concrete, and distinct, but omits an explicit 'Use when...' trigger clause, leaving the 'when to use' only implied. Adding a trigger phrase would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., 'Use when setting up a new git worktree in this repo, when pnpm dev fails after creating a worktree, or when gitignored files (bin/) are missing.'

Include a few natural phrasings users would actually say ('worktree setup', 'dev server won't start in worktree', 'missing bin/ in new worktree') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "copying gitignored files (bin/)" and "building server assets" — tied to a concrete outcome ("so pnpm dev works without errors"), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly states what the skill does but lacks an explicit 'Use when...' / trigger clause for when Claude should invoke it; the 'when' is only implied, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes natural terms a user might say ("git worktree", "pnpm dev", "server assets") but is missing common variations users would voice when needing this (e.g., 'worktree setup', 'dev environment not working', 'missing bin'), so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	The scope is a clear niche — preparing a git worktree for this specific repo by copying gitignored files and building assets — with triggers unlikely to overlap with unrelated 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: temporalio/ui
Commit: ddbeb54

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