context-management-context-restore
Use when working with context management context restore
Overall
score
37%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill context-management-context-restoreActivation
22%This description is severely lacking - it provides a 'Use when' clause but fails to explain what the skill actually does. The circular phrasing 'context management context restore' is confusing and doesn't help Claude understand the skill's purpose or capabilities. Without knowing what actions this skill performs, it cannot be effectively selected.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Saves and restores conversation context, manages session state, preserves working memory across interactions').
Expand trigger terms with natural language variations users might say (e.g., 'save my progress', 'remember this', 'restore session', 'pick up where we left off').
Restructure to follow the pattern: '[What it does]. Use when [explicit triggers].' to clearly separate capabilities from selection criteria.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it doesn't explain what the skill actually does, only vaguely references 'context management context restore' without describing any specific capabilities. | 1 / 3 |
Completeness | The description only provides a weak 'when' clause with no 'what' - it never explains what the skill actually does. The 'Use when' trigger is present but references undefined concepts. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('context management', 'context restore') but these are somewhat technical/jargon-heavy and the repetition of 'context' suggests poor phrasing. Missing natural variations users might say. | 2 / 3 |
Distinctiveness Conflict Risk | The terms 'context management' and 'context restore' provide some specificity to a niche, but without explaining what these mean, it's unclear how this differs from other potential context-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%This skill is overly verbose and conceptual, explaining abstract ideas about context restoration rather than providing concrete, executable guidance. The code examples are incomplete pseudocode referencing undefined dependencies, and the workflows lack specific commands and validation steps. The content reads more like a design document or marketing material than an actionable skill.
Suggestions
Remove the Role Statement, Context Overview, Integration Patterns, and Future Roadmap sections - they add no actionable value
Replace pseudocode with complete, executable examples that include actual imports and function definitions, or clearly specify the required dependencies/tools
Add concrete validation steps to workflows (e.g., 'Run `context-restore --validate` to verify integrity before proceeding')
Consolidate the 8 'Advanced Context Retrieval Strategies' into a reference file and keep only the most essential 2-3 patterns in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with unnecessary conceptual explanations Claude already knows (what vector search is, what cosine similarity means). The 'Role Statement', 'Context Overview', 'Future Roadmap', and 'Integration Patterns' sections add no actionable value and waste tokens on abstract descriptions. | 1 / 3 |
Actionability | Contains Python code examples that appear executable, but they reference undefined functions (VectorDatabase, calculate_composite_score, prioritize_components) making them pseudocode in practice. The bash examples reference a 'context-restore' tool without explaining how to install or access it. | 2 / 3 |
Workflow Clarity | The 'Reference Workflows' section lists high-level steps without concrete commands or validation checkpoints. No feedback loops for error recovery, no verification steps, and the numbered lists describe what to do abstractly rather than how to do it specifically. | 1 / 3 |
Progressive Disclosure | References 'resources/implementation-playbook.md' for detailed examples, which is good progressive disclosure. However, the main content is a monolithic wall of text with 8 numbered sections that could be split into separate reference files. The structure exists but content organization is poor. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
88%Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
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.