x-worktree

Use when the user (or a sibling skill via --wt flag) wants to spin up an isolated git worktree for a task — wraps the worktrunk `wt` CLI when present, falls back to native `git worktree`, switches the Bash session cwd into the new worktree, auto-applies docker isolation when profile present (skip with --no-isolate), and emits a machine-readable result envelope

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A thorough, executable, well-sequenced skill body with strong validation checkpoints and clean reference splitting. The only soft spot is conciseness: several inline security rationales add tokens that could live in a reference without losing operational clarity.

Suggestions

Move the multi-line security rationales (symlink-attack justification, DOCKER CONTEXT injection reasoning) into references/auto-isolation.md, keeping only the normative command in SKILL.md.

Tighten the Step 6.5 envelope-decision bullets into a compact table keyed on xwi_rc to reduce prose tokens while preserving the decision logic.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational with no basic-concept padding, but scattered inline 'Reasoning:' justifications (e.g., symlink-attack rationale, DOCKER CONTEXT injection rationale) and explanatory prose could be tightened or pushed into a reference.	2 / 3
Actionability	Fully executable commands throughout — 'git worktree add -b "$NEW_BRANCH" "$WORKTREE_PATH" "$BASE_BRANCH"', 'wt switch --create --base …', mktemp allocation, and a concrete stderr-sanitization pipeline — copy-paste ready with specific examples.	3 / 3
Workflow Clarity	A clearly numbered Steps 0–7 sequence with explicit validation checkpoints (env check, detached-HEAD check, doc-state check, ref-format validation) and feedback loops (mv rollback on migration failure, orphan cleanup on isolate failure).	3 / 3
Progressive Disclosure	SKILL.md is an overview with well-signaled one-level-deep references — 'See references/examples.md', 'caller-integration.md', 'auto-isolation.md', 'doc-naming.md', 'anti-patterns.md' — all verified to exist; content is appropriately split with easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, third-person description with an explicit 'Use when' trigger and a distinct niche. Its main weakness is trigger-term breadth: the single natural phrase 'git worktree' carries most of the weight while the rest is implementation jargon.

Suggestions

Broaden natural trigger terms (e.g., 'create a worktree', 'isolated checkout', 'work on a branch in isolation') so the description matches more ways a user might phrase the request.

Move internal detail ('--wt flag', 'machine-readable result envelope') out of the lead clause or compress it, so user-facing keywords dominate the opening.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'spin up an isolated git worktree', 'wraps the worktrunk wt CLI when present, falls back to native git worktree', 'switches the Bash session cwd', 'auto-applies docker isolation', 'emits a machine-readable result envelope' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicit 'Use when the user… wants to spin up an isolated git worktree' trigger plus a clear list of what the skill does answers both 'when' and 'what'.	3 / 3
Trigger Term Quality	The natural term 'git worktree' / 'isolated worktree' is present, but coverage of user-said variations is thin and diluted by internal jargon ('--wt flag', 'worktrunk wt CLI', 'machine-readable result envelope'); not the broad natural-term coverage of the level-3 anchor.	2 / 3
Distinctiveness Conflict Risk	A narrowly defined niche — isolated git worktree provisioning with optional docker isolation and a result envelope — with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: quangtran88/x-skills
Commit: 6381b15

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.