brownfield

Scan and manage brownfield repository/worktree defaults for interviews

Quality

67%

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-plugin/skills/brownfield/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clearly sequenced, validated workflow and copy-paste-ready commands. Its main weaknesses are a body that could be tightened and a lack of progressive disclosure into reference files despite its length.

Suggestions

Tighten the deferred-schema guard block and consolidate the repeated tool-discovery re-load instructions into one stated rule with shorter per-call reminders to improve conciseness.

Split the longer subcommand details (e.g. detect, scan boundaries) into reference files linked from a concise overview to improve progressive disclosure.

Add an explicit pre-flight verification note before the destructive set_defaults clear (e.g. confirming the parsed indices against the displayed list) to make the batch operation's checkpoint unmistakable.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational instruction with no basic-concept padding, but the lengthy deferred-schema guard block and repeated tool-discovery re-load instructions could be tightened, matching 'mostly efficient but could be tightened'.	2 / 3
Actionability	It provides exact MCP call arguments (e.g. `{ "action": "set_defaults", "indices": "6,18,19" }`), concrete CLI commands (`uvx --from ouroboros-ai ouroboros detect [path]`), and copy-paste-ready display formats, matching 'fully executable code/commands'.	3 / 3
Workflow Clarity	The default flow is a clear 3-step sequence (Scan, Default Selection, Confirmation) with validation paths (no repos found, invalid-input retry loop) and a post-action confirmation, matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but the ~225-line body is entirely inline with no file-level references and no bundle files present, fitting 'content that should be separate is inline'.	2 / 3
	Total	10 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 occupies a distinct niche, but it stops at naming a domain and a couple of actions without explicit trigger guidance or a comprehensive action list. It is solid but leaves the 'when to use' implicit.

Suggestions

Expand the action list beyond "scan and manage" to concrete behaviors (e.g. "scan, list, set, and clear default repositories") to lift specificity.

Add an explicit trigger clause such as "Use when preparing interview context from existing repos or managing brownfield defaults" to raise completeness.

Include more natural user phrasings (e.g. "scan repos", "set default repos") in the description itself rather than only in the body's trigger keywords.

Dimension	Reasoning	Score
Specificity	Names the domain and two verbs ("Scan and manage brownfield repository/worktree defaults"), but "manage" is broad rather than a list of multiple specific concrete actions, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It clearly states what the skill does ("Scan and manage ... defaults for interviews") but offers no "Use when..." or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	"brownfield", "repository", "worktree", "defaults" are relevant terms but lean toward jargon and miss common user phrasings, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	"brownfield repository/worktree defaults for interviews" carves out a clear, narrow niche unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 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: Q00/ouroboros
Path: .claude-plugin/skills/brownfield/SKILL.md
Commit: f09fa36

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