AC rest-graphql-debug
Debug REST/GraphQL APIs: status codes, auth, schemas, repro.
Debug REST/GraphQL APIs: status codes, auth, schemas, repro.
As a process C 58/100 · Has gaps — weak spots: when it triggers, inputs and preconditions
Runs in: Hermes Agent
How to improve
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:157Credential used in a network call (verify the destination is the intended service) (security demo / example; quoted — discussed, not commanded)terminal('curl -s -o /dev/null -w "%{http_code}\\n" -H "Authorization: Bearer $TOKEN" https://api.example.com/me')demoquoted
Files scanned: 1. 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 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, 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. 49 steps
- 100Execution cost. Instruction body is 3786 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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 60: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 38 headings
- +3Step-by-step instructions: 49 items
- +3Output format is stated explicitly
- +4Has examples (24 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.