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 findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/context-management-context-save/SKILL.md

The canonical home for this skill is context-management-context-save in sickn33/agentic-awesome-skills

Quality

Content

0%Scale 1-3

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 specification document rather than an actionable skill. It explains concepts Claude already understands (compression, vector databases, knowledge graphs), provides only pseudocode with undefined functions, and lacks any concrete, executable guidance. The workflows have no validation steps, the referenced bundle file doesn't exist, and significant content (Future Roadmap, Role and Purpose) adds no instructional value.

Suggestions

Replace all pseudocode with executable, copy-paste-ready code examples that use real libraries and defined functions — or remove code examples entirely if the skill is instruction-only.

Remove sections that explain concepts Claude already knows (Role and Purpose, Context Management Overview, Future Roadmap, Limitations) and focus only on specific, novel instructions.

Add concrete validation checkpoints to workflows (e.g., 'Verify context file exists and is valid JSON: `python -m json.tool context.json`') and include error recovery steps.

Either create the referenced 'resources/implementation-playbook.md' bundle file or remove the reference, and restructure the monolithic content into a concise overview with clearly signaled references to 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. The content reads like a product specification document rather than an actionable skill.	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 doesn't instruct Claude on what to actually do.	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 actionable guidance. No feedback loops or verification steps exist anywhere.	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, storage format lists, JSON schemas, future roadmaps — without any logical separation or progressive depth.	1 / 3
	Total	4 / 12 Passed

Description

0%Scale 1-3

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 weak across all dimensions. It fails to explain what the skill does, uses no natural trigger terms, and provides no concrete actions or distinguishing details. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.

Suggestions

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

Include natural trigger terms users would actually say, such as 'save context', 'remember this', 'store conversation', 'recall previous session', 'persist state'.

Expand the 'Use when' clause with explicit scenarios, e.g., 'Use when the user asks to save, load, or manage conversation context, or when they want to persist information across sessions.'

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Working with context management context save' is vague and abstract with no specific capabilities listed.	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 is so vague ('working with context management context save') that it provides no meaningful trigger guidance.	1 / 3
Trigger Term Quality	The terms 'context management' and 'context save' are technical jargon that users are unlikely to naturally say. There are no natural language variations or common user phrases included.	1 / 3
Distinctiveness Conflict Risk	The description is extremely generic and could overlap with any skill involving saving, caching, or managing context. 'Context management' is too broad to carve out a clear niche.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/context-management-context-save/SKILL.md
Commit: 7520423

Reviewed: ~15 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.