Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

git-worktree-remove

Safely remove a git worktree with branch cleanup and safety checks

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/skills/git-worktree-remove/SKILL.md

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 lean, executable, safety-first playbook: every step is a concrete command, destructive actions are gated by explicit checks and confirmations, and sections are well organized with a decision table. It stops short of top marks due to restated content across three sections, undefined shell variables, and flags not integrated into the step flow.

Suggestions

Show how to resolve the argument into $WORKTREE_PATH/$BRANCH/$BRANCH_SLUG (e.g. via git worktree list or git root) so the commands are fully copy-paste ready.

Integrate the --force/--keep-branch/--keep-remote flags into the numbered steps (e.g. "if --keep-branch: skip step 6") instead of listing them only in the Flags table.

Collapse the Process list or the Quick reference table (they overlap with Removal steps) to remove redundant tokens.

Dimension	Reasoning	Score
Conciseness	Terse bash blocks, tables, and bullets with no explanation of concepts Claude already knows, but the 9-step "Process" overview, "Removal steps" code, and "Quick reference" table restate the same actions, which could be trimmed.	4 / 5
Actionability	Concrete executable commands throughout (protected-branch grep check, merge-base --is-ancestor, git worktree remove, neonctl/pscale cleanup) plus report-format templates; minor gaps: $WORKTREE_PATH/$BRANCH/$BRANCH_SLUG are never derived from the argument, and "# On confirmation" placeholders lack a mechanism.	4 / 5
Workflow Clarity	This destructive workflow explicitly validates before acting (protected-branch block, dirty-state check with commit/force/cancel options, merge-status check, confirmations before -D and remote deletion), so the destructive-cap doesn't apply; it falls short of a 5 only because command-failure recovery is absent and the --keep-branch/--keep-remote flags aren't woven into the step sequence.	4 / 5
Progressive Disclosure	~180 lines, well-sectioned with clear headers, and suite links (../../commands/git-worktree.md etc.) are clearly signaled one level deep; the DB-cleanup detection logic duplicated from /git-worktree could live in a shared reference file.	4 / 5
	Total	16 / 20 Passed

Description

61%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 states what the skill does with mostly concrete actions and natural git vocabulary, but it lacks an explicit "Use when..." trigger clause and has minor overlap with sibling worktree-cleanup commands. Adding trigger guidance and one or two more specific actions (remote branch deletion, DB cleanup) would raise it to the top tier.

Suggestions

Append a trigger clause, e.g. "Use when the user asks to remove or delete a specific git worktree by name", to satisfy the missing "when" half of completeness.

Enumerate the concrete teardown actions, e.g. "remove the worktree, delete local/remote branches, prune references, and remind about database branch cleanup", replacing the generic "safety checks".

Include a distinguishing keyword (e.g. "single worktree teardown") to reduce overlap with the sibling /git-worktree-clean command.

Dimension	Reasoning	Score
Specificity	"remove a git worktree" and "branch cleanup" name the domain with 1-2 concrete actions, but "safety checks" is generic and the description omits covered capabilities like remote branch deletion and database cleanup, matching the 'not comprehensive' anchor rather than 'several specific actions'.	3 / 5
Completeness	The description gives a clear "what" ("Safely remove a git worktree with branch cleanup and safety checks") but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"git worktree", "remove", "branch", "cleanup" are terms users would naturally say, giving good keyword coverage; a few natural synonyms like "delete worktree" or "teardown" are missing, so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	"git worktree remove" carves a clear niche, but the description doesn't distinguish it from the sibling /git-worktree-clean command, leaving minor overlap risk with a closely related skill in the same suite.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 4 suspicious	Warning

	Total	14 / 16 Passed

Repository: FlorianBruniaux/claude-code-ultimate-guide
Path: examples/skills/git-worktree-remove/SKILL.md
Revision: e0d8cbb

Reviewed: 17 days ago

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.

git-worktree-remove

Table of Contents

Is this your skill?