CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pitch-narrative-builder

Use when the user asks to "build our pitch deck narrative", "write a fundraising story", or "structure the sales pitch narrative"; derives from the narrative canon a company pitch/deck narrative — problem → the undeniable shift → product-as-hero → proof → the ask — as a slide-beat outline (one narrative beat per slide, with the claim ID each proof beat rests on), for both a sales pitch and a fundraising deck. Every proof beat is labeled Measured / User-provided / '[needs source]' and unverified ones route to the claims candidates. Not for the launch-window battle cards and talk track — use sales-enablement-kit; not for the durable message hierarchy or the arc itself — use message-system-architect / strategic-narrative-designer; not for finished deck visual design — out of scope; not for claim adjudication — use offer-claims-registry. 路演叙事/融资故事/销售 pitch/幻灯节拍

Quality

81%

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

70%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 an unusually disciplined workflow: clear sequencing, explicit validation checkpoints, stop conditions, and a done-when checklist. Its weaknesses are heavy repetition of the same claim-proposal governance rule and the fact that none of its many referenced files ship in the bundle, leaving the reference layer unresolvable as delivered.

Suggestions

State the 'propose to registry-events.py, never write the ledger directly' rule once (e.g., in the Skill Contract) and reference it from steps 4, 6, and Save Results instead of repeating it verbatim.

Include a short template or worked example of the slide-beat outline output (beat → slides → claim ID → label) so the primary deliverable is copy-paste shaped rather than only described.

Ship the referenced files (skill-contract.md, tale-benchmark.md, humanizer-slop.md, etc.) inside the skill's own references/ directory or trim the links, since none of the current relative paths resolve within this bundle.

DimensionReasoningScore

Conciseness

The body is operational rather than tutorial-style and explains nothing Claude already knows, but the same governance rule is repeated nearly verbatim at least five times ("via an authorized `operation: propose` request to `registry-events.py`" appears in the scope guard, Writes, Promotes, step 4, and Save Results), and cross-skill routing is restated across multiple sections. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean 4/5 anchors.

3 / 5

Actionability

Concrete, executable guidance throughout: exact paths (memory/narrative-registry/canon.md, memory/claims/claims-ledger.md), copy-paste Quick Start invocations, explicit metric labels (Measured / User-provided / Estimated with as-of date), and a defined output shape. It stops short of the 5 anchor because the slide-beat outline and handoff summary are described but no template or worked example of the deliverable is provided inline.

4 / 5

Workflow Clarity

Seven numbered steps in a clear sequence with explicit checkpoints and feedback loops: step 1 stops with NEEDS_INPUT if no canon exists, step 6 flags an L1 contradiction and stops, runs a banned-word rewrite pass and a slop self-check, plus a 'Done when' checklist and termination rules (max-depth 3, ambiguity stop, visited set). This matches the top anchor's 'explicit validation steps; feedback loops; checklists for complex processes'.

5 / 5

Progressive Disclosure

Sections are well organized and the Reference Materials list clearly signals each link with a one-line purpose, but the bundle contains no references/, scripts/, or assets/ directories — every linked path (tale-benchmark.md, skill-contract.md, humanizer-slop.md, CONNECTORS.md, SECURITY.md, and six sibling SKILL.md files) resolves outside the bundle to files that are not present, so the navigation layer cannot actually be followed. This places it between 'references present but not clearly signaled / could be better organized' and 'good structure; references mostly clear'.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description: concrete capabilities, explicit trigger phrases in two languages, a clear what/when pair, and unusually thorough negative boundaries that route users away from neighboring skills. The only weakness is that its action coverage is bundled into long clauses rather than fully itemized, and a few natural trigger synonyms are missing.

Suggestions

Add common trigger synonyms such as "investor deck", "fundraising deck", or "pitch story" to broaden natural-phrase coverage.

Surface the per-audience ask variants (raise/use-of-funds vs next-step framing) as a concrete capability so the action list is fully itemized.

DimensionReasoningScore

Specificity

Names several concrete actions — "derives from the narrative canon a company pitch/deck narrative", rendered "as a slide-beat outline (one narrative beat per slide, with the claim ID each proof beat rests on)", "Every proof beat is labeled Measured / User-provided / '[needs source]'", and routing of unverified claims to candidates. This matches the 'several specific actions; minor gaps' anchor rather than the 5 anchor, whose coverage is more exhaustively itemized (e.g., the per-audience ask variants are not surfaced in the description).

4 / 5

Completeness

Explicitly answers 'what' (derives the five-beat pitch narrative as a slide-beat outline for both a sales pitch and a fundraising deck) and 'when' ("Use when the user asks to..." with three concrete trigger phrases), and adds explicit 'not for' exclusions. This clearly matches the top anchor with concrete trigger phrases; a missing 'Use when' clause would have capped it at 3, but it is present.

5 / 5

Trigger Term Quality

Gives natural quoted trigger phrases ("build our pitch deck narrative", "write a fundraising story", "structure the sales pitch narrative") plus bilingual synonyms (路演叙事/融资故事/销售 pitch/幻灯节拍). A few natural terms a user would plausibly say are missing ("investor deck", "fundraising deck", "pitch story"), so it sits between the 4 and 5 anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (pitch/deck narrative derivation) and actively disambiguates from four adjacent skills ("Not for the launch-window battle cards and talk track — use sales-enablement-kit; not for the durable message hierarchy or the arc itself...; not for finished deck visual design...; not for claim adjudication — use offer-claims-registry"), matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

18

/

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/pitch-narrative-builder/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.