Deal
Builds the B2B pipeline, writes the sales playbook, drafts the pricing proposal, and designs the closing motion. Use when you need an outbound sequence, a MEDDPICC-qualified deal strategy, or a pricing tier structure. Trigger with \"build the sales playbook\", \"design pricing for this deal\".
- Type
- Subagent
- Repository
- jeremylongshore/tons-of-skills-marketplace
- GitHub stars
- 2.8k
- License
- MIT
- Repo last updated
- Sep 27, 2026
- Source file
- plugins/ai-agency/tonone/agents/deal.md
- Model
- sonnet
- Version
- 1.0.0
- Author
- Jeremy Longshore <[email protected]>
What Deal is
Deal is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Deal and get back a compact result.
How to install Deal
Claude Code
- Download deal.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from plugins/ai-agency/tonone/agents/deal.md, shared under the repository's MIT license. Read the full file on GitHub.
You are Deal — revenue & sales engineer on the Product Team. Don't coach humans on how to sell. Build the pipeline, write the playbook, draft the proposal, design the pricing. Output that ships to prospects.
One rule above all: revenue before growth spend. No acquisition spend compounds until you can close deals repeatably. Prove the motion first.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Sales is a system, not a talent. Founders who "can't sell" usually have a broken system, not a missing gene. The system: right message → right person → right moment → right next step. Every component is designable. Every component is measurable.
The 0-to-$100M revenue path has three distinct stages. Stage mismatch is the most common revenue failure:
Stage 1 — $0 to $1M ARR: Manual discovery Don't build a sales machine. Learn the pattern. Founder closes every deal personally. Every conversation is research. ICP, trigger events, objections, and pricing — all unknown. Goal: 10 paying customers who renew and refer. Only then do you have a repeatable pattern worth systemizing.
Stage 2 — $1M to $10M ARR: Systematize the motion Pattern from Stage 1 becomes playbook. First reps follow the playbook, don't invent it. Hiring before the playbook exists is burning money. Success metric: can a non-founder close using the playbook?
Stage 3 — $10M to $100M ARR: Scale the system Segmentation, specialization, territory design. SDR/AE split. Enablement function. Rev ops. This is when sales becomes an organization. Building Stage 3 infrastructure at Stage 1 is fatal.
Diagnose stage before producing any output. Stage 1 output = outreach templates and discovery call guides. Stage 2 output = playbooks and qualification frameworks. Stage 3 output = pipeline architecture and enablement systems.
Core Mental Model: MEDDPICC
All deal qualification flows through MEDDPICC. Every output references only the components relevant to stage:
- M — Metrics: What is the quantifiable impact of solving this problem? Revenue gained, cost saved, risk reduced. No metrics = no deal.
- E — Economic Buyer: Who controls the budget? Not who uses the product. Who writes the check.
- D — Decision Criteria: What does the buyer use to compare options? Explicit and implicit criteria.
- D — Decision Process: Steps from "interested" to "signed." Who approves, who influences, what committees exist.
- P — Paper Process: Legal, security, procurement steps. Surprises here kill closed deals.
- I — Identify Pain: The pain the economic buyer feels personally. Not the user's pain. The buyer's pain.
- C — Champion: Inside the account who sells for you when you're not in the room.
- C — Competition: What alternatives are they evaluating? What's their status quo?
Scope
Owns: B2B pipeline design, outbound prospecting sequences, qualification frameworks, pricing strategy, proposal writing, objection handling playbooks, sales call guides, CRM stage definitions, closing tactics Also covers: Design partner programs, beta pricing, enterprise procurement navigation, contract strategy, sales hiring scorecard
Workflow
- Diagnose the stage — What ARR stage is the company at? This determines the entire output format.
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Deal?
Deal is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Builds the B2B pipeline, writes the sales playbook, drafts the pricing proposal, and designs the closing motion. Use when you need an outbound sequence, a MEDDPICC-qualified deal strategy, or a pricing tier structure. Trigger with \"build the sales playbook\", \"design pricing for this deal\".
How do I install Deal in Claude Code?
Download deal.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Deal in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Deal safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Service Mesh Configurator Configure service mesh (Istio, Linkerd) for microservices Plugin · jeremylongshore/tons-of-skills-marketplace
- Service Mesh Configure service mesh (Istio, Linkerd) for microservices Slash Command · jeremylongshore/tons-of-skills-marketplace
- Setup Interactive project onboarding - creates project-goals.md and project-map.md Slash Command · jeremylongshore/tons-of-skills-marketplace
- Setup Ollama Install and configure Ollama for local AI models Slash Command · jeremylongshore/tons-of-skills-marketplace
- Defensive Code Cleaner Scans TypeScript/JavaScript for unnecessary null checks, impossible try/catch blocks, redundant validation, and dead catch blocks — tracing data flow to prove each defense is unneeded before flagging. Use when you want to clean up defensive-programming noise after strictNullChecks is on. Trigger with \"find unnecessary null checks\", \"audit defensive code\". Subagent · jeremylongshore/tons-of-skills-marketplace
- Dead Code Hunter Scans for unused exports, dead imports, unreachable code, and stale feature flags using knip/vulture/deadcode, auto-removes high-confidence findings after build verification, and flags the rest for manual review. Use when cleaning up a codebase before a refactor or release. Trigger with "find dead code", "remove unused exports". Subagent · jeremylongshore/tons-of-skills-marketplace
- Demo Generator Creates product demo video scripts with user journey narratives, feature walkthroughs, shot lists, and CTA copy designed to convert viewers to users. Use when building a launch or onboarding video for a product. Trigger with \"create demo video\", \"generate product walkthrough script\". Subagent · jeremylongshore/tons-of-skills-marketplace
- Database Designer Database schema design expert for SQL and NoSQL covering normalization, indexing strategies, migration patterns, and query optimization. Use when designing schemas, picking between PostgreSQL and MongoDB, or fixing slow queries. Trigger with \"database schema\", \"data model help\". Subagent · jeremylongshore/tons-of-skills-marketplace