sales-context

Create a centralized .agents/sales-context.md file through a structured five-round process.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Jlsiles/Craig---Skills --skill sales-context-jlsiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sales-context
Source: https://github.com/Jlsiles/Craig---Skills/tree/main/sales/sales-context
Command: npx skills add https://github.com/Jlsiles/Craig---Skills --skill sales-context-jlsiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The foundational skill creates and maintains the .agents/sales-context.md file — the single source of truth read by all other sales skills to ensure consistent context and behavior across prompts.

Core Features & Use Cases

  • Establish and update a centralized .agents/sales-context.md in the project root as the canonical context for ICP, value proposition, sales motion, proof points, and anti-ICP.
  • Guide users through a structured, round-based flow (Round 1 through Round 5) to collect critical inputs and translate them into a machine-readable playbook consumed by downstream skills.
  • Provide red-flag diagnostics and cross-skill references to surface gaps and align tactics across the sales stack.

Quick Start

Walk through the 5 rounds to build your context and save the finished file to .agents/sales-context.md.

Frequently Asked Questions about sales-context

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

FAQPage Schema
How do I build a centralized sales context playbook for my ICP and value proposition?

A sales context playbook establishes a single source of truth for your ICP, value proposition, and anti-ICP. It ensures all your sales prompts and workflows maintain consistent context, behavior, and aligned tactics across your sales stack.

What is an anti-ICP and how do I define it for my sales workflow?

An anti-ICP defines the prospects you should avoid targeting. You define it using a structured, questions-driven process that identifies red flags and records them in your sales-context.md playbook to guide and align your sales workflows.

How do I create a single source of truth for my sales motion and proof points?

You create a single source of truth for your sales motion and proof points by completing a five-round collection flow. This process translates your critical inputs into a machine-readable playbook saved as .agents/sales-context.md.

How do I diagnose red flags and gaps in my ICP definition process?

You diagnose red flags and gaps in your ICP definition process by applying the built-in red-flag diagnostic system. This system surfaces misalignments during the structured collection flow and provides cross-skill references to adjust your tactics.

Do I need any specific dependencies or environment setup to maintain centralized sales context?

No dependencies are required to maintain centralized sales context. You only need to complete the guided collection rounds and save the resulting playbook to the .agents/sales-context.md file in your project root.