CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

narrative-enablement-kit

Use when the user asks to "make everyone tell the same story", "write our elevator pitch ladder", or "build a spokesperson Q&A and approved boilerplate pack"; derives from the narrative-registry canon, message house, and brand voice a repeatable enablement kit — an elevator ladder (10-second / 30-second / 2-minute), a spokesperson Q&A (tough questions with on-canon answers), an approved boilerplate/bio pack (25 / 50 / 100-word), and a do/don't language sheet — so sales, support, founders, and partners repeat one consistent story. Not for the launch-day runbook — use launch-day-conductor; not for finished per-channel copy — use content-writer or each discipline creative builder; not for launch-window battle cards — use sales-enablement-kit; this kit never adjudicates a claim. 叙事赋能包/电梯梯度/发言人问答/审定样板/该说不该说

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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, well-routed instruction skill with a clear contract, explicit validation gates, and exemplary progressive disclosure through annotated one-level-deep references. Its main weakness is token efficiency — the claims-proposal procedure and deliverable list are each restated four to five times — and the absence of a worked example of the kit's output format.

Suggestions

State the `[needs source]` → claims.ndjson `operation: propose` procedure once (e.g., in the Skill Contract) and reference it from steps 3, 6, and Save Results instead of repeating the full sentence five times.

Add one short worked example — a sample 30-second ladder rung or a single spokesperson Q&A entry with an on-canon answer — so the expected output format is unambiguous.

Trim the deliverable enumeration (elevator ladder / Q&A / boilerplate / do-don't) from the intro, Quick Start, and Skill Contract down to one canonical statement, keeping the rest as shorter references to it.

DimensionReasoningScore

Conciseness

The body is dense and free of concept-explaining filler, but repeats the same procedure verbatim several times: "marked `[needs source]` and submitted to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py`" appears in the scope guard, the Skill Contract Writes entry, instructions steps 3 and 6, and Save Results; the elevator-ladder/boilerplate deliverable list is also restated four times. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than score 4's 'minor instances'.

3 / 5

Actionability

As an instruction-only skill the guidance is concrete: each step specifies exact structure ("10-second (the onlyness sentence + the single strongest pillar)", "2-minute (old world → the shift → the promised land → proof)", "25 / 50 / 100-word"), exact read/write paths, and a done-when checklist. Not 5 because there is no worked example of any output artifact (a sample ladder rung, Q&A entry, or do/don't row) that would make the expected format copy-paste unambiguous.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with real checkpoints: step 1 is a validation gate (stop with `NEEDS_INPUT` and route if no canon; confirm if stale), step 6 is a label-and-sweep pass, and the three-condition done-when list closes it out. Not 5 because the final consistency validation is delegated entirely to the next skill (narrative-quality-auditor) rather than performed or re-checked inline — most checkpoints present, minor gap.

4 / 5

Progressive Disclosure

The body is a compact, well-sectioned overview (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) whose details live one level deep in clearly signaled references: the handoff format and banned-vocabulary list are delegated to skill-contract.md, the TALE framework to tale-benchmark.md, security handling to SECURITY.md, each annotated with what it provides in the Reference Materials section. No bundle files exist to verify beyond these one-level-deep, well-signaled pointers.

5 / 5

Total

16

/

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 deliverables with variants, explicit 'Use when' triggers in the user's own words, and explicit negative routing to adjacent skills. The only gap is a few missing natural synonyms (e.g., 'talking points', 'messaging guide').

DimensionReasoningScore

Specificity

The description enumerates the full deliverable set concretely: "an elevator ladder (10-second / 30-second / 2-minute), a spokesperson Q&A (tough questions with on-canon answers), an approved boilerplate/bio pack (25 / 50 / 100-word), and a do/don't language sheet". This matches the anchor for multiple specific concrete actions with comprehensive coverage; not score 4 because there are no minor gaps — every output of the kit is named with its variants.

5 / 5

Completeness

It explicitly answers both questions: what ("derives ... a repeatable enablement kit" with the four named components) and when ("Use when the user asks to ..." with three concrete trigger phrases), plus explicit when-not-to redirects. This matches the anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quoted natural trigger phrases like "make everyone tell the same story", "write our elevator pitch ladder", and "build a spokesperson Q&A and approved boilerplate pack" are phrases a user would plausibly say, plus deliverable keywords (elevator pitch, boilerplate, Q&A). Not 5 because common synonyms such as "talking points", "messaging guide", or "sales script" are absent; not 3 because coverage clearly goes beyond a few generic keywords and includes whole natural utterances.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche and actively disambiguates: "Not for the launch-day runbook — use launch-day-conductor; not for finished per-channel copy — use content-writer ... not for launch-window battle cards — use sales-enablement-kit; this kit never adjudicates a claim". Minimal conflict risk with explicitly named sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

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

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/land/narrative-enablement-kit/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.