BF google-maps
A Google Maps API alternative and Google Places API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no Google Cloud billing account. Use when the user wants to search places by text query or anchor the search to a latitude/longitude coordinate, fetch a place's full details by its feature ID (fid), pull a place's reviews sorted by relevance/newest/rating, or look up a single review by ID. Also covers local business discovery, points-of-interest data, store-locator input, and review monitoring without Google Cloud Platform's API key setup, billing, and per-request pricing.
A Google Maps API alternative and Google Places API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no Google…
As a process F 39/100 · Will not run — References files that are not bundled: ../fetcher/SKILL.md
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
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Exfiltration
net-credential-useSKILL.md:41Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:70Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:78Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:88Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:91Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../fetcher/SKILL.md - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 39/100
- 0Tools and files. 1 referenced file(s) missing: ../fetcher/SKILL.md
- 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
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (google-maps) differs from the folder (google-maps-api)
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 100Steps. 10 steps
- 100Execution cost. Instruction body is 1015 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 626: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.