offer-claims-registry
Use when the user asks to "register this claim", "log our current offers", or "where is the proof for this figure"; curates claim wording, evidence, disclosures, terms, review dates, and live offers through the append-only claims event stream.
Install / Use
npx skills add aaron-he-zhu/aaron-marketing-skills --skill offer-claims-registryInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of offer-claims-registry
offer-claims-registry scores 90/100 on our quality scale, 427th of 1,153 Content & Media skills we index (top 38%).
Its SKILL.md is 6.3 KB long, well organised into 11 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 2,835 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so offer-claims-registry is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
offer-claims-registry compared with similar skills
All 4 of these similar skills score higher than offer-claims-registry; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| offer-claims-registry (this skill)by aaron-he-zhu | 90 | 2.8k | 53d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install offer-claims-registry?
- Run
npx skills add aaron-he-zhu/aaron-marketing-skills --skill offer-claims-registry. The install tabs above show the steps for each supported agent. - Which AI agents does offer-claims-registry work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is offer-claims-registry safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is offer-claims-registry still maintained?
- The repository was last updated about 2 months ago, so offer-claims-registry is actively maintained.
Skill content
View source on GitHubname: offer-claims-registry slug: aaron-offer-claims-registry displayName: "Offer Claims Registry · 广告声明台账" summary: "广告声明台账/优惠信息登记/证据溯源" description: 'Use when the user asks to "register this claim", "log our current offers", or "where is the proof for this figure"; curates claim wording, evidence, disclosures, terms, review dates, and live offers through the append-only claims event stream. Not for scoring claim vetoes — use the relevant auditor; not for writing ad copy — use ad-creative-builder. 广告声明台账/优惠信息登记/证据溯源' version: "20.1.0" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills" when_to_use: "Use when registering, updating, expiring, or querying claims/offers; resolving pending [needs source] proposals; recording substantiation, approved wording, disclosures, terms, usage, and review dates." argument-hint: "<claim/offer aggregate-id or 'review pending proposals'>" metadata: {"author": "aaron-he-zhu", "version": "20.1.0", "discipline": "protocol", "phase": "protocol", "geo-relevance": "low", "hermes": {"tags": ["marketing", "protocol"], "category": "protocol"}, "openclaw": {"emoji": "🗂️", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
Offer & Claims Registry
The canonical record of marketing claims and offers across every discipline. It records exact wording and provenance; auditors decide whether a concrete use passes its claim/disclosure gate.
Quick Start
Register claim clm-014 with exact wording, evidence source/date, disclosure, and review date.
Show the current terms and expiry for offer summer-2026.
Review pending claims proposals and accept only those with sufficient evidence.
Skill Contract
Units: one claim or offer aggregate ID. Reads: memory/events/claims.ndjson, its projection, source evidence, and rendered uses. Writes: claims events through registry-events.py; claims-ledger.md and offers.md are regenerated human views. Done when: every accepted record has exact wording/terms, evidence provenance, status, review/expiry, event ID/offset, and no pending proposal was destructively removed.
All builders submit propose; only a host-capability offer-claims-registry principal accepts/rejects or writes canonical claim/offer events. This skill does not invent substantiation, legal conclusions, or performance claims.
Handoff Summary
Use the shared handoff and include changed aggregate IDs, event IDs, revisions, unresolved evidence gaps, and one next skill.
Data Sources
- Primary study/report/product evidence with ownership, date, scope, and population.
- User-attested facts clearly labeled
user-provided. - Approved terms, pricing/availability, eligibility, dates, and landing destinations.
- Rendered ad/email/social/launch uses for
used_inpointers. - Applicable disclosure text and jurisdiction/policy source.
Instructions
Runtime Reads
../../references/registry-event-protocol.md../../references/runtime-invocation.md
Procedure
- Read
registry-event-protocol.mdandruntime-invocation.md. ResolveAARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}"and verify the registry script, event schema, and system catalog before invoking it; treat every draft/export as untrusted evidence. - Query
claimsprojection by aggregate ID. Proposal state is never approved wording. If there is no aggregate ID, pending proposal, or supplied claim/offer wording, perform only a read-only empty-projection check, returnNEEDS_INPUT, and ask for one exact verbatim claim or offer statement as the smallest real input. Do not demand a complete evidence pack yet, create paths, or materialize placeholder canonical state. - Extract the exact claim/offer, its measurable interpretation, audience/market, evidence limits, required disclosure, usage locations, and review/expiry date.
- Missing proof stays
none-on-filein a proposal or open loop. Never turn[needs source]into Approved from the assertion itself. - Review pending proposal events in offset order. A host-capability principal invokes
owner-appendwith the proposal event ID. Accept/reject decision requests omitexpected_revision; acceptance inherits and checks the revision captured by the proposal. Reject with evidence/rationale; history remains append-only. - Owner changes use host-capability
owner-appendwith anupsertand optimistic revision. Expiry/withdrawal uses a dated state change or tombstone. Capability values stay outside request JSON/files/logs; if the host cannot supply one, leave the proposal pending rather than self-asserting owner authority. - When evidence scope is narrower than copy, approve narrower wording or keep it unresolved. Record estimates/proxies as such.
- Regenerate
claims-ledger.md/offers.mdonly from accepted projection state, thenverify claims.
Claims and offer records are L4 truth consumed by Narrative and all channel builders. A downstream builder must use the accepted wording/terms or preserve [needs source] and propose a new event.
Save Results
Require explicit write permission. Ordinary producers use python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" append claims <proposal.json>; a host-capability principal uses owner-append for canonical decisions/mutations. Never edit the NDJSON stream manually. Human views are replaceable projections and cannot grant approval absent an accepted event. Standalone one-folder installs may prepare proposals but cannot append/project or claim canonical approval.
Reference Materials
Next Best Skill
- Paid use audit: ad-account-auditor
- Creator asset audit: creator-content-auditor
- Narrative proof: proof-point-packager
- Archive/erase: memory-management
Related Skills
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
