content-health

Monitor enablement assets for content decay and trigger automatic updates.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/jbalbu01/gtm-enablement-engine --skill content-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-health
Source: https://github.com/jbalbu01/gtm-enablement-engine/tree/main/skills/content-health
Command: npx skills add https://github.com/jbalbu01/gtm-enablement-engine --skill content-health

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about content-health

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

FAQPage Schema
How do I monitor enablement content for decay and trigger automatic updates?

You can monitor enablement content for decay by running a health check that detects stale assets and triggers auto-refresh or flags them for human review. This tracks freshness across your content registry and knowledge base to keep information current.

What is content decay tracking and how does it keep knowledge base assets fresh?

Content decay tracking monitors the age and relevance of enablement assets to detect when they become stale. It automatically refreshes outdated content or flags it for review, propagating changes through dependencies to maintain a current knowledge base.

How do I automatically flag stale playbooks when win rates drop or competitors make announcements?

You can automatically flag stale playbooks by triggering a content-health check when win rates drop, competitors announce news, or pricing changes. The skill detects affected enablement assets and marks them for immediate refresh or human review.

Can I check if my enablement content is up to date after launching a new product feature?

Yes, you can check if your enablement content is up to date by running a full health check after a product launch. The skill identifies assets needing updates based on recent changes and propagates those updates through all dependent knowledge base materials.

What's the best way to set up dependency tracking for enablement assets across a content registry?

The best way to set up dependency tracking is to use a self-healing monitoring system that maps relationships across your content registry. When one asset updates, the system automatically propagates changes downstream to dependent dashboards and knowledge base materials.

When should I not use automated content health monitoring for my knowledge base?

Automated content health monitoring may not suit contexts requiring manual editorial control or where assets lack structured dependencies. If your enablement content does not follow a tracked registry format, auto-refresh workflows cannot accurately detect decay or propagate updates.