CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

category-narrative-mapper

Use when the user asks to "map the category narrative", "tear down how competitors tell their story", or "find the language conventions in our market"; produces a category narrative map — the dominant stories and points of view in the category, its language conventions and framing clichés, and a per-competitor narrative teardown (arc, claimed onlyness, proof pattern) plus how each rival's messaging has shifted over time (scraped copy vs archived copy). Not for the positioning canvas itself — use positioning-mapper; not for the beachhead's beliefs and objections — use audience-belief-mapper; not for SERP keyword targeting — use keyword-research; 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 well-structured, instruction-only skill whose workflow is clearly sequenced with explicit done-when gates and concrete tool/path guidance. Its main weaknesses are redundancy — sibling-skill routing and the registry-events propose wording each repeated three times — and the absence of a sample output table or script invocation that would make the expected deliverable fully concrete.

Suggestions

State the sibling-skill routing (positioning-mapper, audience-belief-mapper, keyword-research, offer-claims-registry) once — in the Scope guard — and have Reference Materials and Next Best Skill link back to it instead of restating each handoff with new annotations.

State the claims-routing rule ("mark `[needs source]` and route to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py`") once in the Skill Contract, then reference it briefly from Instructions step 4 and Save Results rather than repeating the full wording verbatim three times.

Add a one-row example of the per-competitor teardown table (arc, claimed onlyness sentence, proof pattern, primary framing, source label) and a sample invocation of `scripts/connectors/firecrawl.py` so the expected output shape and commands are copy-paste concrete.

DimensionReasoningScore

Conciseness

The instruction steps are lean and assume competence, but the same routing content is repeated: sibling-skill handoffs appear in the Scope guard ("reuse positioning-mapper... audience-belief-mapper... keyword-research..."), again in Reference Materials, and a third time in Next Best Skill, while "an authorized `operation: propose` request to `registry-events.py`" appears verbatim three times (Skill Contract Writes, Instructions step 4, Save Results). This matches the 3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than 4, where trimming would be only minor.

3 / 5

Actionability

Concrete, executable guidance throughout: named tools ("Scrape with `scripts/connectors/firecrawl.py` and label each row Measured with the source URL"), exact paths ("write `memory/narrative/category-narrative-mapper/YYYY-MM-DD-<topic>.md`"), and a precise labeling convention (Measured / User-provided / Estimated / proxy). Falls short of the 5 anchor because no script invocation examples or a sample teardown-table row/output template are shown — the expected output is described only in prose.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with checkpoints: a robots pre-flight on every scrape, "Done when" exit criteria ("every named competitor has a teardown row... sourced with a Measured URL or marked User-provided/Estimated"), and ask-before-write gates ("ask before writing", "Do not write memory without asking"). Not a 5 because there are no error-recovery feedback loops (e.g., what to do when a competitor has no archived snapshot or a scrape fails), leaving minor validation gaps at the 4 anchor.

4 / 5

Progressive Disclosure

No bundle files exist alongside this SKILL.md, and the body is a well-sectioned overview with one-level-deep references, each link annotated ("[tale-benchmark.md](../../../references/tale-benchmark.md) — TALE framework; this skill feeds the `T` category frame..."). Good structure with mostly clear references, but the same links surface in three separate sections (Scope guard, Reference Materials, Next Best Skill) and the referenced paths (CONNECTORS.md, scripts/connectors/*.py) live outside this bundle and cannot be verified — minor organization gaps at the 4 anchor rather than the clean split of the 5 anchor.

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.

An exemplary description: concrete what, explicit when with natural quoted trigger phrases, and four explicit not-for routings that sharply delimit it from sibling skills. The trailing Chinese summary repeats the summary field, which adds slight length but also Chinese-language trigger coverage, not padding.

DimensionReasoningScore

Specificity

Quotes multiple concrete capabilities: "produces a category narrative map — the dominant stories and points of view in the category, its language conventions and framing clichés, and a per-competitor narrative teardown (arc, claimed onlyness, proof pattern) plus how each rival's messaging has shifted over time (scraped copy vs archived copy)" — a comprehensive, concrete inventory of what the skill does. This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); it exceeds 4 because coverage is complete rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both questions: "Use when the user asks to..." (when, with concrete trigger phrases) and "produces a category narrative map — ..." (what, in detail). Fits the 5 anchor exactly (both what AND when with concrete trigger phrases); a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Opens with natural quoted phrases a user would actually say: "map the category narrative", "tear down how competitors tell their story", "find the language conventions in our market", and adds Chinese synonyms (品类叙事/竞争叙事拆解/语言惯例/叙事演变). Matches the 5 anchor's comprehensive natural-term coverage; below it there is no missing common variation relevant to this niche.

5 / 5

Distinctiveness Conflict Risk

Clear niche (category narrative terrain) with explicit negative routing to four sibling skills: "Not for the positioning canvas itself — use positioning-mapper; not for the beachhead's beliefs and objections — use audience-belief-mapper; not for SERP keyword targeting — use keyword-research; not for claim adjudication — use offer-claims-registry." Minimal conflict risk, matching the 5 anchor; the disambiguation is stronger than the 4 anchor's 'minor overlap risk'.

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

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/trace/category-narrative-mapper/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.