BC capacities
Manage Capacities notes, daily entries, and weblinks.
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
net-credential-useSKILL.md:27Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)`curl -X POST https://api.capacities.io/save-to-daily-note -H "Authorization: Bearer $CAPACITIES_API_TOKEN" -H "Content-Type: application/json" -d '{"spaceId": "$CAPACITIES_SPACE_ID", "mdText": "Yourvendor-hostquoted -
low Exfiltration
net-credential-useSKILL.md:31Credential used in a network call (verify the destination is the intended service) (security demo / example; the skill's own vendor host; quoted — discussed, not commanded)`curl -X POST https://api.capacities.io/save-weblink -H "Authorization: Bearer $CAPACITIES_API_TOKEN" -H "Content-Type: application/json" -d '{"spaceId": "$CAPACITIES_SPACE_ID", "url": "https://exampldemovendor-hostquoted -
low Exfiltration
net-credential-useSKILL.md:35Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)`curl -X POST https://api.capacities.io/lookup -H "Authorization: Bearer $CAPACITIES_API_TOKEN" -H "Content-Type: application/json" -d '{"spaceId": "$CAPACITIES_SPACE_ID", "searchTerm": "My Note"}'`vendor-hostquoted -
low Exfiltration
net-credential-useSKILL.md:39Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)`curl -X GET "https://api.capacities.io/space-info?spaceid=…" -H "Authorization: Bearer $CAPACITIES_API_TOKEN"`
vendor-hostquoted
Files scanned: 2. 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 52/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Steps. 2 steps
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 315 tokens
- 100Running it twice. No mutating operations
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 53: 120–800 characters recommended
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: suspicious
The skill matches its Capacities note-taking purpose, but its shell examples need review because unsafe value substitution could run unintended local commands.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026