CC obsidian-rest-api
Operate Obsidian via Local REST API plugin from remote/WSL environments. Use when: (1) user asks to operate Obsidian, read/write notes, or manage vault remotely; (2) working with Obsidian vault files from WSL/remote where direct filesystem access is blocked; (3) creating, editing, or searching notes through API instead of file edits.
As a process C 56/100 · Has gaps — weak spots: result and completion, 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
- 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 · 10
✓ No critical or high findings
Medium and low: 10
-
medium Exfiltration
net-credential-usereferences/api.md:63Credential used in a network call (verify the destination is the intended service)curl -k -H "Authorization: Bearer $KEY" "$URL/vault/my-note.md"
-
medium Exfiltration
net-credential-usereferences/api.md:69Credential used in a network call (verify the destination is the intended service)curl -k -H "Authorization: Bearer $KEY" \
-
medium Exfiltration
net-credential-usereferences/api.md:74Credential used in a network call (verify the destination is the intended service)curl -k -X PATCH -H "Authorization: Bearer $KEY" \
-
medium Exfiltration
net-credential-usereferences/api.md:82Credential used in a network call (verify the destination is the intended service)curl -k -X PATCH -H "Authorization: Bearer $KEY" \
-
medium Exfiltration
net-credential-usereferences/api.md:108Credential used in a network call (verify the destination is the intended service)curl -k -H "Authorization: Bearer $KEY" "$URL/vault/"
-
medium Exfiltration
net-credential-useSKILL.md:43Credential used in a network call (verify the destination is the intended service)curl -k -H "Authorization: Bearer $KEY" "$URL/"
-
medium Exfiltration
net-credential-useSKILL.md:46Credential used in a network call (verify the destination is the intended service)curl -k -H "Authorization: Bearer $KEY" "$URL/vault/"
-
medium Exfiltration
net-credential-useSKILL.md:49Credential used in a network call (verify the destination is the intended service)curl -k -X PUT -H "Authorization: Bearer $KEY" -H "Content-Type: text/markdown" \
-
medium Exfiltration
net-credential-useSKILL.md:57Credential used in a network call (verify the destination is the intended service)curl -k -X PUT -H "Authorization: Bearer $KEY" -H "Content-Type: text/markdown" \
-
medium Exfiltration
net-credential-useSKILL.md:63Credential used in a network call (verify the destination is the intended service)curl -k -X POST -H "Authorization: Bearer $KEY" -H "Content-Type: text/markdown" \
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 804 tokens
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 335: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.