wt

Create a git worktree in worktree/ subdirectory with up-to-date master

2.30x

Quality

73%

Does it follow best practices?

Impact

90%

2.30x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

93%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 a tight, fully executable worktree-creation script with clear sequencing and a confirmation checkpoint. Its only weakness is the absence of explicit error handling for the state-changing git operations.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line summary, a single executable bash block, and a short Notes list, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	The Execution block is fully executable, copy-paste-ready bash using $ARGUMENTS, and the Notes give concrete removal/listing commands covering the common cases.	5 / 5
Workflow Clarity	Steps are clearly sequenced with comments and a final confirmation echo that verifies location and branch; minor validation gaps remain (no error handling if pull or worktree add fails).	4 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed and is well-organized into Execution and Notes sections, satisfying the simple-skill exception for a top score.	5 / 5
	Total	19 / 20 Passed

Description

53%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 concrete and third-person but one-dimensional: it states a single action with no 'when to use' trigger guidance. It is specific enough to avoid most conflicts yet lacks the trigger phrases that would make it discoverable.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when you need an isolated checkout of master for parallel work.'

Mention common synonyms or variants users might say (e.g. 'worktree', 'parallel branch', 'isolated checkout').

List the secondary action it performs (submodule init) so coverage reads as more than a single step.

Dimension	Reasoning	Score
Specificity	Names the domain (git worktree) and one concrete action (create a worktree in worktree/ with up-to-date master), but lists no other actions, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It clearly states what the skill does but has no 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	'git worktree' and 'master' are relevant keywords a user might say, but there are no synonyms or natural variations beyond the single technical term.	3 / 5
Distinctiveness Conflict Risk	Worktree creation is a clear niche with distinct triggers and minimal conflict risk, though it could overlap slightly with general git-branching skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: homeassistant-ai/ha-mcp
Path: .claude/skills/wt/SKILL.md
Commit: 47582a7

Reviewed: ~22 hours 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.