CtrlK
BlogDocsLog inGet started
Tessl Logo

brownfield

Scan and manage brownfield repository/worktree defaults for interviews

60

Quality

71%

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

88%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 content is highly actionable with fully executable tool calls and a clearly sequenced, validation-backed workflow including feedback loops for the destructive set_defaults operation. Its only real weakness is moderate verbosity in a few explanatory passages and a monolithic single-file structure that could split subcommand detail into reference files.

DimensionReasoningScore

Conciseness

The body is mostly efficient and instruction-focused with concrete tool calls and example outputs, though the deferred-schema guard and AskUserQuestion rationale include some extended explanatory prose that could be trimmed, landing it just above the midpoint between efficient and lean.

4 / 5

Actionability

It provides fully executable, copy-paste-ready guidance: exact MCP tool names and JSON arguments, CLI commands ('uvx --python ">=3.12" --from ouroboros-ai ouroboros detect [path]'), and concrete example outputs covering the common cases.

5 / 5

Workflow Clarity

The default flow is a clearly sequenced Step 1/2/3 process with explicit validation checkpoints (re-running tool discovery before every MCP call, parsing user replies with retry-on-garbage, error handling for detect failures) and feedback loops for the batch destructive set_defaults operation.

5 / 5

Progressive Disclosure

The single file is well-organized into Usage, How It Works, per-subcommand sections, and a footer section with no nested references, but all content lives in one ~240-line monolithic SKILL.md with no bundle files to offload the subcommand detail, leaving minor organization gaps.

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 specific to a clear niche and mostly distinct from other skills, but it lacks an explicit 'Use when' trigger clause and its action vocabulary ('manage') is somewhat generic, capping both completeness and specificity at the midpoint.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user asks to scan for existing git repos/worktrees or set default context repos for interviews').

Replace the generic verb 'manage' with concrete actions the skill performs, such as 'set, clear, and list default repos'.

Add natural trigger synonyms users might say, such as 'default repos', 'scan repositories', or 'brownfield scan'.

DimensionReasoningScore

Specificity

The description names the domain ('brownfield repository/worktree defaults') and two concrete actions ('Scan' and 'manage'), but 'manage' is generic and the action list is not comprehensive, matching the anchor that lists 1-2 concrete actions without full coverage.

3 / 5

Completeness

It gives a clear 'what' (scan and manage brownfield repo/worktree defaults for interviews) but has no explicit 'Use when...' trigger clause; per the judging guidelines a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant terms ('brownfield', 'repository', 'worktree', 'defaults', 'interviews') but misses common variations, synonyms, and file extensions, falling at the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The phrase 'brownfield repository/worktree defaults for interviews' carves out a clear niche with distinct triggers and only minor overlap risk with closely related repo-management skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Q00/ouroboros
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.