narrative-resonance-monitor
Use when the user asks to "measure how our narrative is landing", "track echo rate against our canon lexicon", or "check how AI answer engines describe our brand"; produces a resonance report — echo rate (overlap of market language with the narrative-registry canon lexicon, method declared), AI-answer perception via tavily.py --answer (proxy-labeled), share-of-voice on a locked competitor panel (reusing share-of-voice-tracker), and resonance signals from bluesky.py / gdelt.py / pageviews.py — every number labeled Measured / proxy / User-provided, feeding the TALE E dimension and the upstream o
npx skills add aaron-he-zhu/aaron-marketing-skills --skill narrative-resonance-monitor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Narrative Resonance Monitor Measures whether the durable brand narrative is actually landing in the market — an **echo rate** (how much of the market's own language overlaps the narrative-registry canon lexicon, with the matching method declared), an **AI-answer perception** read (how answer engines describe the brand versus the canon, via `scripts/connectors/tavily.py --answer`, proxy-labeled), **share-of-voice** on a locked competitor panel, and public **resonance signals** from Bluesky / GDELT / Wikipedia-attention. It sits in the **Evaluate** phase of the TALE loop and is the resonance-evidence feed for the `E` dimension — specifically the upstream of the `E1` evidence-integrity veto: the *proxy-not-Measured* discipline, echo-rate-with-declared-method, and AI-answer-perception sub-items (see [tale-benchmark.md](../../../references/tale-benchmark.md)). It reads the canon lexicon but never edits it, and it never adjudicates a claim. **Scope guard**: this skill produces the resonance report only. It does **not** rebuild share-of-voice tracking (it *reuses* [share-of-voice-tracker](../../../social/observe/share-of-voice-tracker/SKILL.md) — same locked-panel machinery, narrative/m
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Save Results
- Reference Materials
- Next Best Skill
What does the narrative-resonance-monitor skill do?
Use when the user asks to "measure how our narrative is landing", "track echo rate against our canon lexicon", or "check how AI answer engines describe our brand"; produces a resonance report — echo rate (overlap of market language with the narrative-registry canon lexicon, method declared), AI-answer perception via tavily.py --answer (proxy-labeled), share-of-voice on a locked competitor panel (reusing share-of-voice-tracker), and resonance signals from bluesky.py / gdelt.py / pageviews.py — every number labeled Measured / proxy / User-provided, feeding the TALE E dimension and the upstream o
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill narrative-resonance-monitor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.