Individual skill
narrative-baseline-mapper
Use when the user asks to "map what our surfaces say today", "inventory our current messaging", or "find the gap between what we say and what we mean"; produces the narrative baseline — a surface-by-surface inventory of what every owned touchpoint (homepage, pricing, docs, decks, social bios, email footers) claims RIGHT NOW, each line labeled Measured / User-provided / Estimated, plus a per-surface gap read vs the intended message and the drift-baseline snapshot the Evaluate phase measures future drift against. Not for authoring the canon — use message-system-architect; not for scoring the surfaces or running the vetoes — use narrative-quality-auditor. 现状叙事盘点/各触点口径/意图差距/漂移基线
narrative/trace/narrative-baseline-mapper/SKILL.md
Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,134
- Repository last updated
- Nov 12, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- geo Repository topic
- seo Repository topic
- agent-skills Repository topic
- content-optimization Repository topic
- generative-engine-optimization Repository topic
- marketing Repository topic
- influencer-marketing Repository topic
- paid-advertising Repository topic
- roas Repository topic
- email-marketing Repository topic
- docs Derived category
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Narrative Baseline Mapper
Inventories what every owned surface says **today** — the homepage headline, the pricing page value line, the docs intro, the pitch-deck one-liner, the social bios, the email footer — and reads each against the intended message to expose the gap. It is the first move of the TALE **Trace** phase and the "before" snapshot the rest of the narrative work is measured against. It feeds the [TALE](../../../references/tale-benchmark.md) **T** (Truth) dimension — specifically the *positioning matches shippable reality* and *surface-truth* reads — and freezes the **drift baseline** that the Evaluate phase (`narrative-drift-monitor`) measures future surface drift against. It never scores and never authors: it records the current state so the gap is visible.
**Scope guard**: this skill produces the surface inventory + gap read only. It does **not** author the canon or the message house (use [message-system-architect](../../architect/message-system-architect/SKILL.md)), reconcile the positioning canvas against shippable reality (use [positioning-truth-tracer](../positioning-truth-tracer/SKILL.md)), map the category's or competitors' stories (use [category-narrative-mapper](../category-narrative-mapper/SKILL.md)), compute the TALE profile result or run the vetoes (only [narrative-quality-auditor](../../evaluate/narrative-quality-auditor/SKILL.md) scores TALE), or adjudicate any claim it surfaces (unverifiable ones are marked `[needs source]` and submitted to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py`). It works one lever — the current-state inventory — and hands off.
## Quick Start
```
Map what our surfaces say today for [brand]. Surfaces: [homepage / pricing / docs / deck / bios / emails — URLs or paste].
```
```
Inventory our current messaging and show the gap vs our intended message: "[intended one-liner]".