BF proof-point-packager
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. 证据模块/证据卡/客户案例/主张对齐
turns claims-ledger-approved proofs into reusable proof modules — stat cards, case snippets, testimonial blocks, comparison proofs — each pinned to a…
As a process F 47/100 · Will not run — References files that are not bundled: ../../../references/tale-benchmark.md, ../../../protocol/offer-claims-registry/SKILL.md, ../../architect/story-bank-builder/SKILL.md
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 811 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: ../../../references/tale-benchmark.md - warning
missing-refreference to a missing file: ../../../protocol/offer-claims-registry/SKILL.md - warning
missing-refreference to a missing file: ../../architect/story-bank-builder/SKILL.md - warning
missing-refreference to a missing file: ../narrative-cascade-planner/SKILL.md - warning
missing-refreference to a missing file: ../../evaluate/narrative-quality-auditor/SKILL.md - warning
missing-refreference to a missing file: ../../architect/message-system-architect/SKILL.md - warning
missing-refreference to a missing file: ../../../launch/assemble/message-house-builder/SKILL.md - warning
missing-refreference to a missing file: ../../../protocol/narrative-registry/SKILL.md - warning
missing-refreference to a missing file: ../../../references/skill-contract.md - warning
missing-refreference to a missing file: ../../../CONNECTORS.md - warning
missing-refreference to a missing file: ../../../SECURITY.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 47/100
- 0Tools and files. 11 referenced file(s) missing: ../../../references/tale-benchmark.md, ../../../protocol/offer-claims-registry/SKILL.md, ../../architect/story-bank-builder/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 22 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 2703 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +3Description length 811: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Description says when NOT to use the skill
- +4Structure: 9 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.