Name: auto-claude-workspace
Rating: 65.60000000000001 (1 reviews)
Author: fernandezbaptiste

auto-claude-workspace

Auto-Claude workspace and git worktree management. Use when reviewing changes, merging builds, managing branches, or understanding isolation strategy.

Quality

79%

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/auto-claude-workspace/SKILL.md

The canonical home for this skill is auto-claude-workspace in fernandezbaptiste/Skrillz

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 highly actionable with executable commands and clear validation-gated merge practices, and is well-structured for navigation. Its main weaknesses are duplicated merge-conflict guidance across sections and a long single-file form where troubleshooting/manual-ops content could be offloaded to reference files.

Suggestions

Consolidate the three repeated merge-conflict passages (Conflict Resolution, Troubleshooting, Best Practices) into one canonical section and cross-reference it, cutting roughly 30-40 lines.

Move Troubleshooting and Manual Worktree Operations into a separate reference file (e.g. references/troubleshooting.md) and link from SKILL.md to reduce inline token load.

Turn the Discard Build flow into an explicit validate->confirm->discard loop (list what will be deleted, confirm, then remove) so the destructive path matches the validation rigor of the merge flow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's intelligence (no over-explanation of what a worktree is), but merge-conflict guidance is repeated across 'Conflict Resolution', 'Troubleshooting > Merge Conflicts', and 'Best Practices > Before Merging', and the 'cd ../../apps/backend' return pattern is restated several times, so it could be tightened; not a 4 because the duplication is noticeable rather than minor.	3 / 5
Actionability	Dense with copy-paste-ready, executable commands (e.g. 'python run.py --spec 001 --merge', 'git worktree add .worktrees/experiment -b experiment-branch') and concrete JSON metadata examples covering the common review/test/merge/discard/troubleshoot cases, matching the top anchor.	5 / 5
Workflow Clarity	Merge and discard workflows are numbered and the 'Before Merging' checklist provides explicit validation checkpoints (review, test, diff for conflicts) plus post-merge verification; not a 5 because the destructive 'Discard Build' relies on a confirmation prompt rather than a verify-then-confirm loop, and conflict-resolution feedback loops are described rather than structured as validate->fix->retry.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but it is well-organized with clear hierarchical section headers and a 'Related Skills' pointer to companion skills, making navigation easy; not a 5 because sizable sections (Troubleshooting, Manual Worktree Operations) are natural candidates for separate reference files and would benefit the context budget if split out.	4 / 5
	Total	16 / 20 Passed

Description

83%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 cleanly answers both what and when with concrete, third-person trigger phrases and a well-scoped niche. It is slightly thin on synonyms and enumerates actions at a high level rather than comprehensively.

Dimension	Reasoning	Score
Specificity	Names the domain ('Auto-Claude workspace and git worktree management') plus four concrete actions — 'reviewing changes, merging builds, managing branches, or understanding isolation strategy' — matching the several-specific-actions anchor; not a 5 because 'understanding isolation strategy' is somewhat abstract and coverage of the full merge/discard lifecycle is implied rather than enumerated.	4 / 5
Completeness	Explicitly states both what it does ('Auto-Claude workspace and git worktree management') and when to use it ('Use when reviewing changes, merging builds, managing branches, or understanding isolation strategy') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	'reviewing changes', 'merging builds', 'managing branches' are natural phrases a developer would say, giving good keyword coverage; not a 5 because synonyms and concrete artifacts (e.g. 'worktree', 'spec', 'auto-claude branch') are thin and 'merging builds' is a slightly unnatural phrasing.	4 / 5
Distinctiveness Conflict Risk	The 'Auto-Claude' + 'git worktree' framing carves a clear niche distinct from generic git skills; not a 5 because 'managing branches' and 'reviewing changes' overlap with general git/workflow skills, leaving minor conflict risk with closely related skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: .claude/skills/auto-claude-workspace/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.