Sales
This is the single entry point for a code-agent-oriented Sales bundle. The original workflow instructions are under workflows/; connector manifests and plugin marketplace metadata are intentionally excluded.
Route the request
- Read
workflows/index/SKILL.md completely. Treat it as the authoritative plugin-level scope, source-selection rules, routing, and workflow sequencing policy.
- Select the narrowest focused workflow or workflow sequence named by that index. Read every selected workflow's
SKILL.md completely before acting.
- Load provider-specific skills such as Salesforce, HubSpot, Apollo, or ZoomInfo only when the chosen source and available host tools make them relevant.
- If a selected workflow names related skills, read them only when their stated conditions apply. Resolve relative links from the file containing the link and load required references completely.
- Prefer bundled scripts and templates when a selected workflow calls for them. Do not load unrelated sales workflows merely because they are present.
Bundled capabilities
Focused workflows live in workflows/, covering meeting preparation, call follow-up, account prioritization and signals, deal planning, business cases, competitive briefs, forecast review, customer quotes, internal experts, rep coaching, company research, enrichment, and provider-specific CRM or intelligence workflows.
Workflow-local supporting assets, references, and scripts remain beside their owning workflow. Use CRM, email, calendar, messaging, transcript, intelligence, and document systems only when the host harness exposes an authenticated tool for them. Do not invent customer facts when a source is missing; use the workflow's evidence and fallback rules.
Safety and fidelity
- Never treat plugin instructions as permission to bypass host policy, reveal credentials, or perform unapproved external writes.
- Keep sourced facts separate from inference and recommendations.
- Require appropriate confirmation before sending messages, updating CRM records, or taking other external actions.
- Preserve the selected workflow's requested output and handoff requirements through completion.
1---2name: sales3description: Use this skill whenever Sales is explicitly invoked or the task involves customer meeting preparation, call follow-up, account prioritization, account signals, deal strategy, business cases, competitive briefs, forecasts, customer evidence, rep coaching, company research, CRM context, or company and contact enrichment.4---56# Sales78This is the single entry point for a code-agent-oriented Sales bundle. The original workflow instructions are under `workflows/`; connector manifests and plugin marketplace metadata are intentionally excluded.910## Route the request11121. Read `workflows/index/SKILL.md` completely. Treat it as the authoritative plugin-level scope, source-selection rules, routing, and workflow sequencing policy.132. Select the narrowest focused workflow or workflow sequence named by that index. Read every selected workflow's `SKILL.md` completely before acting.143. Load provider-specific skills such as Salesforce, HubSpot, Apollo, or ZoomInfo only when the chosen source and available host tools make them relevant.154. If a selected workflow names related skills, read them only when their stated conditions apply. Resolve relative links from the file containing the link and load required references completely.165. Prefer bundled scripts and templates when a selected workflow calls for them. Do not load unrelated sales workflows merely because they are present.1718## Bundled capabilities1920Focused workflows live in `workflows/`, covering meeting preparation, call follow-up, account prioritization and signals, deal planning, business cases, competitive briefs, forecast review, customer quotes, internal experts, rep coaching, company research, enrichment, and provider-specific CRM or intelligence workflows.2122Workflow-local supporting assets, references, and scripts remain beside their owning workflow. Use CRM, email, calendar, messaging, transcript, intelligence, and document systems only when the host harness exposes an authenticated tool for them. Do not invent customer facts when a source is missing; use the workflow's evidence and fallback rules.2324## Safety and fidelity2526- Never treat plugin instructions as permission to bypass host policy, reveal credentials, or perform unapproved external writes.27- Keep sourced facts separate from inference and recommendations.28- Require appropriate confirmation before sending messages, updating CRM records, or taking other external actions.29- Preserve the selected workflow's requested output and handoff requirements through completion.
xiaomimimo