sales-context

sales-context is a skill for Claude Code from Doris-Labs/sales-skills. It costs 69 tokens per session (966 once invoked), scanned A, original, MIT.

A shared profile of what you sell, who buys it, typical deal sizes and sales cycles, the sales process, and connected tools. It gives other sales tasks the background they need.

In plain words
What is it for?
Use it when setting up sales work, describing your target customers, recording your sales process, or checking which connected tools can provide information.
Why use it?
It prevents sales tasks from repeatedly asking for the same basic information and helps them use the right available sources.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sales-skills plugin — 30 skills shipped together

Good fit Use it when setting up sales work, describing your target customers, recording your sales process, or checking which connected tools can provide information.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/doris-labs/sales-skills/sales-context
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Doris-Labs/sales-skills --skill sales-context
Clone the repo
git clone --depth 1 https://github.com/Doris-Labs/sales-skills

Made for: Claude Code.

Or install sales-skills, the plugin that ships this one along with the rest of its 30 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sales-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/doris-labs/sales-skills/sales-context/github.svg)](https://agentmods.dev/skills/doris-labs/sales-skills/sales-context)
Your own site
<a href="https://agentmods.dev/skills/doris-labs/sales-skills/sales-context"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/sales-context/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sales-context

Your own site · 80×15
<a href="https://agentmods.dev/skills/doris-labs/sales-skills/sales-context"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/sales-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 966 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00069 $0.00966
Opus 5 $0.00034 $0.00483
Sonnet 5 $0.00014 $0.00193
Haiku 4.5 $0.00007 $0.00097

Measured 11d ago against content hash b2ae29c6abaa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

sales-context scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sales-context/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sales Context

Purpose

Establish the shared context that every other sales skill depends on, so no skill has to re-ask the basics. This skill captures the AE profile (what you sell and how), the ICP, the average deal size and sales cycle, the default qualification framework, and a tool inventory of what's connected. Downstream skills read this context first and only ask for the deltas they specifically need.

By default, the qualification framework is MEDDPICC. The tool inventory records whether Doris, a CRM, a conversation-intelligence tool, or an email tool is connected so other skills know which substrate to pull from versus what to ask for.

Inputs

  • Your product — what it is, what problem it solves, who it's for.
  • Your ICP — target company profile, buyer roles, the pains you sell into.
  • Your deal motion — average contract value (ACV), sales cycle length, stage names, main competitors.
  • Optionally, a connected MCP (Doris, a CRM, conversation intelligence, or email).

Method

Run a short interview to capture and persist context. Ask for, and record:

  1. Product — one-line description and the core problem it solves.
  2. ICP — company size/segment/industry, the buyer and influencer roles.
  3. ACV — typical deal value (and range).
  4. Sales cycle — typical length from first call to close.
  5. Stage names — the actual pipeline stages you use.
  6. Main competitors — who you most often lose to or compete against.

Persist this so other skills reuse it rather than re-asking.

Default framework: MEDDPICC. Each element maps to evidence you collect across calls, emails, and the CRM:

  • Metrics — quantified business impact / ROI the buyer cares about.
  • Economic buyer — who controls the budget and can say yes.
  • Decision criteria — what they'll judge solutions against.
  • Decision process — the steps and people from eval to signature.
  • Paper process — procurement, legal, security review steps.
  • Identify pain — the explicit problem driving the purchase.
  • Champion — an internal advocate selling on your behalf.
  • Competition — who else is in the deal, including status quo.

Read the full file on GitHub · 84 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 84 lines · 69 tokens per session scan A b2ae29c6abaa

Subscribe to this mod's changes

sales-context is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 966 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.