Installation
Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.
Install the "narrative-drift-monitor" skill by following the instructions at https://skill123.me/install/narrative-drift-monitor.
Run in your terminal — downloads and installs to ~/.claude/skills/.
curl -fsSL https://skill123.me/install/narrative-drift-monitor.sh | bash
Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.
⬇ Download v1.0.0 · 5 KBAbout this skill
Overview
Use when the user asks to "check if our surfaces have drifted from the canon", "watch for competitor repositioning", or "define when we should reposition"; produces a drift report — self-drift per flagship surface vs the narrative-registry canon over time (via wayback.py, change history Measured with as-of dates), competitor-repositioning alerts, an explicit repositioning-trigger condition set, and a D1/W1/M1 message-shift retro (intended vs actual pull-through, evidence-labeled) — feeding the TALE L drift-audit sub-items and the narrative-whiplash guardrail fact base. Not for the first-time consistency check before a surface ships — use narrative-cascade-planner; not for computing the TALE profile result or running the vetoes — use narrative-quality-auditor; not for echo-rate / AI-answer resonance measurement — use narrative-resonance-monitor. 自漂移监测/竞品重定位告警/重定位触发/叙事漂移复盘
Source
- Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
- Path: narrative/evaluate/narrative-drift-monitor
Evaluation
AI-evaluated 2026-09-03: Well-defined drift-detection workflow with wayback change history, explicit repositioning triggers, and a whiplash guardrail, plus read-only canon access; the concept of monitoring narrative drift against a registry canon is an uncommon, suite-internal need, hurting practical usability.