CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

context-management-context-restore

Restore saved project context, architectural decisions, and work state. Use when resuming interrupted work, retrieving prior context, or merging context across sessions.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is code-refactoring-context-restore in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

42%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body reads as an aspirational design document rather than an executable skill: extensive buzzword padding, code that references entirely undefined libraries, and workflows without validation checkpoints. The parameter table and CLI examples show intent toward concreteness, but nothing in the body can actually be run or followed step-by-step against real tooling.

Suggestions

Delete the padding sections (Use/Do-not-use tautologies, Role Statement, Context Overview, Integration Patterns, Future Roadmap) — they consume tokens without adding executable guidance, which is the main conciseness fix.

Replace the pseudocode with runnable code or remove it: define or ground VectorDatabase, calculate_composite_score, prioritize_components, and estimate_tokens, and either provide the context-restore CLI script in scripts/ or drop the usage examples referencing it.

Add explicit validation checkpoints and error-recovery loops to the Reference Workflows (e.g., verify restored context against the current codebase before proceeding, and what to do on mismatch), and move the eight advanced strategy sections into a references/ file linked from a concise overview.

DimensionReasoningScore

Conciseness

Multiple sections are pure padding: the circular "Use this skill when / Do not use this skill when" restatements, the "Role Statement", the buzzword-heavy "Context Overview" ("sophisticated memory management system"), "Integration Patterns", and a "Future Roadmap" with items like "Quantum-inspired vector search algorithms" that add no executable value — matching 'noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

Concrete-looking guidance exists (parameter tables, Python snippets, CLI examples) but every snippet depends on undefined constructs (VectorDatabase, calculate_composite_score, prioritize_components, estimate_tokens, load_component) and the `context-restore` CLI does not exist anywhere in the bundle — 'some concrete guidance but incomplete; pseudocode instead of executable code'.

3 / 5

Workflow Clarity

The Reference Workflows list a coherent sequence (retrieve → validate → restore → summarize) but validation is a bare bullet with no commands or checkpoints, and the merge/conflict-resolution operations have no feedback loops — 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The body has clear section headers (some structure, above 'minimal structure') but with zero bundle files the entire ~180-line body — including the eight advanced strategy sections, code listings, and usage examples that belong in separate reference files — is inlined in SKILL.md.

3 / 5

Total

11

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly and explicitly states both capability and trigger conditions in third-person voice with natural trigger phrases. Its main weakness is that the capability list is one retrieval-themed action rather than several distinct concrete actions, leaving specificity slightly thin.

Suggestions

Enumerate a few more distinct concrete capabilities in the what-clause (e.g., 'reconstruct agent workflow state and decision trails', 'three-way merge of context versions') so specificity goes beyond a single restore action.

Add one or two common user phrasings as triggers (e.g., 'pick up where I left off', 'session handoff') to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Restore saved project context, architectural decisions, and work state" names the domain with one core action applied to three objects; resuming/retrieving/merging in the when-clause are variations of a single retrieval theme rather than several distinct concrete capabilities, matching the '1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

It explicitly answers both what ("Restore saved project context, architectural decisions, and work state") and when ("Use when resuming interrupted work, retrieving prior context, or merging context across sessions") with concrete trigger phrases, in correct third-person voice — a direct match for the top anchor.

5 / 5

Trigger Term Quality

Phrases like "resuming interrupted work", "retrieving prior context", and "merging context across sessions" are natural user trigger terms with good coverage, but common variations such as 'pick up where I left off', 'session handoff', or 'context compaction' are missing, so it falls short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The context-restoration niche is mostly distinct with specific triggers, but it carries minor overlap risk with closely related memory-management and session-summary skills, fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict top anchor.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/context-management-context-restore/SKILL.md

Reviewed

Table of Contents

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.