x-worktree-isolate

Use when the user runs multiple git worktrees of the same repo in parallel and hits docker-compose container_name / port / volume collisions OR has stateful singletons (Slack/Discord bots, schedulers, webhook receivers, host crontabs) that must not run concurrently across worktrees. Singleton-aware in v0.2. Wraps inspector + override emitter + worktrunk hook.

2.63x

Quality

—

Does it follow best practices?

Impact

100%

2.63x

Average score across 1 eval scenario

Securityby

Passed

No known issues

Quality

Content

77%

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

A highly actionable, well-sequenced body with strong validation feedback loops and a clean reference structure, undermined only by time-sensitive version banners inflating conciseness and a missing gotchas.md file referenced from the body. Fixing those two issues would lift the weakest dimensions.

Suggestions

Move the v0.2/v0.3 migration banners and inline version numbers (0.3.1, registry_schema: 2) into a 'Migration / version history' section so the main flow stays version-neutral and lean.

Add the missing references/gotchas.md (or correct the body's 'gotchas.md' references to the actual filename) so every cited bundle path resolves.

Consider extracting the registry claim/conflict state-machine detail into references/singleton-patterns.md to slim the inline Singletons section while preserving actionability.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of basic-concept padding, but it front-loads two version-migration banners (v0.2 hard-reject, v0.3 self-heal) and embeds time-sensitive version numbers (0.3.1, registry_schema: 2) outside any 'deprecated/old patterns' section — the rubric penalizes such version churn, capping conciseness below 3.	2 / 3
Actionability	Every workflow stage is given as a concrete subcommand with specific flags and exact behaviors (e.g. 'apply --force/--steal', 'default + slot * 1000' port formula), plus verifiable line-number references (apply.sh:58-65 checked against the actual script), reaching copy-paste-ready executable guidance.	3 / 3
Workflow Clarity	A clear two-phase INSPECT/APPLY sequence is followed by a detection table and numbered workflow steps with explicit validation checkpoints (doctor, --dry-run) and feedback loops (blocker -> ack-host-singletons, claim -> SINGLETON_CONFLICT -> --force/steal), satisfying the explicit-validation anchor.	3 / 3
Progressive Disclosure	A well-signaled References section lists six real one-level-deep files (all verified present) and the body ties to real scripts, but 'gotchas.md' is referenced twice in the body (Bootstrap step 3 and the Gotchas section) yet is absent from the bundle, leaving a broken reference that prevents a 3.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 dense, specific, well-triggered description that crisply states both the problem (parallel-worktree compose collisions + concurrent singletons) and when to invoke it. The trailing 'Singleton-aware in v0.2 / Wraps inspector...' version flavor is slightly fluffy but does not dilute the otherwise excellent trigger guidance.

Dimension	Reasoning	Score
Specificity	Names concrete collision types ('container_name / port / volume collisions') and enumerates specific stateful singletons ('Slack/Discord bots, schedulers, webhook receivers, host crontabs'), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Opens with an explicit 'Use when...' trigger and states what the skill does ('wraps inspector + override emitter + worktrunk hook'), clearly answering both what and when.	3 / 3
Trigger Term Quality	Surfaces natural user phrasing — 'parallel worktrees', 'compose ... collisions', 'container_name', 'port', 'volume' — plus concrete singleton names a user would actually mention, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The worktree-compose-collision + stateful-singleton niche is sharply scoped and unlikely to fire for unrelated skills; the closing version line ('Singleton-aware in v0.2') is mild marketing fluff but does not broaden the trigger surface.	3 / 3
	Total	12 / 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: 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.