offer-claims-registry

Registers marketing claims and offers with evidence provenance in an append-only event stream.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/qaz26688442/bo-car --skill offer-claims-registry-qaz26688442
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: offer-claims-registry
Source: https://github.com/qaz26688442/bo-car/tree/main/.agents/skills/offer-claims-registry
Command: npx skills add https://github.com/qaz26688442/bo-car --skill offer-claims-registry-qaz26688442

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Marketing teams lose track of which claims are substantiated, which offers are live, and where the proof for a specific figure lives. This Skill maintains a canonical, append-only registry of claim wording, evidence, disclosures, terms, and review dates so downstream builders and auditors work from accepted truth instead of stale drafts. ## Core Features & Use Cases - Claim & Offer Registration: Record exact wording, measurable interpretation, evidence source and date, required disclosures, scope, and review/expiry dates as events in claims.ndjson. - Proposal Review Workflow: Builders submit propose events; only a host-capability principal accepts or rejects them, keeping [needs source] items unresolved rather than silently approved. - Ledger Generation: Regenerate human-readable claims-ledger.md and offers.md views from the accepted projection, then verify consistency. - Use Case: When a teammate asks "where is the proof for this 30% faster figure?", query the claims projection by aggregate ID to return the accepted wording, evidence reference, scope, and review date. ## Quick Start Ask the agent to register claim clm-014 with its exact wording, evidence source and date, required disclosure, and review date in the claims registry.

Frequently Asked Questions about offer-claims-registry

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

FAQPage Schema
How do I register a marketing claim with evidence?▼

Submit a schema-valid proposal event through registry-events.py with the exact wording, evidence type, source reference, observation date, scope, and review date. A host-capability principal then accepts or rejects the proposal; only accepted events become canonical claim state.

How do I find the proof behind a specific advertising figure?▼

Query the claims projection by aggregate ID to retrieve the accepted wording, evidence_ref, evidence_date, and scope. If the claim is still marked unresolved or [needs source], no approved substantiation exists yet.

Can a builder skill approve its own claim proposals?▼

No. Ordinary producer skills can only submit propose events via registry-events.py. Acceptance or rejection requires a host-capability principal invoking owner-append with the proposal event ID, keeping approval authority separate from proposal authorship.

What happens to claims whose evidence scope is narrower than the copy?▼

The registry approves narrower wording that matches the evidence scope, or keeps the claim unresolved. Estimates and proxies are recorded as such, and [needs source] markers are never converted to approved status without real evidence.

When should I not use the offer claims registry?▼

Do not use it to score or veto whether a concrete ad use passes claim and disclosure gates; that is the job of auditors like ad-account-auditor. It also does not write ad copy, which belongs to ad-creative-builder.