CtrlK
BlogDocsLog inGet started
Tessl Logo

session-recovery

Find and resume interrupted Copilot CLI sessions using session_store queries

49

Quality

53%

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 ./.squad/skills/session-recovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is highly actionable with executable SQL for every pattern and clean organization, but it slightly over-explains context and lacks an explicit validation checkpoint before the resume step despite flagging that risk in its anti-patterns.

Suggestions

Add an explicit validation step before resuming: query the last checkpoint / completion status and only run `copilot --resume` when the session has pending work, mirroring the anti-pattern guidance.

Trim the Context paragraph to one or two sentences since the tool definition and queries already convey the session_store setup.

Consider extracting the full-context inspection queries (Pattern 5) into a reference script once the skill grows, keeping SKILL.md lean.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it leads with actionable SQL patterns and avoids explaining what SQLite or Copilot is — but the Context section restates setup that the tool listing and queries already imply, and a few prose sentences could be trimmed without losing clarity.

2 / 3

Actionability

Every section provides complete, executable SQL (or a `copilot --resume` command) that is copy-paste ready, with concrete table names, columns, and filtering logic rather than pseudocode.

3 / 3

Workflow Clarity

The patterns are individually sequenced and the 'Get Full Session Context Before Resuming' step acts as a soft checkpoint, but for destructive/resume operations there is no explicit validate-then-act feedback loop (e.g., confirm the session is not already complete before resuming), which caps clarity at 2 given the anti-pattern about resuming completed sessions.

2 / 3

Progressive Disclosure

No bundle files are present and the skill is a single self-contained overview with well-organized sections (Patterns, Examples, Anti-Patterns), so per the rubric's simple-skill guidance a clean one-level structure with no nested references scores 3.

3 / 3

Total

10

/

12

Passed

Description

35%

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 states a clear domain and single action but lacks natural trigger terms, a 'Use when...' clause, and a comprehensive action list, leaving it somewhat generic despite the specific Copilot/session_store framing.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when a Copilot CLI session crashed, network dropped, or the user wants to resume yesterday's interrupted work').

Broaden the action list to match the body's capabilities (e.g., 'find interrupted sessions, search by topic or working directory, detect orphaned issue work, and resume sessions').

Replace jargon-only phrasing with user-natural terms like 'recover interrupted work' or 'resume a crashed session'.

DimensionReasoningScore

Specificity

The description names a concrete action ('resume interrupted Copilot CLI sessions') and the mechanism ('using session_store queries'), but it lists only one action and omits the breadth of capabilities the body demonstrates (FTS5 search, filtering automated sessions, orphaned-issue detection), so it is not a comprehensive set of specific actions as required for a 3.

2 / 3

Completeness

It clearly states what the skill does ('Find and resume interrupted Copilot CLI sessions'), but there is no 'Use when...' clause or equivalent explicit guidance on when to invoke it, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

The phrasing relies on technical jargon ('Copilot CLI sessions', 'session_store queries') rather than the natural words a user would actually say when they need this skill (e.g., 'find interrupted work', 'recover my last session', 'resume a crashed session').

1 / 3

Distinctiveness Conflict Risk

The Copilot CLI session-recovery niche is fairly specific, but the lack of distinct trigger phrasing and the generic 'find and resume' wording means it could still overlap with other session- or recovery-oriented skills.

2 / 3

Total

7

/

12

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.

Validation15 / 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
bradygaster/squad
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.