CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-refactoring-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

70%

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/code-refactoring-context-restore/SKILL.md
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 is padded with persona, boilerplate, and roadmap fluff, and its code examples read as illustrative pseudocode rather than executable guidance: every snippet calls undefined helpers and the CLI has no backing script. Structure is reasonable, but the skill tells rather than instructs, and nothing is progressively disclosed into reference files.

Suggestions

Delete the 'Use this skill when' / 'Do not use this skill when' / 'Role Statement' / 'Context Overview' / 'Future Roadmap' sections and the generic 'Instructions' list — they add fluff, not instruction, and could cut the file by more than half.

Replace the illustrative Python (VectorDatabase, prioritize_components, calculate_composite_score, etc.) with executable code — e.g., a real script in scripts/ for loading a saved context file with token budgeting — or link to concrete file-based context-restore commands instead of an undefined `context-restore` CLI.

Add explicit validation checkpoints to the Reference Workflows (e.g., how to verify restored context against the current codebase, and what to do on mismatch) so the sequences become feedback loops rather than a list of step names.

DimensionReasoningScore

Conciseness

Several padded sections add nothing Claude does not already know: circular "Use this skill when / Do not use this skill when" boilerplate ("The task is unrelated to context restoration: advanced semantic memory rehydration"), a "Role Statement" persona paragraph, a buzzword-heavy "Context Overview", generic "Instructions" ("Clarify goals, constraints, and required inputs"), and a "Future Roadmap" ("Quantum-inspired vector search algorithms", "Self-healing context reconstruction"). This matches anchor 2 ("Noticeably verbose; several unnecessary explanations or padded sections") rather than 1, since the parameter specs and code do carry real information.

2 / 5

Actionability

Input parameters and the CLI usage block are concrete, but all three Python examples depend on undefined machinery — VectorDatabase(...), rank_and_filter_contexts(...), calculate_composite_score(...), prioritize_components(...), estimate_tokens(...), load_component(...) — and the `context-restore` CLI has no corresponding script in the bundle. This matches anchor 3 ("Some concrete guidance but incomplete; pseudocode instead of executable code; missing key details") rather than 4, since none of the code is executable as written.

3 / 5

Workflow Clarity

The two "Reference Workflows" list coherent steps, but validation is nominal ("Validate context against current codebase", "Validate knowledge transferability") with no commands, mechanisms, or error-recovery loops, matching anchor 3 ("Steps listed but validation gaps; checkpoints missing or implicit"). Not 2 because the sequences are defined rather than full of gaps; not 4 because no checkpoint is concretely actionable.

3 / 5

Progressive Disclosure

The single 179-line file is well-sectioned by headers, but everything — strategy code, usage examples, integration patterns, roadmap — is inlined when it clearly belongs in separate reference files, and no references/ or scripts/ files exist. This matches anchor 3 ("Some structure but could be better organized; content that should be separate is inline") rather than 2, since headers keep it navigable and it is not a wall of text.

3 / 5

Total

11

/

20

Passed

Description

83%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 well-formed description with a clear third-person 'what' statement and an explicit 'Use when...' clause with three concrete trigger phrases. It only narrowly misses top marks on trigger coverage and distinctiveness.

DimensionReasoningScore

Specificity

"Restore saved project context, architectural decisions, and work state" names the domain plus several concrete restore targets, matching anchor 4 ("Lists several specific actions; minor gaps in coverage"). It is not 3 because more than 1-2 concrete actions are stated, and not 5 because coverage is not comprehensive (no mention of what form the restored context takes or how).

4 / 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 — the exact pattern of the anchor 5 example. Not 4, since the 'when' clause is already explicit and specific rather than merely adequate.

5 / 5

Trigger Term Quality

Triggers "resuming interrupted work", "retrieving prior context", and "merging context across sessions" are natural phrases a user would say, matching anchor 4 ("Good keyword coverage; a few natural terms missing"). It falls short of anchor 5 because common variants like "restore context", "pick up where I left off", or "previous session" are absent.

4 / 5

Distinctiveness Conflict Risk

Context restoration/session resumption is a clear niche with distinct triggers, but "work state" restoration overlaps with general memory and session-restore skills, matching anchor 4 ("Mostly distinct; minor overlap risk with closely related skills"). Not 5 because of that residual overlap; not 3 because the triggers are firmly tied to this specific purpose.

4 / 5

Total

17

/

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/code-refactoring-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.