CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

resume-session

List in-flight Ouroboros sessions and show the commands needed to re-attach after MCP disconnect

Quality

82%

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

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.

An exemplary lean skill body: concrete copy-paste commands with non-obvious behavioral notes (exit codes, prompt behavior, read-only guarantees) and a well-sequenced decision workflow covering found, not-found, and stuck-session outcomes. The only minor gaps are unhandled recovery paths for an unreadable EventStore or a missing Seed file.

DimensionReasoningScore

Conciseness

Nearly every token is operational detail Claude cannot know: "Exit code 2 means the EventStore exists but could not be read", "--list prints the table and exits without the interactive prompt, which aborts when no terminal is attached", and the read-only guarantees. Only the one-line naming rationale ("The name avoids shadowing Claude Code's built-in /resume") is trimmable, which is too minor for the anchor-4 'minor instances of over-explanation'.

5 / 5

Actionability

Fully executable, copy-paste-ready commands with flags: "ouroboros resume --list", "ouroboros status execution <exec_id> --events", "ouroboros tui monitor", "ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>", plus follow-ups "ooo evaluate" and "ooo cancel <session_id>". Placeholders are explicitly sourced ("Each row carries the session_id, exec_id, and Seed id"), and the found/not-found/stuck cases are all covered.

5 / 5

Workflow Clarity

Clear three-step sequence (list → ask the user which session → give the matching re-attach path) with outcome branches for "No in-flight sessions found" and exit code 2, and explicit next actions ("ooo evaluate once the execution completes, or ooo cancel <session_id> if it is stuck"). Not 5 because recovery for an unreadable EventStore (exit code 2) and a missing Seed file is explained-but-not-handled — minor validation gaps per anchor 4; the operations are read-only/non-destructive so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with no external reference files needed (no references/, scripts/, or assets/ exist), organized into clear sections (usage, Instructions with the three re-attach paths, breadcrumb footer). Per the rubric's simple-skill scoring note, well-organized sections alone merit 5 here.

5 / 5

Total

19

/

20

Passed

Description

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

A specific, third-person description with a clear 'what' and good domain keywords, undermined by the absence of any explicit 'when to use' trigger clause and missing natural synonyms like resume/reconnect. It is distinctive within the Ouroboros niche but slightly thin on the full range of actions the skill covers.

Suggestions

Add an explicit trigger clause, e.g., "Use when the Ouroboros MCP server disconnects unexpectedly and in-flight sessions need to be recovered."

Include natural synonyms users would say — "resume", "reconnect", "recover" — alongside "re-attach" to broaden trigger coverage.

Mention the additional actions the skill guides (interactive monitoring via `ouroboros tui monitor`, resuming execution from a Seed file) to raise specificity from two actions to several.

DimensionReasoningScore

Specificity

Names the domain and exactly two concrete actions ("List in-flight Ouroboros sessions", "show the commands needed to re-attach") but omits others the skill actually guides (monitoring, resuming execution, evaluating/cancelling). It is not 4 because 'several' specific actions are required, and not 2 because the actions given are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear (list sessions, show re-attach commands) but there is no 'Use when...' clause; "after MCP disconnect" only weakly implies when. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"Ouroboros sessions", "MCP disconnect", "re-attach", and "in-flight" are natural phrases a user would say when needing this skill. It falls short of 5 because the most likely user verbs — resume, reconnect, recover — are absent; better than 3 because coverage goes well beyond a single keyword.

4 / 5

Distinctiveness Conflict Risk

"Ouroboros" and "MCP disconnect" establish a clear niche with low conflict risk, but "sessions" and "re-attach" carry minor overlap with closely related session-resume skills (e.g., Claude Code's built-in /resume). Not 5 because that residual overlap with closely related skills exists; not 3 because the niche terms are far more specific than that anchor's example.

4 / 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/resume-session/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.