regulator-eyes

GitHub

模拟监管视角审查营销材料,识别显性/隐性主张及遗漏风险。生成证据需求清单、监管问询函草稿及整改建议,帮助规避合规隐患。

plugins/pm-simulators/skills/regulator-eyes/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

检查我的营销主张 像监管机构一样阅读此内容 审计落地页的主张风险 评估广告是否合规

Install

npx skills add mohitagw15856/pm-claude-skills --skill regulator-eyes -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-simulators/skills/regulator-eyes -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@regulator-eyes

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill regulator-eyes -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "regulator-eyes",
    "description": "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."
}

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 (higher bar)

Framework: How an Investigator Reads

Pass Looking for
1. Express claims Direct statements: "fastest", "clinically proven", "saves 40%", "#1"
2. Implied claims What a reasonable consumer takes away — before/afters, testimonials as typical results, comparison imagery
3. Material omissions Conditions, fees, auto-renewals, "results not typical" realities left unsaid
4. Format traps Fake countdown timers, dark-pattern cancellation, undisclosed endorsements/affiliates

Risk scale: 🔴 enforcement-grade (deceptive on its face or unsubstantiated health/money claim) · 🟡 challengeable (defensible only with evidence the user must produce) · 🟢 puffery (opinion no reasonable consumer takes literally — "the best coffee in town").

Judge claims by the net impression on a reasonable consumer, not the writer's intent — that is the actual legal standard's shape.

Output Format


Regulatory Reading: [Asset] — [date]

Simulation — a plausible adversarial reading, not a prediction or legal advice.

Claim Inventory

# Claim (verbatim) Type (express/implied/omission) Substantiation required User has it? Risk

The Inquiry Letter

[A formal information request citing the specific claims, demanding the substantiation, with a response deadline — the document that starts a very bad quarter.]

Debrief — out of character

# Verdict New wording or required disclosure
[keep / reword / disclose / drop for every 🔴 and 🟡]

Confirm anything load-bearing with an advertising-law attorney — standards vary by jurisdiction and vertical.


Quality Checks

  • Implied claims and omissions are inventoried, not just literal sentences
  • Every 🔴 names the specific missing substantiation, not "needs evidence"
  • Puffery is honestly rated 🟢 — inflating everything to red destroys the signal
  • The letter cites the user's actual claims verbatim
  • Every red/yellow claim gets a concrete verdict with replacement wording where kept

Anti-Patterns

  • Do not grade intent — grade the net impression on a reasonable consumer
  • Do not invent claims the material doesn't make; the inventory quotes the source
  • Do not offer "add an asterisk" as a fix for a deceptive net impression — disclosures cure omissions, not lies
  • Do not treat testimonials as safe because they're "just customers talking" — typicality is the user's problem
  • Do not stay in character in the debrief

Version History

  • 54fad50 Current 2026-07-19 13:11

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
6d56a619
Indexed
2026-07-19 13:11

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-29 19:24
浙ICP备14020137号-1 $방문자$