CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 disciplined routing-and-spec skill: the workflow is well sequenced with explicit stop conditions and a Done-when checklist, paths and event-write mechanics are exact, and every external reference is labeled with its role. Its main weakness is redundancy — the scope exclusions and the five-builder routing list are each restated three to four times, which inflates token cost without adding information.

Suggestions

State the not-for exclusions and the five-builder routing list once (in the Scope guard) and refer to them elsewhere as 'per the Scope guard' — the current three to four restatements are the single largest token cost in the body.

Inline a minimal one-line shape for the handoff brief and drift-list entries (or a compact example) so the outputs can be produced without opening skill-contract.md, which would also raise actionability.

Tighten the multi-clause sentences in the intro and Skill Contract (e.g., the 100+ word intro paragraph) by moving the TALE L1 veto framing to the tale-benchmark reference, keeping the body to the operating contract.

DimensionReasoningScore

Conciseness

No space is wasted explaining concepts Claude already knows, but the routing contract is stated repeatedly: "never writes the surface copy" appears in the intro, Scope guard, step 6 ("angles and constraints, not finished copy"), and Done-when; the five-builder link list ([content-writer], [ad-creative-builder], [email-creative-builder], [social-creative-builder], [message-house-builder]) is repeated in full in both the Scope guard and step 6. This matches anchor 3 — mostly efficient but could be meaningfully tightened — rather than anchor 4, since whole duplicated sections, not just stray sentences, could be cut.

3 / 5

Actionability

Concrete and executable for an instruction-only skill: exact paths ("memory/narrative-registry/", "memory/narrative/narrative-cascade-planner/YYYY-MM-DD-<topic>.md", "memory/events/claims.ndjson"), exact operation semantics ("operation: propose" request to registry-events.py), defined spec fields ("pillar, lead claim + ledger status, proof, objection reframe, localization note"), and copy-paste Quick Start invocations. Falls short of anchor 5 because the actual output shapes — the handoff summary and save-results templates — are only pointed at externally ("[skill-contract.md §Handoff Summary Format]"), so the artifact cannot be produced from this file alone.

4 / 5

Workflow Clarity

Seven clearly sequenced steps (confirm canon → load inventory → write specs → build drift list → sweep claims → cut briefs → label and hand off) with explicit entry checkpoints: step 1 stops with "NEEDS_INPUT" and routes on a missing canon, step 2 says "do not guess which surfaces exist", and a Done-when checklist closes the run. Anchor 5 requires validate→fix→retry feedback loops; here recovery is stop-and-route rather than fix-and-revalidate, so anchor 4 is the better fit.

4 / 5

Progressive Disclosure

The bundle is a single SKILL.md with no local references/ or scripts/ directories; all external pointers (tale-benchmark.md, skill-contract.md, CONNECTORS.md, SECURITY.md, and sibling SKILL.md files) are one level deep and each carries a purpose label in the Reference Materials section (e.g., "the only scorer of cross-surface consistency (TALE profile result + L1)"). Good structure and clear navigation, but a substantial amount of contract prose (the repeated builder lists and exclusion clauses) is inlined where a reference file would carry it — anchor 4 rather than anchor 5.

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.

A model description: concrete third-person capability statement, three quoted natural trigger phrases, a complete when/what pairing, and explicit boundary routing to four neighboring skills. The length is dense but every clause is functional scoping rather than padding, so it fully meets the top anchors on all four dimensions.

DimensionReasoningScore

Specificity

Multiple concrete actions with comprehensive coverage: "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". Both actions are fully enumerated with their inputs and outputs, matching the anchor-5 example's level of detail; nothing is left abstract.

5 / 5

Completeness

Explicitly answers both: "Use when the user asks to..." with three concrete trigger phrases, and a precise what (per-surface message-match spec + handoff briefs, with spec contents spelled out). It even adds explicit when-not guidance ("Not for writing the finished surface copy... use each discipline creative builder"), exceeding the anchor-5 example.

5 / 5

Trigger Term Quality

Leads with three verbatim natural user asks — '"plan how our narrative lands on every surface"', '"write per-surface message-match specs"', '"brief each creative builder from the canon"' — plus the full surface list, builder names, intent phrasing ("the same story lands consistently everywhere"), and CJK synonyms (叙事落地/逐面消息一致/创意交接简报). Coverage of what a user of this ecosystem would naturally say is comprehensive; not anchor 4 because no common variation within the domain is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche — per-surface message-match specs and creative handoff briefs — with explicit de-confliction against four adjacent skills: "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", plus the not-for-copy clause. Minimal conflict risk; the routing is exactly what anchor 5 rewards.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

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: 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

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.