CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ouroboros-status

Check session status and measure goal drift

Quality

72%

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

Quality

Content

78%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 compact, well-structured orchestration guide: concrete MCP call templates, an explicit pre-flight tool-discovery guard, threshold-driven branching, and a fallback path. Its only weaknesses are minor — an ambiguous discovery-string mapping for the drift tool and no explicit recovery step for a failed status call.

Suggestions

Clarify the tool-discovery mapping in the deferred-schema guard section: state the exact discovery string for ouroboros_measure_drift separately (e.g., '+ouroboros measure drift') rather than appearing to reuse '+ouroboros session status' for both tools.

Add one recovery branch to the workflow, e.g.: if a status or drift call fails after the schema is loaded, retry discovery once and only then report the error — this closes the validation gap that keeps workflow clarity below 5.

DimensionReasoningScore

Conciseness

The body is lean and operational — the deferred-schema guard, numbered steps, fallback, and footer policy all carry load-bearing instructions with no padding or explanations of concepts Claude already knows. Minor tightening is possible: step 4 compresses the render output plus both threshold branches into a single dense sentence, and the parenthetical "(or says 'am I drifting?')" could be folded into step 3's condition, so this fits the 4 anchor ('efficient; minor instances that could be trimmed') rather than the 5 anchor's 'every token earns its place'.

4 / 5

Actionability

The steps provide concrete, near-copy-ready MCP call templates with exact tool names and full argument lists (including placeholder defaults like 'constraint_violations: []'), a concrete discovery command '+ouroboros session status', and a specific threshold (0.3 / EXCEEDED) with named next commands (ooo interview, ooo evolve, ooo run, ooo evaluate). This fits the 4 anchor; it falls short of 5 because the discovery-string mapping lists one string '+ouroboros session status' ambiguously for two tools (ouroboros_session_status and ouroboros_measure_drift), leaving the reader to guess whether measure_drift has its own discovery invocation.

4 / 5

Workflow Clarity

The sequence is clear: an explicit session-resolution order (given ID → most recent → ask the user), a pre-flight schema-loading check, conditional drift measurement, and threshold-based branching with recommended next actions, plus an explicit no-MCP fallback section. This matches the 4 anchor ('clear sequence with most checkpoints present; minor validation gaps') — it is not a 5 because there is no error-recovery loop if a call fails mid-flow (the fallback only covers server absence, not a failed status call). No destructive or batch operations are involved, so the workflow-clarity cap of 3 does not apply.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are needed; the ~46-line body is well organized into clearly labeled sections (Instructions, Steps, Fallback, Footer) with no nested or buried references. Per the rubric's simple-skill exception — 'for skills under 50 lines with no need for external references, progressive disclosure can score 5 with just well-organized sections' — this earns a 5.

5 / 5

Total

17

/

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 names two concrete actions, but it omits any trigger guidance ('use when...'), which caps completeness, and its keyword coverage lacks natural variations users would say. It is serviceable but sits just below the level of the rubric's good examples.

Suggestions

Add an explicit trigger clause, e.g.: "Use when the user asks about an execution session's status, progress, or whether the work has drifted from the original Seed goal."

Include natural user phrasings as trigger terms — "am I drifting?", "still on track?", "session progress" — so the description matches how users actually ask for this skill.

Mention that it uses the Ouroboros MCP server's session tools, which sets expectations and further distinguishes it from generic status-reporting skills.

DimensionReasoningScore

Specificity

The description names the domain and exactly two concrete actions — "Check session status" and "measure goal drift" — which matches the anchor for 'names domain and 1-2 concrete actions, but not comprehensive' (e.g., 'Processes PDF files and extracts content'). It is not a 4 because two actions do not constitute 'several specific actions', and not a 2 because both actions are concrete rather than generic.

3 / 5

Completeness

The 'what' is clearly stated (check session status, measure goal drift) but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. This matches the anchor example 'Extract text and tables from PDF files, fill forms, merge documents' — clear what, missing when.

3 / 5

Trigger Term Quality

"session status" and "goal drift" are relevant keywords users of this system would plausibly say, but the description misses common variations and natural phrasings such as "on track", "am I drifting?", "progress", or "session check". This matches the anchor 'some relevant keywords but missing common variations or synonyms' rather than the 4 anchor's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

"goal drift" is a distinctive niche term tied to the Ouroboros system, but "Check session status" is a phrase a generic status/progress skill could equally claim, giving minor overlap risk with closely related skills. This fits the 4 anchor ('mostly distinct; minor overlap risk') better than 5 ('clear niche with distinct triggers'), since no distinct triggers are actually listed.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.