CtrlK
BlogDocsLog inGet started
Tessl Logo

session-recovery

Find and resume interrupted Copilot CLI sessions using session_store queries

58

Quality

68%

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

82%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 highly actionable with copy-paste SQL recipes and a concrete resume command, well-organized into clear sections, with only minor conciseness trims and implicit validation checkpoints leaving it just short of top marks.

DimensionReasoningScore

Conciseness

The body is efficient with concrete SQL recipes and only brief, domain-specific context (e.g. why automated sessions must be filtered); a few introductory lines could be trimmed but overall it assumes Claude's competence, fitting the efficient/minor-trim anchor.

4 / 5

Actionability

All seven patterns are complete, executable SQL queries plus a concrete resume command ("copilot --resume SESSION_ID"), copy-paste ready and covering the common recovery cases, matching the fully executable anchor.

5 / 5

Workflow Clarity

The Examples give a clear numbered sequence (query -> find session -> check last checkpoint -> resume) and patterns include state-checking steps, but validation checkpoints are implicit rather than explicit feedback loops, fitting clear sequence with minor validation gaps.

4 / 5

Progressive Disclosure

Content is well-organized into Context, Patterns, Examples, and Anti-Patterns with numbered, navigable sections and no nested references; since the seven inline SQL recipes could arguably live in a separate reference file, this is good structure with minor organization gaps rather than a fully split overview.

4 / 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 specific and clearly identifies a distinct niche, but it lacks an explicit "Use when..." trigger clause and broader natural-language trigger terms, capping completeness and trigger quality at the midpoint.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers, e.g. "Use when a Copilot CLI session crashed, was closed, or left work unfinished and you need to locate and resume it."

Broaden trigger terms with natural synonyms users would say ("recover crashed session", "lost work", "resume interrupted session") to improve trigger term quality.

Optionally add a third concrete action (e.g. "detect orphaned issue work") to lift specificity above 3.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("Find and resume ... sessions using session_store queries") but offers only two actions rather than several, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It clearly states what the skill does but provides no explicit "Use when..." trigger guidance, so per the rubric cap completeness is held at 3 for a clear what with missing/weakly-implied when.

3 / 5

Trigger Term Quality

Phrases like "interrupted Copilot CLI sessions" and "resume" are relevant and somewhat natural, but common variations or synonyms (e.g. "recover", "crashed session", "lost work") are missing, matching the anchor for some relevant keywords missing variations.

3 / 5

Distinctiveness Conflict Risk

The niche (interrupted Copilot CLI sessions queried via session_store) is mostly distinct with only minor overlap risk against general git or issue-management skills, fitting the anchor for mostly distinct with minor overlap.

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.

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.