← Back to list
proof-point-packager ✓ Security reviewed
Use when the user asks to "package our proof points", "build reusable stat cards and case snippet…
⚡ Productivity By aaron-he-zhu Version v1.0.0 Updated 2026-09-03
7.0Overall rating

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "proof-point-packager" skill by following the instructions at https://skill123.me/install/proof-point-packager.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/proof-point-packager.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 4 KB

About this skill

Overview

Use when the user asks to "package our proof points", "build reusable stat cards and case snippets", or "put proof where each pillar makes its claim"; turns claims-ledger-approved proofs into reusable proof modules — stat cards, case snippets, testimonial blocks, comparison proofs — each pinned to a message-house pillar and the ledger claim ID it substantiates, and flags any pillar making a claim with no approved proof behind it. Never adjudicates a proof: unverified or ledger-absent proofs are marked ''[needs source]'' and routed to the claims candidates. Not for adjudicating or substantiating claims — use offer-claims-registry; not for fabricating a benchmark to fill a gap — a missing proof is flagged, not invented; not for scoring narrative quality — use narrative-quality-auditor. 证据模块/证据卡/客户案例/主张对齐

Source

  • Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
  • Path: narrative/land/proof-point-packager

Evaluation

AI-evaluated 2026-09-03: Well-contracted packaging workflow with per-module claim-ID pinning, as-of dating, a proof-gap list, and a hard no-fabrication rule (missing proof is flagged, never invented). Ecosystem-coupled like the rest of the suite, so practical value outside that repo setup is limited.

Score breakdown

Quality
8.0
Usability
5.0
Security
8.0
Popularity
7.0