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 reads like a marketing document or product specification rather than actionable instructions for Claude. It is extremely verbose, explains concepts Claude already understands, provides no executable code (all examples call undefined functions), and lacks any concrete workflow with validation steps. The content would need to be fundamentally rewritten to be useful.

Suggestions

Replace all pseudocode examples with executable, copy-paste-ready code that actually performs context saving operations (e.g., writing project state to a JSON file, reading directory structures).

Remove the 'Role and Purpose', 'Future Roadmap', 'Advanced Integration Capabilities', and conceptual overview sections — these waste tokens explaining things Claude already knows.

Add concrete, step-by-step workflows with explicit validation checkpoints (e.g., 'verify the saved context file is valid JSON by running: python -m json.tool context.json').

Either create the referenced 'resources/implementation-playbook.md' bundle file or remove the reference, and restructure the content so the SKILL.md is a concise overview pointing to well-organized supporting files.

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. Much of 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. The JSON schema is the only concrete artifact but isn't tied to any actionable instruction.	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. 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. The content dumps everything inline — vector database lists, compression techniques, knowledge graphs, storage formats — without any logical separation or clear signposting.	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 critically underdeveloped. It lacks any concrete actions explaining what the skill does, and the 'Use when' clause is essentially a tautological restatement of the skill's name rather than providing meaningful selection guidance. The description would fail to help Claude distinguish this skill from others in a multi-skill environment.

Suggestions

Add specific concrete actions describing what the skill does, e.g., 'Saves, loads, and manages conversation context and state across sessions.'

Expand the 'Use when' clause with natural trigger terms users would actually say, such as 'save this context,' 'remember this for later,' 'persist state,' 'restore session,' 'load previous context.'

Clarify the skill's niche to reduce conflict risk—specify what kind of context (conversation, project, session) and what operations are supported (save, load, delete, list).

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 explanation of capabilities. While there is a 'Use when' clause, it merely restates the skill name rather than providing meaningful trigger guidance, making both halves effectively weak.	1 / 3
Trigger Term Quality	It includes some potentially relevant keywords like 'context management' and 'context save,' but these are somewhat redundant and don't cover natural variations a user might say (e.g., 'save state,' 'remember this,' 'persist context,' '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

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.