BC admin
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster & external users, audit/errors/metrics/egress) accepts your token when the user you're talking to is an org admin and started this turn themselves. Use when an admin asks you to inspect or change anything org-wide or in another scope, or anyone asks whether they're an admin.
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster &…
As a process C 55/100 · Has gaps — References files that are not bundled: setup.submitUrl
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:58Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -fsS -H "x-agent-capability: $AGENT_API_TOKEN" "$AGENT_API_URL/v1/admin/..."
security skill
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: setup.submitUrl
Process rating: all ten parameters 55/100
- 0Tools and files. 1 referenced file(s) missing: setup.submitUrl
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 16 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 100Steps. 21 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3678 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (9 tags): a typed call is more reliable
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 426: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.