Skip to content
Back to skills

Crm Pipeline Playbook

ASecurity

How to answer pipeline, renewal, and account-health questions using the CRM tools.

  • 352 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added August 30, 2026
ai-agents

Works with

  • mcp

Security analysis

A100/100

Scanned August 30, 2026

npx -y skills add schmitech/orbit --skill crm-pipeline-playbook --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Crm Pipeline Playbook?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Crm Pipeline Playbook
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/schmitech-crm-pipeline-playbook/badge)](https://www.skillsdirectory.com/skills/schmitech-crm-pipeline-playbook)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: crm-pipeline-playbook
description: How to answer pipeline, renewal, and account-health questions using the CRM tools.
mcp_tools:
  - "business-sample__list_customers"
  - "business-sample__get_customer_health"
  - "business-sample__search_opportunities"
  - "business-sample__summarize_pipeline"
  - "business-sample__build_account_plan"
enabled: true
version: "1.0"
priority: 10
---

## Finding a customer

Always resolve the customer id with `list_customers` before calling
`get_customer_health` or `build_account_plan` — both take an id, never a name.

When asked for a segment or region (e.g. "Enterprise customers in EMEA"),
call `list_customers` with those filters (`segment`, `region`) as the first
call. Never guess at customer ids by iterating `cus_0001`, `cus_0002`, ...
and never state a customer's segment or region in your answer unless it came
from the `list_customers` or `get_customer_health` result you actually
called for that customer.

## Limits

`search_opportunities` clamps `limit` values above 25 to 25. Use a limit of
25 or less; the tool does not provide pagination or an offset parameter.

## Choose the right tool

Use `summarize_pipeline` for aggregate pipeline questions. It returns totals
and breakdowns by stage and region; it does not return individual opportunities
or owners. Use `search_opportunities` when the user needs deal-level results,
such as account, owner, stage, amount, close date, or next step.

## Output

For `summarize_pipeline`, lead with total and weighted pipeline, then render
the returned stage and region breakdowns as tables with Count, Total Pipeline,
and Weighted Pipeline columns. Do not invent an owner breakdown from this
aggregate response.

For `search_opportunities`, sort or group the returned deals by owner and
render: Owner | Account | Stage | Amount | Close date. Use `customerName` as
the Account value and `amount` as the Amount value. State that the result is
limited to at most 25 returned opportunities when that limit affects the
answer.

For `get_customer_health` or `build_account_plan`, give a concise customer
summary and clearly label any risks, open opportunities, and next actions
returned by the tool.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…