CD progressive-loading
Implements hub-and-spoke lazy loading to minimize token usage in large skills
As a process D 38/100 · Unfinished process — 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 · 4
-
high Dangerous commands
cmd-persistencemodules/macos-patterns.md:59Persistence mechanism (cron / launchd / scheduled task / autorun registry)~/Library/LaunchAgents/
Medium and low: 3
-
medium Dangerous commands
cmd-persistencemodules/macos-patterns.md:98Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)User-scoped agents go in `~/Library/LaunchAgents/`. System-scoped
quoted -
medium Dangerous commands
cmd-persistencemodules/macos-patterns.md:99Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)daemons go in `/Library/LaunchDaemons/` and require root. Load
quoted -
medium Dangerous commands
cmd-persistencemodules/macos-patterns.md:100Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)with `launchctl load -w <path>`, unload with `launchctl unload`.
quoted
Files scanned: 25. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_plugin"
Process rating: all ten parameters 38/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (progressive-loading) differs from the folder (nm-leyline-progressive-loading)
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 85Steps. 85 steps, 1 vague phrases
- 100Execution cost. Instruction body is 2012 tokens
- 100Progress reporting. Reports progress
- 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 77: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 20 headings
- +3Step-by-step instructions: 85 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.