The description is well-structured with explicit trigger terms and a clear 'Use when' clause, making it easy for Claude to select appropriately. Its main weakness is that the 'what' portion is somewhat thin — it says to 'resume session' but doesn't elaborate on what concrete actions are performed (e.g., reading the file, restoring variables, summarizing previous progress). Overall it's a solid, focused description for a narrow-purpose skill.

Suggestions

Add more specific actions describing what happens during resumption, e.g., 'Reads CONTEXT-llm.md to restore project state, recall previous decisions, and continue work from the last checkpoint.'

Dimension	Reasoning	Score
Specificity	Names the domain (session resumption from CONTEXT-llm.md) and one action (resume session), but doesn't describe concrete actions like parsing the file, restoring state, or what specifically happens during resumption.	2 / 3
Completeness	Clearly answers both 'what' (resume session from CONTEXT-llm.md) and 'when' (explicit 'Use when' clause with triggers like 'load context', 'resume session', 'continue where I left off').	3 / 3
Trigger Term Quality	Includes strong natural trigger terms that users would actually say: 'load context', 'resume session', 'continue where I left off'. These cover common variations of how a user would phrase this request.	3 / 3
Distinctiveness Conflict Risk	Very specific niche — resuming from a particular file (CONTEXT-llm.md) with distinct trigger phrases. Unlikely to conflict with other skills since the concept of session resumption from a saved context file is quite unique.	3 / 3
	Total	11 / 12 Passed

Implementation

70%

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

This is a well-structured skill with clear workflow phases and good progressive disclosure. Its main weaknesses are moderate verbosity in the 'When to Use/Not Use' and 'Anti-Patterns' sections (which repeat concepts and explain rationale Claude doesn't need), and usage examples that are comments rather than executable demonstrations. The core workflow logic and error handling are strong.

Suggestions

Consolidate 'When to Use', 'When Not to Use', and 'Anti-Patterns' into a shorter constraints/guardrails section — much of the 'Why:' explanations repeat what's already stated and explain reasoning Claude can infer.

Replace the comment-only usage examples with actual executable command sequences or show the expected resume report output format inline, so Claude has a concrete template to follow.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some sections that could be tightened. The 'When to Use', 'When Not to Use', and 'Anti-Patterns' sections are quite verbose with explanations that repeat information already conveyed elsewhere (e.g., the done/ marker is explained in both the workflow and anti-patterns). The Philosophy section adds little actionable value. However, the core workflow and performance rules are lean.	2 / 3
Actionability	The workflow provides concrete steps with specific file paths and bash commands, but the commands shown are incomplete (e.g., `rtk ls -t` is shown but the full execution context is unclear). Usage examples are illustrative comments rather than executable commands. The AskUserQuestion guard is concrete and actionable. Key details like the report format are deferred to reference.md without inline examples of what the output looks like.	2 / 3
Workflow Clarity	The three-phase workflow is clearly sequenced with explicit conditions (if not found, check done/; if multiple streams, ask user). The AskUserQuestion guard provides a clear feedback loop for error recovery. Validation steps are present (verify session_id, check for empty answers, confirm done/ files with user). The conditional branching is well-defined.	3 / 3
Progressive Disclosure	The skill provides a clear overview with well-organized sections and a single-level reference to reference.md for detailed formatting rules. Content is appropriately split — the main skill covers workflow and philosophy while detailed section mapping and report structure are in the reference file. Navigation is clearly signaled.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Reviewed

5 days ago

Table of Contents

Discovery Implementation Validation