AB tracking-google-serp-rankings
Tracks Google search rankings and SERP features for any keyword using apidojo's Google Search scraper on Apify. Triggers when the user asks to: check Google rankings for a keyword, see who ranks on page 1 for a search term, track SERP positions for a list of keywords, monitor competitor rankings on Google, find featured snippets or People Also Ask boxes for a query, analyze the search results landscape for a topic, audit top-ranking content for a keyword, or research organic search competition for SEO. Returns ranking position, URL, title, snippet, and SERP feature type per result. Ideal for SEO managers, content strategists, and digital marketing agencies.
Tracks Google search rankings and SERP features for any keyword using apidojo's Google Search scraper on Apify.
As a process B 73/100 · Nearly there — 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-secret-in-urlskill-card.md:46Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)- [Apify actor run API endpoint from artifact](https://api.apify.com/v2/acts/apidojo~google-search-scraper/runs?token=…)
placeholder -
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) (placeholder value)"https://api.apify.com/v2/acts/apidojo~google-search-scraper/runs?token=…" \
placeholder
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 73/100
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (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. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1356 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 665: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 15 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.