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

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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, highly actionable contract skill with a clear sequenced workflow and explicit validation feedback loops. The main weakness is verbatim repetition of the claims-routing and boundary-routing language across sections.

Suggestions

State the claims.ndjson / registry-events.py routing once in the Skill Contract Writes bullet and reference it from later steps instead of repeating the full phrase in step 4 and Save Results.

Consolidate the 'Not for...' boundary list into one place (Scope guard) and let Reference Materials / Next Best Skill focus on downstream pointers to avoid overlapping the same exclusions three times.

Tighten the Data Sources and Reference Materials sections, which re-list several of the same canon/ledger/story-bank paths already named in the Skill Contract.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the claims-routing phrasing ('via an authorized operation: propose request to registry-events.py' to claims.ndjson) is repeated verbatim across the Scope guard, Writes, Instructions step 4, and Save Results, and the 'Not for...' boundary list overlaps the Reference Materials / Next Best Skill sections.	3 / 5
Actionability	Concrete file paths (memory/narrative-registry/canon.md, memory/claims/claims-ledger.md, memory/narrative/pitch-narrative-builder/), a specific seven-step process, a defined output shape, and an explicit Measured/User-provided/Estimated labeling scheme make the guidance fully actionable for an instruction-only skill.	5 / 5
Workflow Clarity	Seven clearly sequenced steps with explicit validation checkpoints — step 1 stops with NEEDS_INPUT and routes when no canon exists; step 6 runs the canon-consistency / banned-word / slop self-check and says 'flag it and stop' on a contradiction, providing the feedback loop the contract context requires.	5 / 5
Progressive Disclosure	Well-organized overview (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with one-level-deep, clearly signaled references to external skill/reference paths and no nested indirection; no local bundle files exist to misorganize.	5 / 5
	Total	18 / 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 exceptionally complete description: concrete actions, natural trigger phrases, explicit what-and-when, and clear boundary routing to adjacent skills. Written in third person with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'derives...a company pitch/deck narrative', 'rendered as a slide-beat outline (one narrative beat per slide)', labels every proof beat 'Measured / User-provided / [needs source]' and 'routes...to the claims candidates' — with comprehensive coverage of the five-beat arc.	5 / 5
Completeness	Explicitly answers both 'what' (derives the five-beat arc as a per-slide beat outline for sales and fundraising decks) and 'when' ('Use when the user asks to...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Opens with natural trigger phrases users would actually say — 'build our pitch deck narrative', 'write a fundraising story', 'structure the sales pitch narrative' — plus synonyms and the trailing keyword set '路演叙事/融资故事/销售 pitch/幻灯节拍'.	5 / 5
Distinctiveness Conflict Risk	Four explicit 'Not for...' clauses route away from sales-enablement-kit, message-system-architect / strategic-narrative-designer, finished deck visual design, and offer-claims-registry, giving it a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 888dd38

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.