recover-context

Extract full context of the last task from the most recent parent session shown in the session lineage. Strategically uses sub-agents to avoid bloating your own context.

Quality

62%

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 ./plugins/aichat/skills/recover-context/SKILL.md

Quality

Content

78%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 a concise, actionable, well-structured workflow that tells Claude exactly which subagent or skill to invoke and what to extract, with a copy-paste example prompt and clear constraints. Minor gains are available from de-duplicating the extraction checklist and adding an explicit validation step.

Dimension	Reasoning	Score
Conciseness	Lean and free of concept over-explanation, but the extraction checklist in steps 3-4 is repeated in the Example Sub-agent Prompt, a minor redundancy that could be trimmed — matches anchor 4 rather than 5 (every token earns its place).	4 / 5
Actionability	Provides concrete, executable guidance (specific subagent_type 'session-searcher', fallback 'aichat:session-search' skill, a copy-paste example prompt) with minor gaps from the conditional branch and the '[path from lineage]' placeholder — matches anchor 4 rather than 5 (fully copy-paste ready, common cases covered).	4 / 5
Workflow Clarity	Clear 5-step numbered sequence with a user-confirmation checkpoint in step 5 ('Report back', 'Ask the user how they'd like to proceed'); read-only extraction so the destructive-validation cap does not apply, but no explicit validation/feedback loop keeps it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	A ~50-line single-file skill with no need for external references and well-organized sections (Instructions, Example Sub-agent Prompt, Constraints); per scoring notes this qualifies for anchor 5 with just well-organized sections.	5 / 5
	Total	17 / 20 Passed

Description

46%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 conveys a clear purpose and a distinct niche, but lacks an explicit 'Use when...' trigger clause and leans on internal jargon ('session lineage', 'parent session') rather than natural user language, which weakens trigger-term quality and caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a session lineage is shown in the first user message and you need to recover the previous task's context.'

Include natural synonyms users might say, such as 'previous session', 'resume work', or 'pick up where you left off', alongside 'parent session' and 'session lineage'.

Specify the concrete outputs (e.g. 'summarize the last task's state, pending items, and relevant files') to lift specificity from 1-2 actions toward several concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('most recent parent session shown in the session lineage') and 1-2 concrete actions ('Extract full context', 'uses sub-agents'), but coverage is not comprehensive — matches anchor 3 rather than 4 which requires several specific actions.	3 / 5
Completeness	Has a clear 'what' ('Extract full context of the last task from the most recent parent session') but no explicit 'Use when...' clause — 'when' is only weakly implied by 'shown in the session lineage'; per guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Relies on technical jargon ('session lineage', 'parent session', 'sub-agents') with no natural user-facing phrases; matches anchor 2 (one or two generic keywords, missing natural phrases users say) rather than 3 which requires common variations.	2 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (recovering context from a parent session lineage) unlikely to conflict with unrelated skills, but trigger phrasing is not explicit enough for anchor 5; matches anchor 4 (mostly distinct, minor overlap risk).	4 / 5
	Total	12 / 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: pchalasani/claude-code-tools
Path: plugins/aichat/skills/recover-context/SKILL.md
Commit: c35a135

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