BF planning-with-files
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
Implements Manus-style file-based planning for complex tasks.
As a process F 40/100 · Will not run — References files that are not bundled: reference.md, examples.md, scripts/session-catchup.py
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.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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
- The text references files that are not there: add them or drop the references.
- 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 Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Bash Glob Grep WebFetch WebSearch
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:44Runs PowerShell with execution policy bypassedpwsh -ExecutionPolicy Bypass -File "$SCRIPT_DIR/chec…ps1" 2>/dev/null ||
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:45Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File "$SCRIPT_DIR/chec…ps1" 2>/dev/null ||
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:48Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File "$SCRIPT_DIR/chec…ps1" 2>/dev/null ||
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: reference.md - warning
missing-refreference to a missing file: examples.md - warning
missing-refreference to a missing file: scripts/session-catchup.py
Process rating: all ten parameters 40/100
- 0Tools and files. 3 referenced file(s) missing: reference.md, examples.md, scripts/session-catchup.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1472 tokens
- 100Progress reporting. Reports progress
- low 14 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 263: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.