content-health

What problem does it solve?

Self-healing content monitoring system that tracks freshness of all enablement assets, detects when content is stale, and triggers updates automatically. Use this skill whenever checking if enablement content is current, when a product change happens and assets need updating, when competitive landscape shifts, or when win rates drop (which may signal stale playbooks). Also trigger proactively when any enablement asset is older than 30 days, when a competitor makes news, when pricing changes, or when the user says "is our content up to date", "what needs refreshing", "we just launched a new feature", or "competitor just announced X". This is the self-healing engine that Matthew describes — content that knows when it's decaying.

Core Features & Use Cases

• Monitors freshness of enablement assets across memory/content-registry.md and related dependencies
• Auto-refreshes or flags content for human review when decay is detected
• Triggers responses to product changes, competitor news, pricing shifts, and user prompts to refresh content
• Generates health reports and propagates changes through dependencies to keep the knowledge base current

Quick Start

Run a full content-health check to identify stale assets and automatically refresh or flag them for review.