BD memory-backup-skill
记忆备份与跨渠道同步技能。用于：（1）将对话中的重要内容自动写入记忆文件；（2）跨渠道同步记忆；（3）通过 Git 推送到远程仓库备份；（4）工作流文档的存储与恢复。当用户说"把这段内容存进记忆"、"帮我记住"、"备份记忆"、"同步记忆"、"从备份恢复"时触发。也可在每次重要对话结束时主动沉淀记忆。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Secrets in code
secret-private-keyscripts/memory-sync.sh:46Private key material (key header without key body; quoted — discussed, not commanded)"-----BEGIN PRIVATE KEY----- …
header onlyquoted -
medium Secrets in code
secret-private-keyscripts/memory-sync.sh:47Private key material (key header without key body; quoted — discussed, not commanded)"-----BEGIN PRIVATE KEY----- …
header onlyquoted -
medium Secrets in code
secret-private-keyscripts/memory-sync.sh:48Private key material (key header without key body; quoted — discussed, not commanded)"-----BEGIN PRIVATE KEY----- …
header onlyquoted -
low Dangerous commands
cmd-cron-mentionreferences/setup-guide.md:77Mentions editing / listing crontabcrontab -e
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/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
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 818 tokens
- low 12 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
- +1No license
- +2Single-language instructions
- +3Description length 150: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.