moai-workflow-worktree

Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.

Quality

53%

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 ./.claude/skills/moai-workflow-worktree/SKILL.md

Quality

Content

38%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 skill is well-structured into tiers (Quick Reference / Implementation Guide / Advanced) and includes a verification section, but it is verbose, favors prose over executable commands, and relies heavily on module references that are missing from the bundle.

Suggestions

Replace the prose command descriptions with actual executable invocations (e.g. `moai-worktree new SPEC-001 "description"`) so the Implementation Guide is copy-paste ready.

Either create the referenced modules/worktree-*.md files or remove the broken 'Refer to modules/...' links, since those paths do not exist in the bundle.

Trim the conceptual restatement of git worktree basics and the duplicate Quick Reference summary to reduce padding and respect the context budget.

Add explicit inline validation checkpoints (e.g. verify `git worktree list` after create, confirm sync success before clean) to the workflow steps rather than relying solely on the closing checklist.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose, restating concepts Claude already knows (registry structure, file structure, what a worktree is) in long prose paragraphs and repeating the description in 'Quick Reference'; section 5 is the only lean portion.	2 / 5
Actionability	CLI commands are described in English prose ('use the new command followed by the SPEC ID') rather than shown as executable invocations, and most code lives in references; only section 5 provides copy-paste-ready bash, leaving guidance incomplete.	3 / 5
Workflow Clarity	Plan/Develop/Sync/Cleanup phases are sequenced and a verification checklist closes the doc, but inline validation checkpoints for the destructive/batch operations (sync, remove, clean) are absent or only implicit.	3 / 5
Progressive Disclosure	Repeated references to modules/*.md (worktree-commands.md, worktree-management.md, etc.) point to files that do not exist in the bundle, while the real examples.md and reference.md are correctly signaled, so navigation is partly broken.	2 / 5
	Total	10 / 20 Passed

Description

67%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 is specific and complete with both a clear capability statement and an explicit trigger clause, establishing a distinct niche. It is held back by somewhat jargony trigger terms and a 'when' clause that could enumerate more concrete triggering scenarios.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('worktree management', 'parallel SPEC development', 'isolated workspaces', 'automatic branch registration', 'MoAI-ADK integration'); not quite comprehensive enough for a 5.	4 / 5
Completeness	Has both a clear 'what' (worktree management with enumerated features) and an explicit 'when' ('Use when setting up parallel development environments'); the trigger could be more specific/varied.	4 / 5
Trigger Term Quality	Relevant terms like 'parallel development' and 'worktree' are present, but the vocabulary is domain-jargony (SPEC, MoAI-ADK) and misses common synonyms or variations users would naturally say.	3 / 5
Distinctiveness Conflict Risk	The MoAI-ADK / SPEC niche gives it a clear identity distinct from generic git skills, with only minor overlap risk against closely related workflow skills.	4 / 5
	Total	15 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: modu-ai/moai-adk
Path: .claude/skills/moai-workflow-worktree/SKILL.md
Commit: 4100d87

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