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

87%

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

75%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, actionable skill body with a clear contract, sequenced workflow, and explicit guards (labeling, pre-flight, ask-before-write). Main weaknesses are mild cross-reference redundancy and the absence of exact script invocations and explicit error-recovery loops.

Suggestions

Show a concrete invocation example for at least one connector script (e.g. `python scripts/connectors/firecrawl.py <url>`) so the workflow is copy-paste executable.

Add an explicit validate→fix→retry checkpoint for the scrape and save steps (e.g. on robots-disallow or empty scrape, retry with a proxy label or mark User-provided).

De-duplicate the downstream handoff: state the primary next skill once in Next Best Skill and reference it from the other sections rather than restating it four times.

Dimension	Reasoning	Score
Conciseness	Lean and free of beginner-concept padding, but the downstream skill (positioning-truth-tracer) and the same sibling skills are restated across Skill Contract, Instructions, Reference Materials, and Next Best Skill — minor redundancy that could be trimmed. Not a 5 because of that repeated cross-referencing.	4 / 5
Actionability	Concrete named tools (firecrawl.py, tavily.py, wayback.py), specific memory paths, and a 7-step workflow with explicit output labeling rules give mostly executable guidance; falls short of 5 only because exact script invocations are not shown (script names without call syntax).	4 / 5
Workflow Clarity	A clearly sequenced 7-step process with a 'Done when' completion checklist, robots pre-flight, and untrusted-input handling on every scrape; not a 5 because there is no explicit validate→fix→retry feedback loop for batch scrape/write operations.	4 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep, clearly signaled references (tale-benchmark.md, skill-contract.md, CONNECTORS.md, SECURITY.md); not a 5 because no bundle files exist in this skill and several referenced paths point outside the bundle, so navigation cannot be fully verified.	4 / 5
	Total	16 / 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 high-quality description: concrete capabilities, natural trigger phrases, and explicit scope boundaries that prevent overlap with sibling skills. Voice is appropriately third-person throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'dominant stories and points of view', 'language conventions and framing clichés', 'per-competitor narrative teardown (arc, claimed onlyness, proof pattern)', and messaging drift over time — giving comprehensive coverage of what the skill produces.	5 / 5
Completeness	Explicitly answers both 'what' (produces a category narrative map with named components) and 'when' (opens with 'Use when the user asks to...'), each with concrete trigger phrases.	5 / 5
Trigger Term Quality	Three natural quoted trigger phrases ('map the category narrative', 'tear down how competitors tell their story', 'find the language conventions in our market') are exactly the kind of phrasing a marketing user would say, plus negative triggers for neighboring skills.	5 / 5
Distinctiveness Conflict Risk	Four explicit 'not for...use X' boundaries (positioning-mapper, audience-belief-mapper, keyword-research, offer-claims-registry) carve a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 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: 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
Commit: 64562bc

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