CF memory-scan
(no description)
Scans MEMORY.md, daily logs (memory/.md), and workspace configuration files for malicious content, prompt injection, credential leakage, and dangerous…
As a process F 36/100 · Will not run — References files that are not bundled: scripts/memory-scan.py, scripts/schedule-scan.sh, scripts/quarantine.py
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The text references files that are not there: add them or drop the references.
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 · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
missing-refreference to a missing file: scripts/memory-scan.py - warning
missing-refreference to a missing file: scripts/schedule-scan.sh - warning
missing-refreference to a missing file: scripts/quarantine.py
Process rating: all ten parameters 36/100
Will not run. References files that are not bundled: scripts/memory-scan.py, scripts/schedule-scan.sh, scripts/quarantine.py
- 0Tools and files. 3 referenced file(s) missing: scripts/memory-scan.py, scripts/schedule-scan.sh, scripts/quarantine.py
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 55Failures and branches. 1 branches
- 100Steps. 54 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1252 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 18 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
The skill has a legitimate memory-security purpose, but needs Review because optional remote analysis can expose private memory contents and quarantine can overwrite files outside the intended memory area.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026