CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

strategic-narrative-designer

Use when the user asks to "design our change narrative", "build the old-world-to-new-game story arc", or "frame the shift our category is undergoing"; produces a Raskin-style strategic narrative arc — old world → the undeniable shift → winners vs losers under the new rules → the promised land → proof the promised land is real — derived from the positioning truth set and the belief/objection map, feeding the TALE Architecture arc sub-item. Every proof beat is labeled Measured / User-provided / [needs source] and this skill never adjudicates a claim. Not for the message house hierarchy — use message-system-architect; not for the pitch deck narrative — use pitch-narrative-builder; not for claim substantiation — use offer-claims-registry. 变革叙事弧/旧世界/应许之地/战略叙事结构

Quality

81%

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.

The body is well structured with a gated, validated workflow and specific file-level guidance, but it is padded with repeated claim-routing and scope boilerplate and provides no worked example of the deliverable it specifies. Tightening the repetition and showing one filled-in five-beat arc would raise both conciseness and actionability.

Suggestions

State the claims.ndjson routing rule once (e.g. in the Skill Contract) and reference it from steps 6 and Save Results instead of repeating the full "authorized operation: propose request to registry-events.py" clause four times.

Add a short worked example of a completed five-beat arc (even 5-10 lines) so the expected output shape is concrete rather than only described.

Deduplicate the skill routing between the Reference Materials and Next Best Skill sections, or fold the scope-guard exclusions out of the body since the description already carries them.

DimensionReasoningScore

Conciseness

The claim-routing boilerplate ("via an authorized `operation: propose` request to `registry-events.py`" to `memory/events/claims.ndjson`) is repeated nearly verbatim in the scope guard, Writes, step 6, and Save Results, and the Reference Materials / Next Best Skill sections re-list the same four skills — more than minor over-explanation, so 3 rather than 4.

3 / 5

Actionability

Seven steps name exact sources, labels, destinations, and connectors (e.g. `scripts/connectors/tavily.py`, `memory/narrative/strategic-narrative-designer/`) and Quick Start gives ready prompts, but there is no worked example of a finished arc and output shapes are delegated to skill-contract.md, which is not in this bundle — concrete guidance with minor gaps, matching 4 not 5.

4 / 5

Workflow Clarity

Clear 7-step sequence with an explicit upstream gate (step 1 stops with NEEDS_INPUT and routes), a self-check step (empty-chair test, labeling check), and "Done when" criteria — but no recovery path when a check fails (e.g. arc contradicts existing canon), so 4 rather than 5.

4 / 5

Progressive Disclosure

Well-sectioned body with a clearly labeled Reference Materials list giving one-line descriptions, but it leans on external references (../../../references/skill-contract.md, tale-benchmark.md, CONNECTORS.md, SECURITY.md, five sibling SKILL.md files) that are absent from this bundle — good structure with organization gaps, matching 4 not 5.

4 / 5

Total

15

/

20

Passed

Description

92%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 five-beat output structure, explicit quoted triggers in two languages, clear what/when, and explicit routing away from adjacent skills. Only weakness is slightly incomplete synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

Enumerates the full output structure ("old world → the undeniable shift → winners vs losers under the new rules → the promised land → proof the promised land is real") plus concrete labeling behavior ("Every proof beat is labeled Measured / User-provided / [needs source]") in third-person voice — comprehensive concrete coverage with no gaps, matching the 5 anchor rather than the minor-gaps 4 anchor.

5 / 5

Completeness

Explicitly answers both: what ("produces a Raskin-style strategic narrative arc" with its five beats and inputs) and when ("Use when the user asks to..." with concrete trigger phrases) — exactly the 5 anchor; not 4 since the when-clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Natural quoted triggers ("design our change narrative", "build the old-world-to-new-game story arc", "frame the shift our category is undergoing") plus bilingual synonyms (变革叙事弧/旧世界/应许之地) give good coverage, but a few natural variations (e.g. plain "story arc", "messaging narrative") are missing, so it fits the 4 anchor rather than comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Explicit anti-triggers name every adjacent skill ("Not for the message house hierarchy — use message-system-architect; not for the pitch deck narrative — use pitch-narrative-builder; not for claim substantiation — use offer-claims-registry"), giving a clear niche with minimal conflict risk per the 5 anchor.

5 / 5

Total

19

/

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 3 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/architect/strategic-narrative-designer/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.