ouroboros-status

Check session status and measure goal drift

Quality

60%

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

Quality

Content

67%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 body is a well-structured, mostly actionable instruction skill with clear sequencing, concrete MCP tool invocations, and a useful worked example. Its main weakness is verbosity in the tool-loading preamble and some duplicated breadcrumb guidance.

Suggestions

Tighten the 'Load MCP Tools' section: collapse the repeated 'You MUST' / 'IMPORTANT' emphasis into a single concise instruction to reduce padding.

Specify how to obtain current_output and seed_content (e.g., where the seed YAML lives) so the drift-measurement call is fully executable rather than placeholder-driven.

Merge the duplicate breadcrumb guidance: the 'State breadcrumb' inline list and the 'RFC #1392 State Breadcrumb Footer' section restate the same requirement and could be consolidated.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete tool calls, but the deferred-tool loading section is padded with repeated emphasis ('You MUST', 'IMPORTANT: Do NOT skip') and conceptual explanation that could be tightened.	3 / 5
Actionability	It names exact MCP tools and their argument structures with a worked example output, giving mostly executable guidance; minor gaps remain where arguments like current_output/seed_content are left as placeholders.	4 / 5
Workflow Clarity	Status steps are clearly numbered with tool-availability checks and a fallback path, and the drift-threshold table acts as a checkpoint; it is a read-only skill so the destructive-cap does not apply, but it lacks explicit feedback loops for a 5.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Usage, How It Works, Instructions, Drift Thresholds, Fallback, Example) with no nested references and no bundle files; the repeated RFC breadcrumb footer is a minor organization blemish keeping it below 5.	4 / 5
	Total	15 / 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 concise and third-person with two concrete actions, but it omits any 'Use when...' trigger guidance and only partially covers natural trigger phrasing. It is a competent but incomplete description that should add an explicit when-to-use clause.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers, e.g. 'Use when the user asks am I drifting?, wants session status, or needs a drift check.'

Include natural-sounding synonyms users would actually say (e.g. 'am I drifting?') rather than only the technical 'goal drift'.

Optionally surface a third concrete capability to lift specificity from two actions toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and two concrete actions ('Check session status' and 'measure goal drift'), matching the anchor for 1-2 concrete actions without comprehensive coverage; it does not list several actions so it is not a 4.	3 / 5
Completeness	It gives a clear 'what' (check status, measure drift) but no 'when'/Use-when clause; per the guidelines a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	'session status' and 'goal drift' are relevant keywords, but it misses the natural user phrasing ('am I drifting?') that the body actually relies on, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	'session status' and 'goal drift' denote a fairly niche concept with minimal overlap risk, but it is not so uniquely phrased as to be conflict-free against general status-check skills, so it sits below 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Q00/ouroboros
Path: skills/status/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.