CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

worktrees

Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./src/skills/worktrees/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable protocol with concrete Git commands, a pre-flight safety checklist, explicit user-confirmation gates, and validation checkpoints across all four phases. It is token-efficient with only minor duplication, and its main gaps are the absence of error-recovery feedback loops and non-concrete integration commands.

DimensionReasoningScore

Conciseness

The body is imperative and assumes Claude's knowledge of Git, with only minor trimmable padding: the intro line "Its value is giving the Orchestrator a consistent OMO workflow..." duplicates the description, and the ignore-file setup is restated in Phases 1 and 4. This matches 'Efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean anchor 5.

4 / 5

Actionability

Concrete, executable commands are provided (git worktree add -b <branch-name> .slim/worktrees/<slug> <base-commit/branch>, git worktree remove, git worktree list) plus a full JSON manifest example and an exact gitignore block. It stops short of anchor 5 because the integration step only says "such as merge or cherry-pick" without copy-paste-ready commands.

4 / 5

Workflow Clarity

Four clearly sequenced phases include explicit checkpoints: a pre-flight checklist, mandatory user confirmation gates, a diff review before integration, and an uncommitted-changes check before removal — so validation is present and the destructive-operation cap at 3 does not apply. It misses anchor 5 because there are no error-recovery feedback loops (e.g., what to do if worktree add fails or a merge conflicts).

4 / 5

Progressive Disclosure

There are no bundle files and no external references, and the ~155-line body is well-sectioned (Core Contract, Safety Guidelines, Workflow Guide, When to Use vs. Not Use) and self-contained. Structure is good (anchor 4), but the under-50-line exception for a 5 does not apply, and the JSON manifest schema and gitignore block could arguably live in separate reference files.

4 / 5

Total

16

/

20

Passed

Description

48%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 names a clear, distinctive domain (Git worktrees) but relies on a single generic action verb and undefined internal jargon ("OMO"), and it lacks an explicit 'Use when...' trigger clause. It reads as a purpose statement rather than a capability-plus-trigger description, leaving a user unsure exactly when to invoke it.

Suggestions

Replace the generic "Manage" with concrete actions, e.g., "Create, delegate, integrate, and clean up Git worktrees as isolated coding lanes".

Add an explicit trigger clause: "Use when running parallel agents or experiments on separate branches, doing risky refactors, or when the user mentions worktrees or isolated branches."

Drop or expand the undefined jargon "OMO" — it is not a term a user would say and adds no trigger value.

DimensionReasoningScore

Specificity

"Manage Git worktrees" names the domain but the sole action verb is the generic "Manage", and "OMO safe isolated coding lanes" is undefined jargon rather than a concrete capability. This matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because no concrete second action (e.g., create, integrate, clean up lanes) is actually stated.

2 / 5

Completeness

The 'what' is present ("Manage Git worktrees as ... isolated coding lanes") though somewhat vague, and there is no 'Use when...' clause — "for complex, risky, or parallel work" is a purpose qualifier with generic adjectives rather than explicit trigger guidance, which caps completeness at 3. It does not reach 4 because the 'when' is only weakly implied, unlike the anchor-4 example's explicit 'Use when working with PDF files.'

3 / 5

Trigger Term Quality

Relevant keywords like "Git worktrees", "parallel work", and "risky" are present, but "OMO" is internal jargon a user would never say, and natural variations such as "branches", "multiple branches", or "experiments" are missing. This fits 'Some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Manage Git worktrees" carves a clear niche that a user requesting worktree or parallel-branch isolation would naturally trigger, with only minor overlap risk against general git or parallel-agent orchestration skills. It is mostly distinct (anchor 4) rather than a 5 because "complex, risky, or parallel work" is broad and the description lacks the concrete distinct triggers shown in the anchor-5 example.

4 / 5

Total

12

/

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

alvinunreal/oh-my-opencode-slim

Path

src/skills/worktrees/SKILL.md

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.