BC canvas
Fetch Canvas LMS courses and assignments via API token.
Fetch Canvas LMS courses and assignments via API token.
As a process C 63/100 · Has gaps — weak spots: 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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Exfiltration
net-redirectable-api-keyscripts/canvas_api.py:20Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Exfiltration
net-credential-useSKILL.md:74Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $CANVAS_API_TOKEN" \
-
medium Exfiltration
net-credential-useSKILL.md:78Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $CANVAS_API_TOKEN" \
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "prerequisites"
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 9 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 727 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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 55: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 8 headings
- +3Step-by-step instructions: 9 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.