CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-recovery

Find and resume interrupted Copilot CLI sessions using session_store queries

Quality

80%

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 ./.github/skills/session-recovery/SKILL.md

The canonical home for this skill is session-recovery in FritzAndFriends/BlazorWebFormsComponents

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 seven complete executable SQL patterns, a coherent find-to-resume workflow, explicit pre-resume validation in the Examples, and protective Anti-Patterns. It is efficient and well organized, with only minor room for improvement: factoring out the repeated last_checkpoint subquery and adding a fallback path for when session matching or resume fails.

DimensionReasoningScore

Conciseness

The body is mostly lean: SQL-first patterns with one-line intros, and a Context section that stays skill-specific ("session_store" SQLite, read-only access via the sql tool) rather than explaining generic concepts. It falls short of anchor 5 because the correlated "last_checkpoint" subquery is repeated verbatim in patterns 1, 2, and 4, and the interruption-cause enumeration ("terminal crashes, network drops, machine restarts, or accidental window closes") could be trimmed; it is well above anchor 3 since there is no padding or teaching of things Claude already knows.

4 / 5

Actionability

Every pattern ships complete, executable SQL — time-window filters ("datetime('now', '-24 hours')"), a concrete FTS5 MATCH string with synonym expansion ("'auth OR login OR token OR JWT'"), correlated subqueries, and a NOT IN automated-session filter — plus the bash resume command ("copilot --resume SESSION_ID") and a "gh issue list --label "status:in-progress"" cross-check. This matches anchor 5: copy-paste ready commands covering the common cases, with placeholders clearly marked.

5 / 5

Workflow Clarity

The patterns form a logical find-to-resume sequence (find recent → filter automated noise → search → inspect full context → detect orphaned work → resume), and both Examples include an explicit pre-resume validation checkpoint ("Check its last checkpoint — was the code committed? Was the PR created?"), reinforced by Anti-Patterns ("Resuming sessions that completed successfully"). It matches anchor 4 rather than 5 because there are no feedback loops for error recovery (e.g., what to do when no session matches or a resume fails); the destructive/batch cap at 3 does not apply since the queries are read-only.

4 / 5

Progressive Disclosure

The single file is well structured with clear sections (Context → seven numbered Patterns → Examples → Anti-Patterns) and no nested or buried references; no bundle files exist, so there are no broken or dead reference paths. It matches anchor 4 rather than 5 because at ~140 lines all content is inline with no one-level-deep reference split — several repeated query variants could live in a separate reference file to keep the overview leaner — and it exceeds the simple-skill under-50-line threshold that would otherwise allow a 5 on organization alone.

4 / 5

Total

17

/

20

Passed

Description

70%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 highly distinctive, clearly conveying what the skill does and the mechanism it uses, with reasonably natural trigger language ("resume", "interrupted"). Its main weakness is the complete absence of a "Use when..." clause, which caps completeness at 3 despite it being the heaviest-weighted dimension, and it misses common user synonyms like "recover" or "crash".

Suggestions

Add an explicit trigger clause, e.g. "Use when a Copilot CLI session was interrupted by a crash, restart, or network drop, or when the user asks to resume, recover, or continue earlier work."

Include natural synonym phrasing users would actually say — "recover", "crashed", "restore", "continue where I left off" — alongside the existing "resume" and "interrupted".

Optionally broaden the action coverage to mention detecting orphaned in-progress work or checking checkpoint state, which the body supports but the description omits.

DimensionReasoningScore

Specificity

"Find and resume interrupted Copilot CLI sessions using session_store queries" names a precise target domain and concrete actions ("Find", "resume", "session_store queries") with only minor coverage gaps — the body also covers orphaned-issue detection and checkpoint inspection, which the description omits. It sits between anchor 3 ("1-2 concrete actions, not comprehensive") and anchor 4 ("several specific actions; minor gaps"); the mechanism mention and exact target push it to 4 rather than 3.

4 / 5

Completeness

The "what" is clear ("Find and resume interrupted Copilot CLI sessions using session_store queries") but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description. Per the rubric guideline, a missing trigger clause caps completeness at 3; "interrupted" only weakly implies when to invoke the skill.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present: "resume", "interrupted", "sessions", "Find" — matching utterances like "resume my session" or "my session was interrupted". It falls short of anchor 5 because common synonyms such as "recover", "crash(ed)", "restore", or "continue where I left off" are missing, and "session_store queries" is internal jargon; it clears anchor 3 because the included terms are genuinely natural rather than generic.

4 / 5

Distinctiveness Conflict Risk

The scope is a clear, narrow niche — recovering "interrupted Copilot CLI sessions" via "session_store queries" — with distinct trigger terms unlikely to fire for unrelated skills. It matches anchor 5 ("clear niche with distinct triggers; minimal conflict risk") rather than anchor 4, since no plausible closely-related-skill overlap remains at this level of specificity.

5 / 5

Total

16

/

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.

Validation — 15 / 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

microsoft/waza

Path

.github/skills/session-recovery/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.