CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ouroboros-config

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

Quality

80%

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/config/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

This is a strong, tight operational skill: concrete commands in every branch, a crisp decision question, validation via `config show` plus error relay and undo, and no wasted tokens. The only shortfall is the absence of fix-and-retry guidance after a rejected `set`, which leaves workflow_clarity just below the top anchor.

DimensionReasoningScore

Conciseness

The body is dense and directive throughout — "Pick the branch by one question", "Do not start a server nobody can reach", the exact footer line — with zero concept explanations or padding. Every token earns its place, matching anchor 5; nothing can be trimmed without losing an instruction.

5 / 5

Actionability

All guidance is copy-paste executable: the `if command -v ouroboros...` launch block with uvx fallback, `ouroboros config --web --host 0.0.0.0 --no-browser`, a full `ouroboros config set ...` setter menu, `config show`, and `config undo`. The commands cover the common cases across all three branches, matching anchor 5.

5 / 5

Workflow Clarity

Sequencing is explicit (one branch-selection question, numbered steps per branch, "Confirm with `ouroboros config show`") with validation checkpoints and an undo recovery path. It falls one short of anchor 5 because a rejected `set` is only relayed verbatim — there is no fix-and-retry loop guidance for error recovery.

4 / 5

Progressive Disclosure

The skill is self-contained (~68 lines) with no bundle files (no references/, scripts/, or assets/ exist) and no content that belongs in separate files; sections (## Instructions, ### Branch A-C, ### All branches) are well-organized and easy to navigate, so the no-external-references exception applies cleanly.

5 / 5

Total

19

/

20

Passed

Description

57%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 concise, third-person, and names a distinct product surface, but it reads more like a title than a trigger: it has a clear 'what' with no 'when', and its keyword coverage misses the natural phrases (config, configure, change model/backend) a user would say. It is serviceable but well short of the good examples' standard.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to view or change Ouroboros settings/configuration (runtime, models, backend) or mentions 'ouroboros config'."

Include the natural user vocabulary — 'config', 'configure', 'change the default model', 'switch backend' — as trigger terms alongside 'settings'.

Enumerate 2-3 concrete editable targets (per-stage runtimes/models, LLM backend, env-override warnings) to lift specificity beyond a single 'open or drive' action.

DimensionReasoningScore

Specificity

"Open or drive the Ouroboros settings GUI" names the domain and 1-2 concrete actions (open, drive) across three modes (browser, TUI, conversational fallback), but does not enumerate the editable settings (runtimes, models, LLM backend) that the body covers. It sits at anchor 3: not 4 because it lacks a list of several specific actions, not 2 because the domain is named and actions are concrete.

3 / 5

Completeness

The description has a clear 'what' ("Open or drive the Ouroboros settings GUI") but no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "settings", "GUI", "browser", and "TUI" are relevant, but common natural variations a user would say ("config", "configure", "change the model") are absent. This matches anchor 3 (some relevant keywords, missing common variations or synonyms) rather than 4.

3 / 5

Distinctiveness Conflict Risk

"Ouroboros settings GUI" names a specific product's settings surface with distinct triggers (settings, GUI, config modes); it is a clear niche with minimal conflict risk against other skills. Anchor 5 fits; nothing generic remains to overlap.

5 / 5

Total

14

/

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/config/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.