context-management-context-restore

Use when working with context management context restore

Quality

14%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/context-management-context-restore/SKILL.md

Quality

Content

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

This skill is a conceptual overview document masquerading as actionable guidance. It explains abstract concepts Claude already understands (vector search, semantic similarity, context merging) without providing any executable code, real tool references, or concrete workflows. The pseudocode examples reference non-existent libraries and functions, and the CLI examples appear fabricated. The 'Future Roadmap' section is entirely irrelevant to a skill file.

Suggestions

Replace all pseudocode with executable code using real libraries/tools, or remove code blocks entirely and provide specific, concrete textual instructions instead.

Remove sections that explain concepts Claude already knows: Role Statement, Context Overview, Integration Patterns, Future Roadmap, and the conceptual descriptions under each strategy heading.

Add concrete validation checkpoints to workflows (e.g., specific commands to verify context integrity, expected output formats, error conditions and recovery steps).

Either provide the referenced 'resources/implementation-playbook.md' bundle file or remove the reference and inline the essential actionable content.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive conceptual explanations Claude already knows (what vector search is, what cosine similarity is, what RAG is). The 'Role Statement', 'Context Overview', 'Future Roadmap', and 'Integration Patterns' sections add no actionable value. The skill explains concepts rather than providing specific instructions.	1 / 3
Actionability	The code examples are pseudocode referencing undefined functions (VectorDatabase, calculate_composite_score, prioritize_components, load_component, estimate_tokens) and non-existent CLI tools (context-restore). Nothing is executable or copy-paste ready. The bash examples reference a tool that doesn't appear to exist.	1 / 3
Workflow Clarity	The 'Reference Workflows' section lists high-level steps without any concrete commands, validation checkpoints, or error recovery. Steps like 'Validate context against current codebase' and 'Selectively restore relevant components' are vague and unactionable. No feedback loops or verification steps are present.	1 / 3
Progressive Disclosure	There is a reference to 'resources/implementation-playbook.md' for detailed examples, but no bundle files exist to support it. The content itself is a monolithic wall of text with 8 numbered strategy sections that could be split into separate files. Some structural organization exists via headers, preventing a score of 1.	2 / 3
	Total	5 / 12 Passed

Description

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 weak—it lacks any explanation of what the skill actually does and merely restates its name in a 'Use when' clause. It provides no concrete actions, no meaningful trigger guidance, and would be nearly useless for Claude to differentiate this skill from others in a large skill library.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Saves and restores conversation context, session state, and working memory across interactions.'

Expand the 'Use when' clause with natural trigger terms users would say, such as 'resume session', 'pick up where I left off', 'reload previous context', 'restore working state'.

Clarify the specific scenarios and inputs/outputs so Claude can distinguish this from other context-related or session management 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 explaining any specific capabilities.	1 / 3
Completeness	The 'what does this do' part is entirely missing—there is no explanation of the skill's capabilities. While there is a 'Use when' clause, it only restates the skill name rather than providing meaningful trigger guidance.	1 / 3
Trigger Term Quality	It includes the terms 'context management' and 'context restore,' which could be relevant trigger terms, but they are somewhat redundant and lack natural variations a user might say (e.g., 'reload context', 'restore session', 'pick up where I left off').	2 / 3
Distinctiveness Conflict Risk	The terms 'context management' and 'context restore' provide some specificity to a niche, but without concrete actions described, it could overlap with other context-related skills and is not clearly distinguishable.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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: 88d1e11

Reviewed: 5 days 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.