narrative-drift-monitor

Detect narrative drift and competitor repositioning against a canonical reference.

2.5k|345|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill narrative-drift-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: narrative-drift-monitor
Source: https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/narrative/evaluate/narrative-drift-monitor
Command: npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill narrative-drift-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Detects when a narrative has drifted from the canonical reference, triggering repositioning alerts.

Core Features & Use Cases

  • Narrative Drift Detection: Monitors flagship surfaces for drift from the canonical narrative over time.
  • Competitor Repositioning Alerts: Detects competitor repositioning against the brand's narrative.
  • Repositioning Trigger Conditions: Defines explicit conditions that should trigger a narrative repositioning.
  • D1/W1/M1 Message-shift Retro: Compares intended vs. actual narrative pull-through for analysis.

Quick Start

Check narrative drift for 'homepage', 'competitors', 'canon path', window: D1.

Frequently Asked Questions about narrative-drift-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is narrative drift detection and how does it monitor brand messaging?

Narrative drift detection monitors flagship brand surfaces to identify deviations from a canonical reference over time, ensuring messaging remains aligned and triggering alerts when repositioning is necessary.

How do I set up competitor repositioning alerts against my brand's narrative?

You can establish competitor repositioning alerts by analyzing competitor context against your canonical narrative, which allows the system to detect shifts in competitor messaging and trigger proactive repositioning warnings.

How can I compare intended vs. actual narrative pull-through for messaging analysis?

You can compare intended versus actual pull-through by running message-shift retrospectives, evaluating D1, W1, or M1 windows to analyze how effectively your canonical narrative translated across brand surfaces.

Do I need Python libraries and specific brand surfaces to monitor narrative drift?

Yes, monitoring narrative drift requires specific Python libraries and access to both your brand surfaces and competitor context to accurately evaluate deviations from the canonical reference path.

What conditions should trigger a narrative repositioning strategy?

Repositioning triggers should be defined by explicit conditions set within the monitoring system, activated when significant narrative drift or competitor repositioning is detected against your canonical reference.