context-management-context-save

Use when working with context management context save

1.31x

Quality

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

14%

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 across all dimensions. It lacks any concrete actions describing what the skill does, essentially just restating its name as a trigger phrase. Without specifying capabilities or meaningful trigger terms, Claude would struggle to correctly select this skill from a pool of available options.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Saves conversation context to persistent storage, retrieves previously saved context, and manages context windows for long-running sessions.'

Expand the 'Use when' clause with natural trigger terms users would actually say, e.g., 'Use when the user asks to save context, remember something for later, persist session state, or manage conversation memory.'

Clarify the scope and niche of the skill to reduce conflict risk, e.g., specify what type of context (conversation, project, code) and what format or mechanism is used.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions at all. 'Working with context management context save' is vague and abstract—it doesn't describe what the skill actually does (e.g., save conversation state, persist variables, manage memory).	1 / 3
Completeness	The 'what does this do' is entirely missing—there is no description of capabilities. While there is a 'Use when' clause, it only restates the skill name without providing meaningful trigger guidance, making both the what and when very weak.	1 / 3
Trigger Term Quality	It includes some potentially relevant keywords like 'context management' and 'context save,' but these are somewhat redundant and lack natural variations a user might say (e.g., 'save state,' 'remember context,' 'persist session,' 'store conversation').	2 / 3
Distinctiveness Conflict Risk	'Context management' is extremely broad and could overlap with many skills involving memory, state, sessions, or data persistence. There are no distinct triggers that would clearly differentiate this skill from others.	1 / 3
	Total	5 / 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 is a verbose, conceptual overview that reads like marketing documentation rather than actionable instructions. It explains numerous concepts Claude already understands, provides only pseudocode with undefined functions, and lacks any concrete, executable guidance for actually performing context save operations. The workflows are abstract step lists without validation or error handling.

Suggestions

Replace pseudocode with fully executable code examples that actually implement context saving (e.g., writing project state to a JSON file with real Python code).

Remove conceptual explanations (Role and Purpose, Future Roadmap, Advanced Integration Capabilities, Limitations) and focus on concrete steps Claude should take when asked to save context.

Add explicit validation checkpoints to workflows, e.g., 'Verify the saved context file is valid JSON by reading it back' with actual commands.

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 context management is, what vector databases are, what compression algorithms do). Includes a 'Future Roadmap' section and 'Role and Purpose' description that waste tokens. The content reads like a product brochure rather than actionable instructions.	1 / 3
Actionability	Code examples are pseudocode calling undefined functions (extract_project_metadata, analyze_architecture, semantic_compression, etc.) — none are executable. The workflows are vague step lists without concrete commands. There is no copy-paste ready guidance for actually saving or restoring context.	1 / 3
Workflow Clarity	The two 'Reference Workflows' are high-level bullet lists with no concrete commands, no validation checkpoints, and no error recovery steps. Steps like 'Analyze project structure' and 'Generate semantic embeddings' give no indication of how to actually perform them.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no meaningful structure for navigation. It references `resources/implementation-playbook.md` but no bundle files exist. The content dumps everything inline — JSON schemas, multiple code blocks, vector database lists, storage format lists — without any logical separation or clear signposting.	1 / 3
	Total	4 / 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: f5dc9e3

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.