revenue-enablement-context

Create a canonical GTM context with ICPs, personas, stages, pricing, and initiatives.

11|1|Updated Mar 17, 2026

Search Tags:#personas #governance #enablement #icp #sales-stages #gtm-context

Ready to run

npx skills add https://github.com/nthnclrk/enablement-skills --skill revenue-enablement-context

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: revenue-enablement-context
Source: https://github.com/nthnclrk/enablement-skills/tree/main/skills/revenue-enablement-context
Command: npx skills add https://github.com/nthnclrk/enablement-skills --skill revenue-enablement-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Canonicalize and maintain a single source of truth for go-to-market context so that multiple enablement skills share consistent ICP definitions, personas, sales stages, pricing, objections, and initiatives, reducing misalignment and rework.

Core Features & Use Cases

Canonical context artifact that captures ICPs, personas, stages, pricing, objections, and initiatives for reuse by downstream enablement skills.
Governance and freshness tracking with owner, last-updated date, and open assumptions to ensure the context stays current.
Multi-skill orchestration: routes sequencing requests across skills and provides a machine-readable reference for automation.

Quick Start

Provide company summary, ICPs, personas, sales stages, pricing and packaging basics, and current initiatives to generate or update the canonical enablement context.

Frequently Asked Questions about revenue-enablement-context

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

FAQPage Schema

How do I maintain a single source of truth for GTM context across multiple enablement skills?▼

Maintain a single source of truth for GTM context by building a canonical artifact that captures ICPs, personas, sales stages, pricing, and initiatives for reuse by downstream enablement skills, ensuring consistent outputs and reducing team misalignment.

What is a canonical enablement context artifact and when do I need one?▼

A canonical enablement context context artifact is a structured record capturing ICP definitions, personas, sales stages, pricing, and objections. You need one when multiple enablement skills require consistent go-to-market context to prevent misalignment and rework.

How do I track governance and freshness for go-to-market context definitions?▼

Track governance and freshness for go-to-market context by recording an owner, last-updated date, and open assumptions within the canonical artifact, ensuring the context stays current and accountable across downstream teams.

How do I provide a machine-readable schema for downstream enablement skill consumption?▼

Provide a machine-readable schema for downstream consumption by structuring your company summary, ICPs, personas, sales stages, and pricing into the canonical context artifact, which enables multi-skill orchestration and automation routing.

Can I use this to route sequencing requests across multiple enablement skills?▼

Yes, you can route sequencing requests across multiple enablement skills by using the canonical GTM context artifact as a machine-readable reference, which coordinates automation and ensures skills share consistent ICP and persona data.

What inputs do I need to generate a canonical GTM context for my sales team?▼

To generate a canonical GTM context for your sales team, provide a company summary, ICPs, personas, sales stages, pricing and packaging basics, and current initiatives to populate the structured enablement artifact.