SKILLEMALL.ai

BC context-compression

Prevent context overflow with automatic session truncation and memory preservation.

ClawHub Agent Skills author: lifei68801 v3.13.3 MIT-0 19 files · 16 scripts body ≈ 1 603 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
95
Quality 40%
65
Run on models
none yet
Process rating
C
61/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

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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

✓ No critical or high findings

Medium and low: 5
  • low Dangerous commands cmd-cron-mention check-context-health.sh:147
    Mentions editing / listing crontab
    if crontab -l 2>/dev/null | grep -q "truncate-sessions"; then
  • low Dangerous commands cmd-cron-mention check-context-health.sh:151
    Mentions editing / listing crontab (string literal in code, not executed)
    echo "    Run: crontab -e and add:"
    code literal
  • low Dangerous commands cmd-cron-mention check-context-health.sh:155
    Mentions editing / listing crontab
    if crontab -l 2>/dev/null | grep -q "generate-daily-summary"; then
  • low Dangerous commands cmd-cron-mention configure.sh:199
    Mentions editing / listing crontab (string literal in code, not executed)
    echo "  1. 运行 crontab -e 添加上面的 cron 条目"
    code literal
  • low Dangerous commands cmd-cron-mention SKILL.md:56
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    > ⚡ **After installing**, run the interactive setup wizard to generate your config file, then add the suggested cron entry with `crontab -e`. See Quick Start below for commands.
    quoted

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 61/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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 9 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 27 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1603 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +3Description length 83: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 27 items
  • +4Has examples (2 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This skill has a legitimate context-management purpose, but it needs review because it can rewrite session history and persist conversation-derived facts while some safety claims are inaccurate.
LLM: suspicious (high) · VirusTotal: · 29 May 2026