context-management-context-restore
Use when working with context management context restore
31
14%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/context-management-context-restore/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely minimal and fails to communicate what the skill actually does. It only provides a 'Use when' clause that essentially restates the skill's name without adding any meaningful information about capabilities, actions, or specific triggers. It needs a complete rewrite with concrete actions and natural trigger terms.
Suggestions
Add a clear 'what it does' section listing specific concrete actions, e.g., 'Saves, loads, and restores conversation context and session state across interactions.'
Expand the 'Use when' clause with natural trigger terms users would actually say, e.g., 'Use when the user asks to save context, restore a previous session, resume a conversation, or manage conversation history.'
Remove the redundant repetition of 'context' and replace with distinct, descriptive language that differentiates this skill from other memory or state-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It does not describe what the skill does—only vaguely references 'context management context restore' without specifying any operations or capabilities. | 1 / 3 |
Completeness | The 'what does this do' component is entirely missing—there is no explanation of capabilities. While there is a 'Use when' clause, it only restates the skill name rather than providing meaningful trigger guidance, making both halves very weak. | 1 / 3 |
Trigger Term Quality | It includes the terms 'context management' and 'context restore,' which are somewhat relevant keywords a user might use, but they are repetitive ('context' appears twice) and miss common variations or natural phrasing users might employ. | 2 / 3 |
Distinctiveness Conflict Risk | The terms 'context management' and 'context restore' provide some specificity to a niche, but without concrete actions or clearer scope, it could overlap with other skills related to session management, memory, or state restoration. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a conceptual design document or product specification rather than actionable instructions for Claude. It is filled with abstract descriptions of capabilities, non-executable pseudocode, a 'Future Roadmap' section, and explanations of concepts Claude already knows. The skill lacks any concrete, executable guidance and appears to describe a hypothetical tool rather than providing practical instructions.
Suggestions
Replace all pseudocode with either executable code examples or remove them entirely—the current undefined function calls (VectorDatabase, calculate_composite_score) provide no actionable value.
Remove the 'Future Roadmap', 'Role Statement', and 'Context Overview' sections as they consume tokens without providing actionable guidance.
Add concrete validation steps to workflows with specific commands or checks, including error recovery paths (e.g., what to do when context restoration fails or returns low-relevance results).
Clarify what 'context-restore' actually is—if it's a real CLI tool, provide installation and setup; if it's conceptual, rewrite the skill around actual tools and techniques Claude can use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanatory content about concepts Claude already understands (vector search, cosine similarity, context management). Includes a 'Future Roadmap' section and 'Role Statement' that add no actionable value. The entire document reads like a design document rather than a concise skill instruction. | 1 / 3 |
Actionability | The code examples are pseudocode calling undefined functions (VectorDatabase, calculate_composite_score, prioritize_components, etc.) that cannot be executed. The CLI commands (context-restore) reference a tool that isn't established as real. Nothing is copy-paste ready or practically usable. | 1 / 3 |
Workflow Clarity | The two 'Reference Workflows' are vague 4-step summaries with no concrete commands, no validation checkpoints, and no error recovery steps. Steps like 'Validate context against current codebase' and 'Generate resumption summary' are abstract descriptions without any specifics on how to accomplish them. | 1 / 3 |
Progressive Disclosure | There is a reference to 'resources/implementation-playbook.md' for detailed examples, which shows some awareness of progressive disclosure. However, the main file itself is a monolithic wall of content (~150 lines) with sections that could be split out, and only one external reference exists. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
93c57b2
- 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.