SKILLEMALL.ai

BC agent-memory-continuity

Solve the "agent forgot everything" problem with search-first protocol, automated memory sync, and context preservation. No more conversation restarts!

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 11 files · 5 scripts body ≈ 1 600 tokens Open the sourcegithub.com analyzed 2 d ago

Solve the "agent forgot everything" problem with search-first protocol, automated memory sync, and context preservation.

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureGitHubAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
79/100
safety, quality, tests
Safety 60%
77
Quality 40%
82
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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.

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 · 6

  • high Dangerous commands cmd-persistence scripts/activate-memory-sync.sh:25
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null; echo "$CRON_JOB") | crontab - 2>/dev/null || true
Medium and low: 5
  • low Dangerous commands cmd-cron-mention docs/troubleshooting.md:11
    Mentions editing / listing crontab (detector / deny-list definition)
    2. Verify cron job: `crontab -l | grep memory`
    detector
  • low Dangerous commands cmd-cron-mention scripts/activate-memory-sync.sh:21
    Mentions editing / listing crontab
    if crontab -l 2>/dev/null | grep -q "sync-memory.sh"; then
  • low Dangerous commands cmd-cron-mention scripts/activate-memory-sync.sh:25
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null; echo "$CRON_JOB") | crontab - 2>/dev/null || true
  • low Instruction override en-ignore-previous SKILL.md:14
    Instruction-override phrase ("ignore previous instructions") (negated — the text forbids it)
    **Agent Memory Continuity** solves fragmented conversations through a battle-tested **search-first protocol** that ensures agents never forget previous context.
    negated
  • low Dangerous commands cmd-cron-mention SKILL.md:211
    Mentions editing / listing crontab
    crontab -l | grep memory

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

Against the Agent Skills spec

  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 59/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. No external tools needed
  • 100Steps. 55 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1600 tokens
  • 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
  • -217 emoji in the instructions: noise for the model
  • -31 of 4 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 151: enough signal without eating the budget
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 55 items
  • +4Has examples (10 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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