CtrlK
BlogDocsLog inGet started
Tessl Logo

wt-switch-create

Create a new worktrunk worktree (optionally in another repo) and switch this session's working directory into it. Use when launching a session that should work in its own worktree.

72

Quality

90%

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

The canonical home for this skill is wt-switch-create in max-sixty/worktrunk

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A well-sequenced, highly actionable procedural skill with strong error-recovery feedback loops and no concept over-explanation. Minor verbosity in recovery prose and a dangling rationale.md reference keep it just short of top marks.

Suggestions

Tighten the step-3 "Tool error" and "Denied" recovery prose to bullet-level brevity; the operational detail can be compressed without losing the routing logic.

Resolve the maintainer reference to rationale.md — either add the file to a references/ bundle or remove the HTML comment, so no dangling reference remains.

DimensionReasoningScore

Conciseness

The body is dense and operational, assuming Claude knows what a worktree is, but the step-3 recovery and "Denied" prose run long and could be trimmed without losing clarity.

4 / 5

Actionability

Concrete, copy-paste-ready commands and tool calls throughout (`EnterWorktree({name: "<branch>"})`, `wt -C <repo> switch --create <branch> --no-cd --format=json`, `git stash push -u`, `cd <path>`) cover the common cases.

5 / 5

Workflow Clarity

Steps 1–3 are clearly sequenced with explicit validation branches ("Branch already exists", tool-error `cd` recovery, "Shell cwd was reset") and feedback loops that route back to user action before continuing.

5 / 5

Progressive Disclosure

Content is well organized into Arguments / What to do / Cleanup / Scope sections in a single appropriately self-contained file, but the maintainer note references a non-existent `rational.md`/`rationale.md`, a minor dangling-reference gap.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A tight, third-person description that concretely states both what the skill does and when to use it, with a clear niche and low conflict risk. Keyword coverage is strong though not exhaustive of every synonym.

DimensionReasoningScore

Specificity

"Create a new worktrunk worktree (optionally in another repo) and switch this session's working directory into it" names two concrete actions (create + switch) with the cross-repo nuance, which is comprehensive for this narrow single-purpose skill.

5 / 5

Completeness

It explicitly states what ("Create a new worktrunk worktree... and switch this session's working directory into it") and when ("Use when launching a session that should work in its own worktree") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural terms "worktree", "worktrunk", "session", and "working directory" appear, but common synonyms a user might say (e.g. "branch", "isolated environment") are absent, so coverage is good rather than exhaustive.

4 / 5

Distinctiveness Conflict Risk

The worktrunk/worktree niche and session re-rooting trigger are distinct from other skills, giving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
max-sixty/worktrunk
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.