config

Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback)

Quality

71%

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

Quality

Content

85%

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 and well-structured with clear branch-based sequencing, validation, and error-recovery guidance, all self-contained with no need for external references. The only tightening opportunity is the duplicated state-breadcrumb footer specification.

Suggestions

Consolidate the breadcrumb-footer guidance: keep the formal "RFC #1392" spec and reduce the inline "All branches" mention to a one-line pointer to avoid stating the requirement twice.

Dimension	Reasoning	Score
Conciseness	The body is direct and assumes Claude's competence with no concept explanations, but the state-breadcrumb footer is specified twice — inline in "All branches" with two examples and again as a full "RFC #1392" section — which could be tightened into one.	2 / 3
Actionability	Every branch gives copy-paste-ready commands (e.g., `ouroboros config --web --host 0.0.0.0 --no-browser`, `ouroboros config set clarification.default_model <model>`) with placeholders clearly marked, fully executable.	3 / 3
Workflow Clarity	Three clearly sequenced branches with numbered steps include validation checkpoints (`ouroboros config show` to confirm) and error-recovery feedback (relay rejected-set and missing-dependency errors verbatim).	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single-purpose skill is well-organized into Usage, Instructions, branches, and footer sections with no nested references or monolithic wall of text.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 names a concrete domain and interface modes and is clearly distinct, but it omits an explicit "Use when..." trigger clause and packs most natural keywords into the body rather than the description field. Adding a trigger clause and a couple of user-facing keywords would lift the two capped dimensions.

Suggestions

Append a "Use when..." trigger clause to the description (e.g., "Use when the user asks to open or change Ouroboros settings, switch the runtime/model backend, or configure agents") so completeness can reach 3.

Surface natural trigger terms in the description itself — "config", "configure", "change model", "change agent" — rather than only in the body's Trigger keywords list.

List one or two more concrete actions (e.g., "show, set, and validate config") to broaden the specificity beyond "open or drive".

Dimension	Reasoning	Score
Specificity	"Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback)" names the domain and a couple of actions (open, drive) plus three interface modes, but the action list is thin compared to the multi-action anchor-3 example.	2 / 3
Completeness	It states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance in the description, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"settings" is a natural term a user would say, but coverage is incomplete and "TUI" / "conversational fallback" are jargon; common variations like "config", "configure", "change model" live only in the body, not the description.	2 / 3
Distinctiveness Conflict Risk	The phrase is anchored to the specific Ouroboros settings GUI, giving it a clear niche unlikely to trigger for unrelated skills.	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: skills/config/SKILL.md
Commit: f09fa36

Reviewed: about 2 hours 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.