CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. 证据模块/证据卡/客户案例/主张对齐

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction-only skill with concrete paths, a defined routing protocol, and a self-checking six-step workflow. Its main weakness is token efficiency: the no-adjudication, no-fabrication, and registry-write boundary rules are each restated three to four times across sections, and the proof-module formats would be crisper with one worked example.

Suggestions

State each boundary rule once (in the Scope guard) and reference it elsewhere with a short label — the 'never writes memory/narrative-registry/ canonical files' routing rule alone appears in Writes, Save Results, and Reference Materials, roughly 60 words each time.

Add one compact worked example of a finished proof module (e.g., a filled-in stat card with pillar tag, claim ID, Measured label, and as-of date) so the 'Done when' criteria are verifiable against a concrete artifact.

Close the workflow loop on self-check failure: after step 6's confirmations, state what to do when a check fails (e.g., strip the module and add the pillar to the gap list) instead of proceeding straight to handoff.

DimensionReasoningScore

Conciseness

Mostly efficient operational detail, but the same boundary rules are restated repeatedly: 'this skill packages, it does not adjudicate' appears in the intro, scope guard, and steps 2 and 5, and the 'never writes memory/narrative-registry/ canonical files, which narrative-registry alone owns' routing rule appears three times. Not a 2 because the padding is redundant restatement of real rules, not explanation of concepts Claude already knows.

3 / 5

Actionability

Concrete guidance throughout — exact memory paths, an exact routing mechanism ('operation: propose request to registry-events.py'), and defined module shapes (stat card: one metric, Measured/User-provided source, as-of date; case snippet: situation → what changed → result). Minor gaps: no rendered example of a finished proof module, and the handoff-summary shape is fully deferred to an external file. As an instruction-only skill, absence of code is not penalized.

4 / 5

Workflow Clarity

Six clearly numbered steps with an explicit self-check checklist ('confirm every module has a pillar tag, a ledger claim ID, and a labeled source with an as-of date') and a NEEDS_INPUT stop-and-route checkpoint in step 1. Not a 5 because there is no explicit recovery loop when the self-check fails — anchor 5's example requires an 'if errors: fix and re-validate' path, but step 6 simply says 'Then hand off'.

4 / 5

Progressive Disclosure

Well-organized sections (Quick Start, Skill Contract, Instructions, Reference Materials) with clearly signaled references, each carrying a one-line purpose statement. Scored against the actual bundle: no references/, scripts/, or assets/ directories exist, so all eight linked files resolve outside the skill directory and cannot be navigated from the skill's own bundle — a minor organization gap rather than a structural failure.

4 / 5

Total

15

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete third-person actions, quoted natural trigger phrases with bilingual synonyms, explicit use-when guidance, and named anti-trigger boundaries that sharply separate it from adjacent skills in the same suite. No fluff or over-claims despite the length.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — turning approved proofs into stat cards, case snippets, testimonial blocks, and comparison proofs, pinning each to a pillar and ledger claim ID, and flagging unproven pillars — with comprehensive coverage of the skill's behavior. Third-person voice is used throughout, so no voice penalty applies.

5 / 5

Completeness

Explicitly answers both questions: a concrete 'what' (four proof module types, each pinned to a pillar and claim ID, plus gap flagging) and an explicit 'Use when the user asks to...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Three quoted natural trigger phrases ('package our proof points', 'build reusable stat cards and case snippets', 'put proof where each pillar makes its claim') plus bilingual synonyms (证据模块/证据卡/客户案例/主张对齐) give comprehensive coverage of how users would actually phrase the request.

5 / 5

Distinctiveness Conflict Risk

Clear niche (packaging ledger-approved proof only) with explicit anti-triggers naming the adjacent skills: 'Not for adjudicating or substantiating claims — use offer-claims-registry... not for scoring narrative quality — use narrative-quality-auditor'. Minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 33 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/land/proof-point-packager/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.