resume-session

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

Quality

70%

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

Quality

Content

75%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 content is well-structured and highly actionable with concrete commands, a clear workflow, and good error/fallback handling, held back mainly by command-form inconsistency, some repetition, and a tangential RFC footer section.

Suggestions

Reconcile the command form: explain or unify `ooo resume-session` vs `ouroboros resume` so Claude knows exactly what to run.

De-duplicate `ouroboros tui monitor` and the resume command, which each appear in Instructions, Fallback, Example, and Next Steps.

Add brief error-recovery guidance for exit codes 1 and 2 (e.g., re-prompt on invalid selection, check EventStore path/permissions on code 2), and consider folding the RFC #1392 footer rule into a concise inline note.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (no basic-concept padding), but `ouroboros tui monitor` is repeated across Instructions, Fallback, Example, and Next Steps, and the long ASCII example block could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands with placeholders for the common cases (inspect, monitor, resume) plus an exit-code table, but the inconsistency between `ooo resume-session` (Usage/How It Works) and `ouroboros resume` (Instructions) is a minor executable gap.	4 / 5
Workflow Clarity	The Instructions give a clear numbered sequence (run command, select session, pick re-attach path) with a no-sessions fallback and exit codes; it is read-only so no destructive-validation cap applies, but explicit error-recovery steps for exit codes 1/2 are absent.	4 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no nested references, and no bundle files exist to split out; the under-50-line exception for a 5 does not strictly apply, and the appended RFC #1392 footer section is a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

65%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 specific and distinctive, clearly conveying a niche read-only recovery task, but it lacks an explicit "Use when..." trigger clause and could include a few more natural trigger synonyms.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when an Ouroboros MCP server disconnects mid-run and you need to recover in-flight sessions.") to lift completeness above 3.

Broaden trigger terms with synonyms users might say, such as "reconnect", "lost session", or "MCP server disconnected".

Optionally enumerate the concrete re-attach paths in the description to push specificity from 2 actions toward fuller coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("in-flight Ouroboros sessions") and two concrete actions ("List" sessions and "show the commands needed to re-attach"), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The "what" is clear, but there is no explicit "Use when..." trigger clause; the "after MCP disconnect" condition is only weakly implied, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	It surfaces several natural domain terms a user would say ("in-flight Ouroboros sessions", "re-attach", "MCP disconnect"), giving good keyword coverage, though a few synonyms (e.g. "reconnect", "lost session") are absent.	4 / 5
Distinctiveness Conflict Risk	The description carves a clear niche tied to a specific tool and condition (Ouroboros session recovery after MCP disconnect) with distinct triggers and minimal overlap risk.	5 / 5
	Total	15 / 20 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: skills/resume-session/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.