A hasdata
Fetch real-time web data via the hasdata CLI. Use when the user wants search results, news, fact-checks, product or seller info, current prices, reviews, real-estate listings or sold comps, vacation rentals, local-business contact details, job postings, salary research, search trends, images, flights, social profiles, or to scrape any URL (HTML / markdown / AI-extracted JSON). Also use when the user asks to summarize a web page, ground a prompt with current information, verify a URL is live or render a JavaScript-heavy page, monitor a price over time, find a phone number or address for a business, build a competitor map, identify recent sold comparables, gather employer reviews, fan out a list of items to per-item details, or check what's being said online about a topic right now. Backed by Google, Bing, Amazon, Shopify, Zillow, Redfin, Airbnb, Yelp, YellowPages, Indeed, Glassdoor, Instagram, Google Maps / Trends / News / Images / Flights / Events APIs.
- Safety 60%
- Quality 40%
- Tests bonus
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 skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Add evals/evals.json with 4–6 real requests and expected answers: the full check will then use your cases instead of a model draft.
- Add a spec.yaml with triggers and assertions (skilltest init): the behaviour contract for CI.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME.md:14Pipe-to-shell installer from a well-known host (still executes remote code)curl -sSL https://raw.githubusercontent.com/HasData/hasdata-cli/main/install.sh | sh
-
low Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:19Pipe-to-shell installer from a well-known host (still executes remote code) (quoted — discussed, not commanded)- `command -v hasdata` — if missing, install with `curl -sSL https://raw.githubusercontent.com/HasData/hasdata-cli/main/install.sh | sh`.
quoted
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Lint
- note
frontmatter-keyunknown frontmatter key "homepage"
Process maturity 73/100
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (hasdata) differs from the folder (hasdata-api)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 42 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 2546 tokens
- 100Progress reporting. Reports progress
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 967: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 10 headings
- +3Step-by-step instructions: 42 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.