# Claims Gate

Checks every claim in a piece of copy (ads, emails, posts, pages, scripts, briefs)...

- Repository: https://github.com/gooseworks-ai/goose-skills (1276 stars)
- Category: Marketing
- License: MIT
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add gooseworks-ai/goose-skills --skill claims-gate -g -a claude-code -y`
Codex: `npx skills add gooseworks-ai/goose-skills --skill claims-gate -g -a codex -y`
Cursor: `npx skills add gooseworks-ai/goose-skills --skill claims-gate -g -a cursor -y`
Gemini CLI: `npx skills add gooseworks-ai/goose-skills --skill claims-gate -g -a gemini-cli -y`

## Description

Checks every claim in a piece of copy (ads, emails, posts, pages, scripts, briefs) against the claims the brand has approved. Keeps, rewrites or cuts each line, and lists the proof that would bring a cut line back. When a line the copy needs has no approval, it asks for a short sign-off on the 3 or 4 lines that matter and records the answer. Use alone when you already have the copy and a brand set up; otherwise run the playbook for the job (e.g. make-static-ads, make-content, write-outreach).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# claims-gate

One contract for every playbook that writes copy, scripts, briefs, emails, posts, pages or captions. Only this atom ever writes a claim as approved; claims and markers already in the brand (from the GooseWorks app or an earlier brand pass) are read the same way. The calling playbook keeps its own extract step (on-image text, video scenes, page sections) and hands this atom the spans.

Say it to the human in plain words ("two lines need your OK before I use them"), never as tool, fact or playbook names.

## 1. Load the contract (once per job)

**Which path.** Use the **older path** (steps 1, 2: the marker and its `Claims you may use, ` facts) on every server today, including ones that list `brand_knowledge_*` tools: approvals customers already gave live there, and a chat sign-off recorded by §5 is usable at once. Also count a brain claim a person confirmed (step 5). Where the two disagree, the stricter wins. Steps 3, 4, 6, 7 and 8 always apply. (The **brain path**, where only brain-confirmed claims count and a chat yes waits for the app, §4.6, applies once the brand's server says chat approvals are recorded only in the app.)

**Local mode** (no GooseWorks, [the `marketing-guide` skill](../marketing-guide/SKILL.md) §5): the contract is `gooseworks-local/<brand-slug>/claims.md`, read and written by [`local-claims.md`](local-claims.md) (next to this file) in place of steps 1, 3 and 5. Only a row whose newest status is `approved` and that passes its checks (scope, date, the approver's own words, proof reopened) is usable; declined, pending and retired rows never are. The `dont`s and `must`s come from `brand-notes.md`. §2, 4 run as written, with `local-claims.md` for who approves and the record.

The rest: https://github.com/gooseworks-ai/goose-skills/blob/HEAD/skills/marketing/claims-gate/SKILL.md