workforest

This skill should be used when the user asks about 'workforest', 'git forest', 'git forest list', 'git forest add', 'git forest remove', 'forest layout', or mentions managing worktrees with workforest. Also use when the user asks how workforest works, how to use git forest commands, or how to navigate a forest.

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 ./plugins/git-workforest/skills/workforest/SKILL.md

Quality

Content

68%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 content is a tight, well-structured, actionable reference for git-workforest with concrete commands and examples. Its main weakness is the absence of explicit validation/verification checkpoints for destructive tree-removal operations, which caps workflow clarity.

Suggestions

Add an explicit validation step to the remove workflow, e.g. "After remove, run `git forest list` to confirm the tree is gone and check `git worktree list` for leftover entries."

Before showing `git forest remove -f`, add a guardrail/checkpoint reminding to confirm or stash uncommitted changes, since force-remove discards work.

Add brief executable examples for `git forest clone`, `git forest migrate`, and `git forest init`, and a one-line `~/.workforest.yaml` config snippet showing `fatTrees: true`, so every table command has a concrete example.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude knows git worktrees, opening with a brief comparison and compact command table; a few facts are restated across sections (e.g. "The forest root is NOT a git repo" appears in multiple places), keeping it just short of a fully lean score 5.	4 / 5
Actionability	Provides copy-paste-ready commands with realistic pwd context and predicted output (git forest add/remove/remove -f), but clone, migrate, and init appear only in the table without examples and the fatTrees config is mentioned without a full config snippet, leaving minor gaps versus a score 5.	4 / 5
Workflow Clarity	Structure and a built-in guard ("refuses if dirty") exist, but destructive/batch tree-removal operations lack explicit Claude-performed validation checkpoints or feedback loops, so per the rubric's destructive-operations cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Self-contained with no external bundles and clear section headers throughout, with no nested references or wall-of-text; at ~95 lines a couple of detail-heavy sections (list output, layout diagram) keep it just below the clean score 5 the simple-skill exception grants to very short self-contained skills.	4 / 5
	Total	15 / 20 Passed

Description

78%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 identifies a distinct niche and provides explicit "Use when" trigger guidance with concrete command keywords. It is slightly held back by a terse capability statement and somewhat trigger-driven framing rather than a comprehensive capability enumeration.

Dimension	Reasoning	Score
Specificity	Lists several concrete triggers ("git forest list", "git forest add", "git forest remove", "forest layout") plus the capability "managing worktrees with workforest", which exceeds the 1-2 actions of a score 3, though the capability framing is more trigger-driven than a comprehensive enumeration so it falls short of a 5.	4 / 5
Completeness	Answers both "what" ("managing worktrees with workforest") and "when" ("This skill should be used when..." / "Also use when...") with concrete trigger phrases, but the "what" statement is terse and embedded among triggers rather than a robust standalone capability list, keeping it below the score 5 anchor.	4 / 5
Trigger Term Quality	Covers natural phrasings a user would say ("workforest", "git forest", "managing worktrees", "navigate a forest", "how workforest works") with command variations, giving good keyword coverage; not a 5 because it lacks synonyms/file-extension-style terms and leans on exact command invocations rather than the broadest natural vocabulary.	4 / 5
Distinctiveness Conflict Risk	Targets a named tool (workforest) with its own command namespace ("git forest") and tool-specific triggers, giving it a clear niche with minimal overlap risk versus other skills.	5 / 5
	Total	17 / 20 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: dwmkerr/git-workforest
Path: plugins/git-workforest/skills/workforest/SKILL.md
Commit: 4b08fab

Reviewed: 4 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.