resume-session

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

Quality

72%

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 ./.claude-plugin/skills/resume-session/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with a clear, well-branching workflow and concrete commands, but it carries redundancy across sections and keeps everything inline with no progressive-disclosure structure. Trimming repeated content and either shortening or signposting the example/breadcrumb detail would improve conciseness and disclosure.

Suggestions

De-duplicate the read-only/no-MCP point and the two re-attach commands so each appears once, removing the repetition between "How It Works", "Instructions", and "Next Steps".

Move the large ASCII example box and the RFC breadcrumb-footer rules into a short reference or trim them, leaving the body a lean overview with the essential commands and steps.

Tighten the breadcrumb section to a one-line rule rather than a paragraph of derivation guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and domain-specific, but repeats the read-only/no-MCP point across "How It Works" and "Instructions", restates both re-attach commands in "Next Steps", and pads the RFC breadcrumb section with meta-process detail that could be tightened.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands (e.g. `ouroboros resume`, `ouroboros tui monitor`, `ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>`) plus a worked example with sample output, matching the fully-executable anchor.	3 / 3
Workflow Clarity	A clear numbered sequence (run command, enter selection, pick re-attach path) with an exit-code table and an explicit "Fallback (No sessions found)" branch gives feedback for error recovery; the operation is read-only so destructive-validation checkpoints are not required.	3 / 3
Progressive Disclosure	There are no bundle files and all content lives inline in one well-sectioned SKILL.md; sections are organized but nothing is split out, so it sits at the "could be better organized / inline" anchor rather than a clean overview-to-detail split.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and clearly distinct within its niche, but it omits an explicit "Use when..." trigger clause and offers a limited set of trigger-term variations. Adding a usage trigger and a couple more natural phrasings would raise completeness and trigger quality.

Suggestions

Append an explicit trigger clause such as "Use when an Ouroboros MCP server disconnects and you need to recover a running or paused execution".

Broaden trigger terms to include natural variations users might say, e.g. "lost Ouroboros execution", "resume paused run", "MCP server dropped".

Dimension	Reasoning	Score
Specificity	"List in-flight Ouroboros sessions and show the commands needed to re-attach" names two concrete actions (list sessions, surface re-attach commands) rather than vague language, matching the multiple-specific-actions anchor.	3 / 3
Completeness	The description clearly states what it does, but "when" is only implied via "after MCP disconnect" with no explicit "Use when..." trigger clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Terms like "in-flight Ouroboros sessions", "re-attach", and "MCP disconnect" are relevant but few; coverage lacks common phrasing variations compared to the multi-term good example.	2 / 3
Distinctiveness Conflict Risk	The Ouroboros/MCP-disconnect niche is highly specific with distinct triggers, making conflict with unrelated skills unlikely.	3 / 3
	Total	10 / 12 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: .claude-plugin/skills/resume-session/SKILL.md
Commit: f09fa36

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