CtrlK
BlogDocsLog inGet started
Tessl Logo

worktree-detection

How to find a Git worktree by task number without hardcoding paths. Use in hooks or scripts that need to locate a specific task's worktree.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 body is a tight, executable reference with clear structure, inline validation, and a verification checklist, all appropriate for a simple single-purpose skill. No bundle files are present or needed.

DimensionReasoningScore

Conciseness

The body is lean: two executable snippets plus brief, purposeful rationale and red flags; it assumes Claude's competence and avoids explaining basic git or shell concepts.

5 / 5

Actionability

Both bash snippets are complete and copy-paste ready, covering the core lookup and TASK_NUM extraction from agent variables.

5 / 5

Workflow Clarity

The single action is unambiguous with inline validation (skip cleanly when no worktree found) and an explicit Verification checklist; the simple-skill exception applies.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, the content is organized into well-labeled sections (When to Use, Pattern, Why this works, Red Flags, Verification).

5 / 5

Total

20

/

20

Passed

Description

73%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 clearly answers what the skill does and when to use it within a narrow, well-delineated niche. It is concise and free of fluff, with only minor room to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"find a Git worktree by task number without hardcoding paths" names the domain and one concrete action (locate a task's worktree) but offers no broader coverage of related actions.

3 / 5

Completeness

It states the what ("find a Git worktree by task number without hardcoding paths") and an explicit when ("Use in hooks or scripts that need to locate a specific task's worktree"), but the trigger is a single condition rather than multiple concrete phrases.

4 / 5

Trigger Term Quality

"hooks or scripts", "worktree", "task number" are natural terms a user of this domain would say, though a few synonyms or variants are missing.

4 / 5

Distinctiveness Conflict Risk

Locating a Git worktree by task number is a narrow, distinct niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

20

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

Validation for skill structure

No warnings or errors.

Repository
marmelab/atomic-crm
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.