CC session-guardian
Never lose a conversation again. Auto-backup, smart recovery, and health monitoring for OpenClaw sessions. Protects against gateway crashes, model disconnections, and token overflow. Use this skill when: - User worries about losing conversations after gateway restart or model crash - User mentions session backup, conversation recovery, session protection, or data loss - User's agent is slow or timing out (likely token overflow from large sessions) - User runs multiple agents and needs to track collaboration across sessions - User asks about session health, backup strategy, or disaster recovery - User mentions "对话丢失", "会话备份", "上下文溢出", "token超限", "Gateway重启后记忆丢失" - Even if user just says "my agent lost everything after a restart" — this is the skill
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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.
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.
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
- 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.
- 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 · 16
-
high Dangerous commands
cmd-persistencescripts/install.sh:80Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null || true; cat << EOF
-
high Dangerous commands
cmd-persistencescripts/install.sh:89Persistence mechanism (cron / launchd / scheduled task / autorun registry)) | crontab -
Medium and low: 14
-
low Dangerous commands
cmd-cron-mentionEXAMPLES.md:46Mentions editing / listing crontab (test fixture / example file; documentation of a security skill)crontab -l | grep session-guardian
fixturesecurity skill -
low Dangerous commands
cmd-cron-mentionREADME_CN.md:53Mentions editing / listing crontab (documentation of a security skill)crontab -l | grep session-guardian
security skill -
low Dangerous commands
cmd-cron-mentionREADME_EN.md:37Mentions editing / listing crontab (documentation of a security skill)crontab -l | grep session-guardian
security skill -
low Dangerous commands
cmd-cron-mentionREADME.md:29Mentions editing / listing crontab (documentation of a security skill)crontab -l | grep session-guardian
security skill -
low Dangerous commands
cmd-cron-mentionREADME.md:220Mentions editing / listing crontab (documentation of a security skill)crontab -l | grep session-guardian
security skill -
low Dangerous commands
cmd-cron-mentionREADME.md:298Mentions editing / listing crontab (documentation of a security skill)crontab -l | grep session-guardian
security skill -
low Dangerous commands
cmd-cron-mentionRELEASE-v1.0.md:123Mentions editing / listing crontab (documentation of a security skill)crontab -l | grep session-guardian
security skill -
low Dangerous commands
cmd-cron-mentionscripts/install.sh:66Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "^#" | grep -v "^$" || echo " (无)"
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:77Mentions editing / listing crontabcrontab -l > /tmp/crontab.backup 2>/dev/null || true
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:80Mentions editing / listing crontab(crontab -l 2>/dev/null || true; cat << EOF
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:97Mentions editing / listing crontab (string literal in code, not executed)echo " crontab -e"
code literal -
low Dangerous commands
cmd-cron-mentionscripts/status.sh:112Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "session-guardian"; then
-
low Dangerous commands
cmd-cron-mentionscripts/status.sh:114Mentions editing / listing crontabcrontab -l 2>/dev/null | grep "session-guardian" | while read line; do
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 28. 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 51/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
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1881 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 22 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -232 emoji in the instructions: noise for the model
- -36 of 13 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 758: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.