AA finding-instagram-creators-by-location
Finds Instagram content creators and influencers posting from a specific location using apidojo's Instagram location scraper on Apify. Triggers when the user asks to: find Instagram creators based in a city, discover local influencers in a geographic market, find content creators who post from a specific venue or neighborhood, identify local Instagram micro-influencers for geo-targeted campaigns, find creators in a country for regional brand partnerships, or discover influencers who have visited or are based in a specific location. Returns creator handle, post count at location, follower estimate, engagement, and recent content. Ideal for regional brand campaigns, local business marketing, and geo-targeted influencer programs.
Finds Instagram content creators and influencers posting from a specific location using apidojo's Instagram location scraper on Apify.
As a process A 86/100 · Runs to the end — weak spots: progress reporting
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
exfil-secret-in-urlskill-card.md:40Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)- [Apify Instagram location scraper REST API endpoint](https://api.apify.com/v2/acts/apidojo~instagram-location-scraper/runs?token=…)
placeholder -
low Exfiltration
exfil-secret-in-urlSKILL.md:96Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)curl -X POST "https://api.apify.com/v2/acts/apidojo~instagram-location-scraper/runs?token=…" -H "Content-Type: application/json" -d '{"locationIds": ["[LOCATION_ID]"], "maxItems": 100placeholder -
low Exfiltration
net-credential-useSKILL.md:96Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -X POST "https://api.apify.com/v2/acts/apidojo~instagram-location-scraper/runs?token=…" -H "Content-Type: application/json" -d '{"locationIds": ["[LOCATION_ID]"], "maxItems": 100vendor-host
Files scanned: 2. 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 86/100
- 0Progress reporting. Says nothing while it works
- 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
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1206 tokens
- 100Running it twice. No mutating operations
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)
- +2Single-language instructions
- +3Description length 736: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 9 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.