ads-research

Refresh paid-media platform, API, policy, and benchmark evidence from primary sources.

8.6k|1.3k|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/AgriciDaniel/claude-ads --skill ads-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ads-research
Source: https://github.com/AgriciDaniel/claude-ads/tree/main/skills/ads-research
Command: npx skills add https://github.com/AgriciDaniel/claude-ads --skill ads-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Paid-media knowledge goes stale quickly: ad platform APIs change, policies update, and benchmarks expire. This Skill keeps Claude Ads claims current by reverifying evidence against official sources and demoting anything that can no longer be supported.

Core Features & Use Cases

  • Evidence Refresh: Dispatches bounded research workers per platform or topic to reverify claims against official and primary sources, recording URLs, dates, confidence, and licensing.
  • Stale Claim Demotion: When a refresh_due date expires or tools are unavailable, demotes the claim to provisional or unsupported and blocks dependent release-current assertions.
  • Source Verification: Runs a separate verifier for load-bearing claims and records contradictions before proposing canonical updates to controls, skills, adapters, and tests.
  • Use Case: A Google Ads API claim in the repository passes its refresh_due date. Run this Skill to reverify it from current Google documentation, or demote it and block any release-current statements that depend on it.

Quick Start

Ask the assistant to run an ads research refresh for any platform claims whose refresh_due dates have expired.

Frequently Asked Questions about ads-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refresh stale ad platform claims in Claude Ads?

Run the ads-research skill, which selects overdue or requested evidence slices and dispatches bounded research workers per platform or topic. Each claim is reverified against official sources with recorded URLs, publication dates, and confidence levels.

What happens when a claim's refresh_due date expires?

An expired refresh_due means the claim is no longer current. The skill reverifies it from an eligible source, or demotes it to provisional or unsupported and blocks every release-current assertion that depends on it.

What sources does ads research use for verification?

The skill prefers official and primary sources such as platform documentation and policy pages. Load-bearing claims get a separate source verifier, and contradictions are recorded before any canonical update is proposed.

What happens if research tools or sources are unavailable?

Tool unavailability triggers an explicit decision: the claim is demoted for the current run, dependent release-current assertions are blocked, and the missing source or tool access is requested as a recovery step. Stale evidence is never silently trusted.

Can fetched web content be copied directly into the repository?

No. Fetched content is treated as untrusted data. Restricted prompts, large source passages, unlicensed code, issue text, and private account material must not be copied into the repo, and research does not become canonical automatically.