CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ac-workspace-manager

Manage git worktrees for isolated development. Use when creating isolated workspaces, managing parallel development, handling worktree lifecycle, or merging completed work.

Quality

81%

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

SKILL.md
Quality
Evals
Security

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.

A compact, well-structured overview with executable quick-start code and a verified one-level-deep reference to the implementation script. Its main weakness is the destructive merge/cleanup workflow lacking explicit validation checkpoints, plus minor redundancy between the intro, Purpose, and duplicated API sections.

Suggestions

Add explicit validation before merging: e.g., a step like 'Run tests in the worktree, then check for merge conflicts before calling merge_completed(worktree)'.

Verify merge success before cleanup: state that cleanup_worktree should only run after merge_completed returns true, covering the destructive cleanup step.

Consolidate the duplicate '## API' and '## API Reference' sections into one, and trim the Purpose section that repeats the description, folding the unexplained 'safe rollback' claim into an actual usage note.

DimensionReasoningScore

Conciseness

The body is largely lean (terse API examples, a compact tree diagram), but the intro line and the Purpose section redundantly restate the frontmatter description, and 'safe rollback without affecting the main branch' claims a capability the body never elaborates — minor trimmable instances consistent with the efficient-with-minor-excess anchor.

4 / 5

Actionability

The Quick Start is real executable async code ('from scripts.workspace_manager import WorkspaceManager', 'await manager.create_worktree("feature-auth")') and every inline API call matches an actual method in the bundle script, but project_dir's provenance is undefined, there is no error-handling example, and script methods switch_to_worktree/sync_with_main are undocumented — mostly executable with minor gaps.

4 / 5

Workflow Clarity

The five-step sequence (Create, Develop, Review, Merge, Cleanup) is clearly ordered, but merging back to main and removing worktrees are destructive/batch operations with no explicit validation commands (no test run, conflict check, or merge-success verification before cleanup); 'Review: Review changes before merge' names a checkpoint without saying what to validate, so the destructive-operations cap applies.

3 / 5

Progressive Disclosure

The body is a concise overview pointing one level deep to a real bundle file ('See scripts/workspace_manager.py for full implementation'), but the duplicated '## API' and '## API Reference' headings, with the inline API list partially duplicating the script, are minor organization gaps rather than the cleanly split structure of the top anchor.

4 / 5

Total

15

/

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.

A strong description that states the domain, several concrete capabilities, and an explicit multi-trigger 'Use when' clause in the recommended good-example pattern. Its only weaknesses are slightly generic phrasing in a couple of triggers and missing natural synonyms like 'branch isolation'.

DimensionReasoningScore

Specificity

Names the domain ('Manage git worktrees') and lists several specific actions ('creating isolated workspaces, managing parallel development, handling worktree lifecycle, or merging completed work'), though some like 'managing parallel development' are broad rather than concrete, fitting the several-actions-with-minor-gaps anchor.

4 / 5

Completeness

Clearly answers 'what' ('Manage git worktrees for isolated development') and 'when' with an explicit 'Use when' clause listing concrete triggers, matching the anchor-5 pattern of the good examples.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ('git worktrees', 'isolated workspaces', 'parallel development', 'merging') with good coverage, but misses common variations such as 'branch isolation' or 'isolated checkout', so it does not reach comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'git worktrees' carves a clear niche with distinct triggers, but generic phrases like 'creating isolated workspaces' and 'managing parallel development' carry minor overlap risk with broader workspace or branch-management skills, so it is mostly distinct rather than minimal-conflict.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

fernandezbaptiste/Skrillz

Path

skills/ac-workspace-manager/SKILL.md

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.