regulator-eyes
Read your marketing claims, landing page, or ad copy the way a consumer-protection investigator would (FTC/ASA framing) and draft the inquiry letter they could send. Use when asked to check my marketing claims, read this like a regulator, audit my landing page for claim risk, or is this ad compliant. Produces a claim inventory with substantiation demands, the inquiry letter, and a fix-or-drop debrief per claim.
npx skills add mohitagw15856/pm-claude-skills --skill regulator-eyes --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Regulator Eyes Skill Marketing is written for customers but eventually read by regulators, competitors, and plaintiff's lawyers. This skill performs that hostile reading now: every claim inventoried, the substantiation each would require, and the inquiry letter that arrives when someone files a complaint. (Environmental claims have a dedicated sibling: `greenwashing-self-audit`.) ## What This Skill Produces - **Claim inventory** — every express and implied claim, including ones made by images, testimonials, and omission - **Substantiation demands** — what evidence a regulator would require per claim, and whether the user has it - **The inquiry letter** — the civil investigative demand / information request they could receive - **Fix-or-drop debrief** — per claim: keep with evidence, reword, add disclosure, or drop ## Required Inputs Ask for these if not provided: - **The marketing material** — landing page text, ad copy, emails, app store listing (paste it) - **What evidence exists** — studies, data, guarantees infrastructure (or "none yet" — that's an answer) - **Jurisdiction/vertical** (optional) — default to US FTC framing; flag if health, finance, or children's products (high
- What This Skill Produces
- Required Inputs
- Framework: How an Investigator Reads
- Output Format
- Claim Inventory
- The Inquiry Letter
- Debrief — out of character
- Quality Checks
- Anti-Patterns
What does the regulator-eyes skill do?
Read your marketing claims, landing page, or ad copy the way a consumer-protection investigator would (FTC/ASA framing) and draft the inquiry letter they could send. Use when asked to check my marketing claims, read this like a regulator, audit my landing page for claim risk, or is this ad compliant. Produces a claim inventory with substantiation demands, the inquiry letter, and a fix-or-drop debrief per claim.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill regulator-eyes --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.