context-management-context-save

Use when working with context management context save

1.31x

Quality

14%

Does it follow best practices?

Impact

91%

1.31x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

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 severely lacking in substance. It provides no information about what the skill actually does - only a vague trigger phrase. The circular phrasing 'context management context save' is redundant and unhelpful for Claude to understand when to select this skill over others.

Suggestions

Add concrete actions describing what this skill does (e.g., 'Saves conversation context to persistent storage, exports session history, creates context snapshots for later retrieval').

Expand trigger terms with natural variations users would say (e.g., 'save session', 'remember this', 'store conversation', 'export context', 'create checkpoint').

Restructure to follow the pattern: '[What it does]. Use when [explicit triggers].' to clearly separate capabilities from usage guidance.

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 save' without describing any capabilities.	1 / 3
Completeness	The description only provides a weak 'when' clause ('Use when working with') but completely lacks the 'what' - there's no explanation of what this skill actually does or what actions it performs.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('context management', 'context save') but they are repetitive and lack natural variations users might say. Missing terms like 'save session', 'store context', 'remember', etc.	2 / 3
Distinctiveness Conflict Risk	The term 'context management' is somewhat specific but could overlap with other context-related skills. Without concrete actions described, it's unclear what distinguishes this from other potential context or memory-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

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 product specification or marketing document rather than actionable guidance for Claude. It describes capabilities at a high level without providing executable code, concrete commands, or specific implementation details. The content is bloated with explanations of concepts Claude already understands and lacks the practical, copy-paste-ready examples needed for effective task execution.

Suggestions

Replace pseudocode with actual executable implementations - define the helper functions or use real libraries with working code

Remove conceptual explanations (what vector databases are, compression overview) and focus on specific commands/APIs Claude should use

Add concrete validation steps to workflows - what command verifies context was saved correctly? What does success look like?

Cut the 'Future Roadmap', 'Role and Purpose', and marketing language - these add no actionable value

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of concepts Claude already knows (what vector databases are, compression algorithms, JSON Schema). Contains marketing-style language ('elite context engineering specialist', 'sophisticated solution') and a 'Future Roadmap' section that adds no actionable value.	1 / 3
Actionability	Code examples are pseudocode with undefined functions (extract_project_metadata, analyze_architecture, etc.) that cannot be executed. No concrete commands, actual tool invocations, or copy-paste ready implementations are provided.	1 / 3
Workflow Clarity	Workflows are vague lists without validation checkpoints or error handling. Steps like 'Analyze project structure' and 'Generate semantic embeddings' provide no concrete guidance on how to perform these actions or verify success.	1 / 3
Progressive Disclosure	References implementation-playbook.md for detailed examples, which is appropriate. However, the main content is a monolithic wall of text with many sections that could be split into separate reference files, and the organization mixes conceptual overview with incomplete implementation details.	2 / 3
	Total	5 / 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: 9c177eb

Reviewed: 3 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.