AB monitoring-google-news-coverage-for-brand
Monitors Google News coverage for a brand using apidojo's Google Search scraper on Apify. Triggers when the user asks to: track news coverage about a brand on Google, monitor press mentions in Google News, find recent news articles mentioning a company, track media coverage for a brand or executive, monitor competitor news coverage, find press releases or news stories about a brand on Google, or research how a company is being covered in the press. Returns article title, publication, date, URL, and coverage sentiment per article. Ideal for PR agencies, communications teams, brand managers, and reputation monitoring services.
Monitors Google News coverage for a brand 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:36Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)- [Apify Google Search Scraper API endpoint](https://api.apify.com/v2/acts/apidojo~google-search-scraper/runs?token=…)
placeholder -
low Exfiltration
exfil-secret-in-urlSKILL.md:91Credential 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. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1020 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 632: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 6 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.