context-management-context-restore

Use when working with context management context restore

1.70x

Quality

14%

Does it follow best practices?

Impact

87%

1.70x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/context-management-context-restore/SKILL.md

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

Quality

Content

7%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 largely a conceptual overview document rather than actionable guidance. It explains abstract ideas about semantic context restoration using non-executable pseudocode and vague workflow descriptions. The content is extremely verbose, padded with sections Claude doesn't need (Role Statement, Future Roadmap, Context Overview), and fails to provide any concrete, copy-paste-ready instructions for accomplishing real tasks.

Suggestions

Remove all conceptual explanations (Role Statement, Context Overview, Future Roadmap, Integration Patterns) and focus only on concrete steps Claude should take when restoring context.

Replace pseudocode with either executable code examples using real libraries/tools, or remove code entirely and provide specific, actionable text instructions.

Add explicit validation checkpoints to workflows — e.g., how to verify context was restored correctly, what to do if restoration fails, and concrete error recovery steps.

Specify what actual tools, libraries, or file formats are involved (e.g., which vector database, what file format for context storage) so Claude can take real action.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive conceptual explanations Claude already knows (what vector search is, what cosine similarity is, what RAG is). The 'Future Roadmap' section, 'Role Statement', and 'Context Overview' are pure padding. The skill is ~150 lines when it could be under 40. Much of the content describes rather than instructs.	1 / 3
Actionability	The Python code examples are pseudocode calling undefined functions (VectorDatabase, calculate_composite_score, prioritize_components, etc.) — none are executable. The bash examples reference a non-existent 'context-restore' CLI tool with no installation or setup instructions. The skill describes concepts abstractly rather than providing concrete, usable guidance.	1 / 3
Workflow Clarity	The two 'Reference Workflows' are vague 4-step summaries with no validation checkpoints, no error handling, and no concrete commands. Steps like 'Validate context against current codebase' and 'Generate resumption summary' are abstract directives with no specifics on how to accomplish them. No feedback loops exist for any operation.	1 / 3
Progressive Disclosure	There is a reference to 'resources/implementation-playbook.md' for detailed examples, which is a reasonable progressive disclosure pattern. However, the main file itself is a monolithic wall of text with 8+ subsections that could be split out, and the single reference is not well-signaled or clearly scoped.	2 / 3
	Total	5 / 12 Passed

Description

22%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 extremely weak—it provides no information about what the skill actually does and relies on a circular, tautological trigger clause. It fails to describe any concrete actions or capabilities, making it nearly impossible for Claude to make an informed decision about when to select this skill over others.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Saves and restores conversation context, session state, and working memory across interactions.'

Expand the 'Use when' clause with natural trigger terms users would actually say, e.g., 'Use when the user asks to save progress, resume a previous session, reload context, or restore earlier conversation state.'

Clarify the specific scenarios and inputs/outputs so the description answers both 'what' and 'when' distinctly.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It does not describe what the skill does—only vaguely references 'context management context restore' without specifying any capabilities.	1 / 3
Completeness	The 'what does this do' part is entirely missing—there is no explanation of capabilities. While it has a 'Use when' clause, the trigger is circular and uninformative ('context management context restore'), making both halves very weak.	1 / 3
Trigger Term Quality	It includes the terms 'context management' and 'context restore,' which are somewhat relevant keywords a user might use, but lacks common variations or natural phrasing (e.g., 'reload context', 'resume session', 'restore state').	2 / 3
Distinctiveness Conflict Risk	The phrase 'context management context restore' is somewhat niche, which reduces conflict risk slightly, but the lack of specificity about what it actually does means it could overlap with other context-related skills.	2 / 3
	Total	6 / 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: plugins/AI-Agents-Safe-Coding-Skills/skills/context-management-context-restore/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.