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

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 verbose, conceptual document that reads like a product specification or marketing overview rather than actionable instructions for Claude. It explains concepts Claude already understands, provides non-executable pseudocode with undefined functions, lacks any concrete commands or validation steps, and references a bundle file that doesn't exist. The content needs to be completely rewritten to focus on specific, executable guidance.

Suggestions

Replace all pseudocode with executable, copy-paste ready code that actually implements context save/restore operations using real libraries and concrete file paths.

Remove the 'Role and Purpose', 'Advanced Integration Capabilities', 'Limitations and Considerations', and 'Future Roadmap' sections — these waste tokens on information Claude doesn't need.

Add explicit validation checkpoints to workflows (e.g., verify context file was written, validate JSON schema, confirm restoration succeeded) with error recovery steps.

Either create the referenced `resources/implementation-playbook.md` bundle file with detailed examples, or remove the reference and inline the essential content concisely.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive conceptual explanations Claude already knows (what context management is, what vector databases are, what compression is). 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 like 'Analyze project structure' and 'Generate semantic embeddings' give no indication of how to actually perform them. No feedback loops exist for any operation.	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. Seven major sections are inlined that could be split, and the organization mixes conceptual overview with schemas, code, and roadmap items indiscriminately.	1 / 3
	Total	4 / 12 Passed

Description

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, provides no meaningful explanation of what the skill does, and its trigger terms are vague and redundant. The description essentially restates the skill name without adding useful information for skill selection.

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, load, or manage conversation context, mentions remembering previous sessions, or needs to persist state across interactions.'

Differentiate from other potentially overlapping skills by specifying the exact scope, e.g., what type of context (conversation history, variable state, project context) and what storage mechanism is used.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions. '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 explanation of capabilities. While there is a 'Use when' clause, it merely 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 miss natural variations a user might say (e.g., 'save state,' 'remember context,' 'persist session,' 'store context').	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

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: 6042393

Reviewed: about 2 hours 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.