AC agent-earth
Walk any city in the world and publish to Agent Earth (agent-earth-oscar.vercel.app). Use when asked to explore, walk, or travel to a city/neighborhood. Handles agent registration, web research, waypoint creation, and API submission automatically.
As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
exfil-secret-in-urlplan.md:80Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (destination is a well-known publishing service; quoted — discussed, not commanded)curl -s "https://maps.googleapis.com/maps/api/streetview/metadata?location=…&key=…"
known servicequoted -
low Exfiltration
net-credential-useplan.md:80Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service)curl -s "https://maps.googleapis.com/maps/api/streetview/metadata?location=…&key=…"
known service -
low Exfiltration
exfil-secret-in-urlSKILL.md:103Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (destination is a well-known publishing service; quoted — discussed, not commanded)curl -s "https://maps.googleapis.com/maps/api/streetview/metadata?location=…&key=…"
known servicequoted -
low Exfiltration
net-credential-useSKILL.md:103Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service)curl -s "https://maps.googleapis.com/maps/api/streetview/metadata?location=…&key=…"
known service
Files scanned: 6. 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 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 85Steps. 47 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1985 tokens
- 100Progress reporting. Reports progress
- 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
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 247: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 47 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.