SKILLEMALL.ai
GitHub ↗ RU Sign in

CD context-restore

Skill that restores conversation context when users want to "continue where we left off". Reads compressed context files, extracts key information (recent operations, projects, tasks), and provides structured output to help users quickly resume their work.

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 36 files · 1 script body ≈ 4 200 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Skill that restores conversation context when users want to "continue where we left off".

As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureTelegramSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
74/100
safety, quality, tests
Safety 60%
70
Quality 40%
81
Run on models
none yet
Process rating
D
44/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 5

  • high Dangerous commands cmd-persistence docs/USAGE.md:347
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    echo "*/5 * * * * /home/athur/.openclaw/workspace/skills/context-restore/scripts/restore_context.py --auto --quiet >> ~/.context_restore.log 2>&1" | crontab -
Medium and low: 4
  • medium Exfiltration exfil-webhook-url docs/USAGE.md:312
    Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)
    curl -s -X POST "https://api.telegram.org/bot$TOKEN/sendMessage" \
    quoted
  • medium Exfiltration net-credential-use docs/USAGE.md:312
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X POST "https://api.telegram.org/bot$TOKEN/sendMessage" \
  • low Dangerous commands cmd-cron-mention docs/USAGE.md:350
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention docs/USAGE.md:454
    Mentions editing / listing crontab
    crontab -l

Files scanned: 29. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

Process rating: all ten parameters 44/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 70Execution cost. Instruction body is 4200 tokens
  • 100Steps. 24 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. No mutating operations
  • low 15 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • -32 of 6 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 256: enough signal without eating the budget
  • +4Structure: 61 headings
  • +3Step-by-step instructions: 24 items
  • +4Has examples (42 code blocks)
  • +4Reference files are cited in the instructions (3 of 5)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.