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

92%

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

85%Weight 40%Scale 1-3

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 orchestration skill with a clear sequenced workflow, explicit validation/stop checkpoints, and clean one-level reference navigation. Its main weakness is conciseness — the same exclusion boundaries are restated across multiple sections, adding tokens without new information.

Suggestions

Consolidate the scope/exclusion list into one place (e.g., the Scope guard) and have other sections reference it rather than re-listing the same four neighboring skills verbatim.

Break the single long 'Scope guard' sentence into a short bullet list of boundaries so it scans faster and trims tokens.

The Reference Materials section largely duplicates links already inline in Scope guard and Instructions; consider keeping only references not already cited inline.

Dimension	Reasoning	Score
Conciseness	Dense and operational with no concept-explanation fluff, but the exclusion list recurs nearly verbatim across the description, the 'Scope guard' paragraph, the Instructions, and the Reference Materials, and the scope-guard sentence is one long link-stuffed block that could be tightened.	2 / 3
Actionability	Gives concrete, executable guidance for an instruction-only skill — exact paths (memory/narrative-registry/, memory/claims/claims-ledger.md), concrete operations ('operation: propose' request to registry-events.py), per-surface spec fields, and explicit done-when criteria.	3 / 3
Workflow Clarity	A clear numbered 1–7 sequence with explicit checkpoints and stop conditions: step 1 stops with NEEDS_INPUT if no canon, step 5 sweeps unapproved claims to [needs source], step 4 builds the drift list, plus 'Done when' criteria and inherited termination rules (visited-set, max-depth: 3).	3 / 3
Progressive Disclosure	Content is split into well-signaled sections with one-level-deep markdown links to specific files (tale-benchmark.md, skill-contract.md, CONNECTORS.md, SECURITY.md) and sibling skills; no nested reference chains. No bundle files are present, so this is scored on the reference structure, which is clean and navigable.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 highly specific, well-triggered description that clearly states capabilities, opens with explicit 'Use when' triggers, and draws sharp boundaries against four neighboring skills. The only minor blemish is length and a few imperative exclusion clauses, but voice stays predominantly third person.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'maps the narrative-registry canon onto every flagship surface', 'cuts a handoff brief to each discipline's creative builder', naming the exact surfaces and builders; far beyond vague 'helps with' language. The dominant voice is third person ('maps', 'cuts'), with only scoped imperative routing in the exclusion clauses.	3 / 3
Completeness	Explicitly answers both what (maps canon to surfaces as message-match specs, cuts handoff briefs) and when (opens with 'Use when the user asks to...'), so the 'Use when' trigger guidance is present and explicit.	3 / 3
Trigger Term Quality	Quotes natural user-sayable triggers verbatim — 'plan how our narrative lands on every surface', 'write per-surface message-match specs', 'brief each creative builder from the canon' — giving good coverage of phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Carries a clear niche and explicit anti-triggers — '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', making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 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: 4a77c48

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