proof-point-packager

Packages approved claims-ledger proofs into reusable stat cards, case snippets, and testimonial blocks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Marketing claims often ship without verified evidence behind them, or proof exists but is scattered and never placed where the claim is made. This Skill turns claims-ledger-approved proofs into reusable proof modules pinned to each message-house pillar, and flags every pillar making a claim with no approved proof behind it. ## Core Features & Use Cases - Proof Module Packaging: Builds stat cards, case snippets, testimonial blocks, and comparison proofs, each tagged with its pillar, ledger claim ID, and a Measured/User-provided label with as-of date. - Gap Detection: Lists every pillar whose claim lacks approved proof and routes unverified proofs to the claims ledger as '[needs source]' proposals, never fabricating benchmarks or statistics. - Use Case: After your message house and story bank exist, ask the Skill to package proof points for each pillar; it produces a proof module set plus a gap list ready for the narrative quality auditor to score. ## Quick Start Package proof points for my product from the approved claims ledger, building stat cards and case snippets for each message-house pillar and flagging any pillar with no approved proof.

Frequently Asked Questions about proof-point-packager

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

FAQPage Schema
How do I package proof points for marketing claims?▼

Provide the product name, the message-house pillars, and your proof material such as case data, benchmark exports, or permitted quotes. The Skill builds stat cards, case snippets, testimonial blocks, and comparison proofs, each tagged with its pillar and ledger claim ID.

What is a proof module in a message house?▼

A proof module is a reusable evidence unit — a stat card, case snippet, testimonial block, or comparison proof — pinned to a message-house pillar and the claims-ledger claim ID it substantiates. Every module carries a Measured or User-provided label with an as-of date.

Can this Skill verify or approve marketing claims?▼

No. It only packages proofs already approved in the claims ledger. Unverified or ledger-absent proofs are marked '[needs source]' and routed to the claims registry for adjudication; it never adjudicates claims itself.

What happens when a pillar has no approved proof?▼

The pillar is added to a gap list and routed to the claims candidates as a '[needs source]' proposal. The Skill flags the gap rather than inventing a benchmark, rounding an unsourced figure, or borrowing a competitor's number.

What inputs does proof packaging require?▼

It requires an existing message house with pillars, approved entries in the claims ledger, reusable story units from the story bank, and user-provided proof material such as case data, benchmark exports, and permitted testimonials. If no message house exists, it stops and routes to the message-system-architect.