category-narrative-mapper

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha a727cd638786 · 30 Oct 2026Report an issue or request a re-scan

• Publisheraaron-he-zhu GitHub userOwner of the repository this skill is read from
• Source folderaaron-he-zhu/aaron-marketing-skills/narrative/trace/category-narrative-mapperThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdicta727cd638786A new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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…

---
name: category-narrative-mapper
slug: aaron-category-narrative-mapper
displayName: "Category Narrative Mapper · 品类叙事地图"
summary: "品类主叙事/竞争叙事拆解/语言惯例/叙事演变"
description: '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. 品类叙事/竞争叙事拆解/语言惯例/叙事演变'
version: "20.2.0"
license: Apache-2.0
compatibility: "Claude Code and compatible agent-skill hosts"
homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills"
when_to_use: "Use when tracing the category's narrative landscape before authoring any brand canon: naming the dominant stories and points of view, recording the language conventions and framing clichés, teardown of each named competitor's narrative (arc, claimed onlyness, proof pattern), and how their messaging has drifted over time. The second move of the TALE Trace phase, feeding the Truth dimension's category-frame and named-alternatives sub-items. Not the positioning canvas and not audience belief work."
argument-hint: "<category / product> [named competitors] [competitor URLs]"
metadata: {"author": "aaron-he-zhu", "version": "20.2.0", "discipline": "narrative", "phase": "trace", "geo-relevance": "low", "hermes": {"tags": ["marketing", "narrative", "trace"], "category": "narrative"}, "openclaw": {"emoji": "📖", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
---

# Category Narrative Mapper

Maps the narrative landscape of the category — the dominant stories and points of view rivals tell, the language conventions and framing clichés everyone reaches for, and a per-competitor narrative teardown (each rival's arc, its claimed onlyness, its proof pattern) together with how that messaging has shifted over time (today's scraped copy against archived copy). It is the second move of the TALE **Trace** phase and feeds the [TALE](../../../references/tale-benchmark.md)-`T` (Truth) dimension directly: the *category frame chosen and defensible* sub-item (you cannot claim "the only \[frame\] that..." without knowing what frames the category already recognizes) and the *competitive alternatives named from win-loss and interviews, not a vendor feature matrix* sub-item — it supplies the narrative half of the named-alternatives set the `T1` differentiation veto is later judged against. It never scores; only [narrative-quality-auditor](../../evaluate/narrative-quality-auditor/SKILL.md) computes the TALE profile result.

**Scope guard**: this skill produces the category narrative map *document* only. It does **not** build the positioning canvas or the onlyness statement (reuse [positioning-mapper](../../../launch/research/positioning-mapper/SKILL.md)), capture the beachhead's beliefs, objections, or switching forces (that is [audience-belief-mapper](../audience-belief-mapper/SKILL.md)), do SERP keyword or ranking work ([keyword-research](../../../seo-geo/survey/keyword-research/SKILL.md)), reconcile positioning against the claims ledger ([positioning-truth-tracer](../positioning-truth-tracer/SKILL.md)), adjudicate any product or comparative claim ([offer-claims-registry](../../../protocol/offer-claims-registry/SKILL.md) is the sole writer of `memory/claims/claims-ledger.md`), or compute the TALE profile result. It works one lever — the category's narrative terrain — and hands off.

## Quick Start

```
Map the category narrative for [product / category]. Competitors: [names or "help me find them"].
```

```
Tear down how [Competitor A], [Competitor B], [Competitor C] tell their story — arc, claimed onlyness, proof pattern.
```

```
Show how [competitor]'s messaging has shifted over the last 2 years — scrape their site now and compare against the archive.
```

## Skill Contract

**Expected output**: a category narrative map — the dominant category stories and points of view, the language conventions and framing clichés (approved/overused terms), a per-competitor narrative teardown table (arc, claimed onlyness sentence, proof pattern, primary framing), and a messaging-drift note per rival (today's copy vs archived copy, with as-of dates) — every line labeled Measured / User-provided / Estimated, plus the standard handoff summary.

- **Reads**: prior [competitor-analysis](../../../seo-geo/survey/competitor-analysis/SKILL.md) findings in `memory/research/competitor-analysis/` when present; competitor public messaging via `scripts/connectors/firecrawl.py` (scrape) and `scripts/connectors/tavily.py` (search — proxy-labeled); archived competitor copy via `scripts/connectors/wayback.py` (change history); the user's own list of named competitors and URLs (User-provided). Robots pre-flight applies to every scrape.
- **Writes**: the category narrative map to `memory/narrative/category-narrative-mapper/`; any product or comparative claim it surfaces from a competitor that the user might echo is marked `[needs source]` and routed to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py` — this skill never adjudicates it. Nothing durable is written to `memory/narrative-registry/` canonical files; canon is the sole domain of [narrative-registry](../../../protocol/narrative-registry/SKILL.md).
- **Promotes**: the named-competitor set and the category frame candidates to `memory/hot-cache.md` and `memory/open-loops.md` (ask before writing); do not write `decisions.md` directly.
- **Done when**: at l

Excerpt, first 6,001 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-30
   ✓SAFE B 89 / 100

   first audit · source a727cd638786

Questions about category-narrative-mapper

• github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/narrati — the audited source at commit a727cd638786 and every finding aboveObserved · 30 Oct 2026

Spotted something wrong? Report a correction · Methodology