ouroboros-config

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

Quality

74%

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

86%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 a well-structured, highly actionable skill with executable commands across three well-chosen deployment branches and clear validation/error-relay feedback. The only real gap is conciseness polish and an explicit validate-retry loop on the GUI path.

Dimension	Reasoning	Score
Conciseness	The body is dense and purposeful with copy-paste commands and no padding about concepts Claude already knows; only minor explanatory passages around the breadcrumb footer keep it from a 5.	4 / 5
Actionability	Every branch provides fully executable bash commands with concrete key paths (e.g. `ouroboros config set clarification.default_model <model>`), covering the common cases copy-paste ready.	5 / 5
Workflow Clarity	Branches A/B/C are clearly sequenced with numbered steps and a confirm-with-`config show` checkpoint plus a verbatim-error relay feedback loop; a small validation gap on the GUI path (no explicit validate-then-retry) keeps it at 4.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md is appropriately organized into clear, navigable sections (Usage, Instructions, Branches, All branches, RFC footer); per the rubric's simple-skill note this qualifies for a 5.	5 / 5
	Total	18 / 20 Passed

Description

62%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 clearly states the what and names a distinctive niche with concrete modalities, but it lacks an explicit when/Use-when trigger clause and natural user-facing trigger synonyms. Adding a "Use when…" clause with terms like "configure ouroboros" or "change model/agent" would lift the weakest dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to configure Ouroboros settings, change the model or agent, or open the settings GUI."

Add natural trigger synonyms users actually say ("configure ouroboros", "change model", "change agent", "open settings") so the description matches the keywords already listed in the body.

Consider third-person active verbs ("Opens or drives…") and confirm the description stands alone without relying on the body's trigger-keyword line.

Dimension	Reasoning	Score
Specificity	Names two concrete actions ("Open or drive") and three modalities (browser, TUI, conversational fallback), but coverage is not comprehensive enough for a 5.	4 / 5
Completeness	The "what" is clear (open/drive the settings GUI) but there is no explicit "when" / "Use when" clause, which the rubric caps at 3.	3 / 5
Trigger Term Quality	"settings GUI" is a moderately natural phrase but the description omits common user variations like "configure", "change settings", or synonyms; no "Use when" trigger clause.	3 / 5
Distinctiveness Conflict Risk	"Ouroboros settings GUI" is a clear, narrow niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	15 / 20 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: 80333ae

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