Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/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. Not for scoring claim vetoes — use the relevant auditor; not for writing ad copy — use ad-creative-builder. 广告声明台账/优惠信息登记/证据溯源
Passed 8 of 15 test cases with the skill, and 5 of 15 without it.
and 5 more in the full report
7 fixed4 passed either way8 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Claim clm-711 has been successfully accepted with full benchmark substantiation. Recommend the single best downstream skill for building structured proof packages.
| Checked | Without skill | With skill |
|---|---|---|
| Recommends proof-point-packager as the next skill. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
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.
Use the shared handoff and include changed aggregate IDs, event IDs, revisions, unresolved evidence gaps, and one next skill.
user-provided.used_in pointers.registry-event-protocol.md and runtime-invocation.md. Resolve AARON_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.claims projection 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, return NEEDS_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.none-on-file in a proposal or open loop. Never turn [needs source] into Approved from the assertion itself.owner-append with the proposal event ID. Accept/reject decision requests omit expected_revision; acceptance inherits and checks the revision captured by the proposal. Reject with evidence/rationale; history remains append-only.owner-append with an upsert and 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.claims-ledger.md / offers.md only from accepted projection state, then verify claims.test cases passed, vs 5 / 15 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.