CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brownfield

Scan and manage brownfield repository/worktree defaults for interviews

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/brownfield/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

90%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 lean, highly actionable skill file: exact MCP/CLI invocations, literal output formats, and explicit reply-parsing rules leave little ambiguity about what to do in each flow. The only notable weaknesses are the missing index-validation before the destructive `set_defaults` batch replacement and a single-file structure that is slightly heavier than the ideal overview-only SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific operational facts Claude could not know (e.g. "Only `scan` walks the disk", "at most two directory levels deep", "text between tool calls may not render, and dialog previews truncate long lists") and contains essentially no explanation of known concepts. Every section earns its tokens; no padded passages found.

5 / 5

Actionability

It gives copy-paste-ready tool calls with exact arguments ("{ \"action\": \"query\" }") and exact CLI commands ("uvx --python '>=3.12' --from ouroboros-ai ouroboros detect [path]"), plus literal response strings to display ("No git repositories or worktrees found.") and concrete reply-parsing rules covering normal, keep/none, and invalid-input cases.

5 / 5

Workflow Clarity

The default flow is a clear 3-step sequence with decision points ("If `meta.total` is 0 ... run the scan below") and an error-recovery loop ("anything else → ask again in plain text, never guess"), and `detect` has a failure path ("could not propose any verifiable commands"). Minor gap: `set_defaults` is a destructive batch replacement ("it replaces every existing default") with no explicit pre-call check that the replied numbers map to registered repos, though it does warn and confirm afterward.

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced; the body is well-sectioned (Loading MCP tools, Default flow steps, Subcommands, Footer) and stays a single level deep. It is ~100 lines of inline detail (scan boundaries, find ranking rules), slightly beyond the under-50-line single-file ideal, so a small amount of content (e.g. scan-boundary or detect specifics) could arguably live in reference files.

4 / 5

Total

18

/

20

Passed

Description

53%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 short, third-person, and names a distinctive domain, but it under-sells the skill: one verb is generic, the concrete subcommands are absent, and — most importantly — there is no 'Use when...' trigger guidance. It is a clear 'what' with a missing 'when', which caps its usefulness for skill selection.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions brownfield repositories, existing/registered repos, worktrees, or setting default interview context repos".

Replace the generic "manage" with the concrete capabilities: "List registered repos, rescan the disk for repos and worktrees, rank repos by topic, set default repos, and author mechanical.toml".

Include natural synonyms users would actually say ("existing repos", "default repos", "interview context") so retrieval matches more than the single jargon term "brownfield".

DimensionReasoningScore

Specificity

It names a concrete domain ("brownfield repository/worktree defaults for interviews") and one concrete action ("Scan"), but "manage" is generic and the description never enumerates the actual capabilities (list, defaults, find, set, detect). Fits 'Names domain and 1-2 concrete actions, but not comprehensive'; not 4 because no specific action list is present, not 2 because the domain and 'scan' are concrete.

3 / 5

Completeness

The 'what' is stated (scan and manage brownfield repo/worktree defaults for interviews) but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4 because the trigger half is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Relevant domain keywords exist ("Scan", "brownfield", "repository", "worktree", "defaults", "interviews") but common user phrasings and synonyms are missing — e.g. 'existing repos', 'registered worktrees', 'default interview repos'. Matches 'Some relevant keywords but missing common variations or synonyms'; not 4 because coverage is one generic sentence with no synonyms or extensions.

3 / 5

Distinctiveness Conflict Risk

The niche 'brownfield repository/worktree defaults for interviews' is quite specific and unlikely to fire for unrelated skills. Not 5 because the generic verb pair 'Scan and manage' plus the unusual 'brownfield' jargon leaves some overlap risk with general repo-management skills; not 3 because the domain qualifier is genuinely distinctive.

4 / 5

Total

13

/

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

Q00/ouroboros

Path

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