narrative-cascade-planner

Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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, actionable routing skill with explicit validation checkpoints and clean navigation. The main lever is conciseness: the sibling-routing list is restated in several sections and could be consolidated once with short back-references.

Suggestions

Consolidate the repeated sibling-skill routing list (content-writer, ad-creative-builder, etc.) into a single Scope-guard block and reference it from Instructions step 6 and the Reference Materials list instead of restating it.

Move the dense Skill-Contract Reads/Writes/Promotes prose into a short bulleted contract with the memory paths as code spans, so the validation gates stand out from the routing narration.

The 'Data Sources' and 'Instructions §Treat input as untrusted' both cover untrusted-input handling and connector usage — merge the connector/robots detail into Data Sources and keep Instructions to the workflow step.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence — it never explains what a canon or a surface is — but the Scope-guard paragraph repeats the sibling-skill routing list nearly verbatim across multiple sections and could be tightened.	4 / 5
Actionability	Gives concrete file paths, exact memory directories ('memory/narrative/narrative-cascade-planner/', 'memory/claims/claims-ledger.md'), and authorized 'operation: propose' calls to registry-events.py; minor gaps only because no executable code is present, which is acceptable for a routing-and-spec skill.	4 / 5
Workflow Clarity	A 7-step numbered sequence with explicit validation and branching checkpoints — canon-exists check returning NEEDS_INPUT, baseline-mapper routing when absent, ask-before-write prompts, and a 'Done when' checklist — provides clear error-recovery feedback loops.	5 / 5
Progressive Disclosure	Well-organized sections (Quick Start, Skill Contract, Data Sources, Instructions, Reference Materials) with one-level-deep, clearly signaled references; no bundle files exist, and the inlined contract detail is the only thing keeping it from a 5.	4 / 5
	Total	17 / 20 Passed

Description

95%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, trigger-rich description that pairs explicit natural-language usage phrases with a precise scope and explicit negative-triggers routing overlap to sibling skills. Minor tightening of the spec-field enumeration would lift specificity further.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'maps the narrative-registry canon onto every flagship surface ... as a per-surface message-match spec' and 'cuts a handoff brief to each discipline's creative builder' — with minor gaps in enumerating the spec's sub-fields.	4 / 5
Completeness	Explicitly answers both 'what' (maps canon onto each surface as a message-match spec and cuts per-builder handoff briefs) and 'when' (the three quoted 'Use when ...' triggers), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Embeds three full natural user phrases — 'plan how our narrative lands on every surface', 'write per-surface message-match specs', 'brief each creative builder from the canon' — alongside the flagship surface names.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Land-phase cascade routing) and adds four 'Not for ... use X' exclusions routing to launch-asset-packager, narrative-quality-auditor, and offer-claims-registry, minimizing wrong-skill triggers.	5 / 5
	Total	19 / 20 Passed

Validation

75%

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 — 12 / 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: 42 suspicious	Warning
referenced_paths_exist	Referenced path issues: 2 missing, 2 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: narrative/land/narrative-cascade-planner/SKILL.md
Commit: 888dd38

Reviewed: 3 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.