BD clawback
Backup and restore your OpenClaw workspace to GitHub
As a process D 44/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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Broad scope
meta-agent-memory-dumpHEARTBEAT.mdAgent memory / workspace files bundled with the skill (4) — likely a workspace dump with personal data or tokensHEARTBEAT.md, IDENTITY.md, SOUL.md, USER.md
-
low Exfiltration
read-dotenvREADME.md:9Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvSKILL.md:83Reads a .env filecp .env.example .env
-
low Secrets in code
secret-github-tokenSKILL.md:143GitHub token (placeholder value)echo "My API key is ghp_…xyz" > /tmp/test-workspace/AGENTS.md
placeholder -
low Secrets in code
secret-labelled-tokenSKILL.md:163Labelled token / key literal (vendor format unknown — verify it is not a live credential) (placeholder value)echo "Real API key: sk-r…890" > /tmp/test-workspace/AGENTS.md
placeholder
Files scanned: 13. 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 44/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. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (clawback) differs from the folder (clawsync)
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 36 steps
- 100Execution cost. Instruction body is 1154 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- +3Description length 52: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -212 emoji in the instructions: noise for the model
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 18 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.