Systems Lab

Agent skill

pipeline-stages

Move deals through an 8-stage pipeline using deterministic stage-gate rules and MEDDPICC slot completion criteria.

slowingNeeds a keyActs undeclared499 words

Filed under CRM and RevOps.

From devangk003/gtm-agent-skills · 32 skills · 0 · pushed 2026-06-18

What it does when it runs

Move deals through an 8-stage pipeline using deterministic stage-gate rules and MEDDPICC slot completion criteria. Use when the user says "advance this deal", "audit pipeline stages", "which deals are stuck", or "move to next stage.

Read from the skill and the 4 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
  • AGENTIC_APP_TOKEN
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It does act, so it runs under whatever permissions your session already grants.
Actions present in the files
shell

Ask about pipeline-stages

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/devangk003/gtm-agent-skills.git /tmp/gtm-agent-skills
git -C /tmp/gtm-agent-skills sparse-checkout set "pipeline-stages"
mkdir -p ~/.claude/skills/pipeline-stages
cp -R "/tmp/gtm-agent-skills/pipeline-stages/." ~/.claude/skills/pipeline-stages/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Before you install: this skill will not complete its job on a bare agent. It needs AGENTIC_APP_TOKEN, which you have to obtain separately.

The skill

Source on GitHub ↗

Reproduced in full from devangk003/gtm-agent-skills/blob/6b9a1b0094ffd83d6c02bc03b7ce1610661a1644/pipeline-stages/SKILL.md, which is licensed MIT (skill frontmatter). 499 words, 6 headings.

Pipeline Stages

Move deals through 8 canonical pipeline stages with deterministic gates: New → Contacted → Engaged → Meeting → Discovery → Proposal → Closed-Won / Closed-Lost. Hard rule: deals cannot advance until gates are met; stuck deals get flagged with the specific missing element.

When to Use

  • Reply classified positive — advance deal
  • Audit pipeline — which deals are in wrong stage
  • Deal signed — move to Closed-Won
  • Bulk classify active deals into correct stages
  • Stuck deal investigation — why hasn't this advanced
  • User says "advance this deal" or "audit pipeline stages"

Quick Reference

StageEntry gateAvg duration
NewLead created<7d
Contacted≥1 Touch sent14–21d
EngagedReply received (not unsubscribe/not-interested)7–14d
MeetingDiscovery call scheduled<14d
DiscoveryMeeting held; ≥5/8 MEDDPICC slots14–30d
ProposalProposal sent; deal value confirmed14–60d
Closed-WonContract signedn/a
Closed-LostExplicit no OR 90d silence post-Proposaln/a
ConceptValue
Stage-skip prohibitionCannot skip stages; only exception is jump to Closed-Lost
Stuck-deal detectionTime-in-stage >2× avg → flag with missing element
Discovery→Proposal gateAll 8 MEDDPICC slots populated (inferred acceptable)
Closed-Lost reasonsno-budget / no-authority / no-need / no-timing / lost-to-competitor / unresponsive

Procedure

  1. Validate inputs. Read deal record + trigger event + stage definitions. Confirm trigger maps to a transition or audit request.
  2. Check stuck status. Pull current stage; compute time-in-stage; flag if >2× avg.
  3. Match trigger to candidate transition. reply-positive → advance; meeting-booked → advance; proposal-sent → advance; contract-signed → Closed-Won; not-interested/90d silence → Closed-Lost. See ${HERMES_SKILL_DIR}/references/stage-gates.md.
  4. Apply stage gates. Check entry criteria for target stage. If gates met → advance. If NOT met → block; surface missing element; flag for crm-hygiene or discovery-call-prep.
  5. Handle edge cases. Reverse transitions allowed but logged. Stage-skip prohibited unless Closed-Lost.
  6. Bulk mode (when applicable). Iterate every active deal, replay gate logic, surface wrong-stage deals. Don't auto-correct without authorization. See ${HERMES_SKILL_DIR}/references/bulk-audit.md.
  7. Update deal + push. PATCH deal with new stage + timestamp. Push interaction:stage-change with trigger + duration. See ${HERMES_SKILL_DIR}/scripts/push_to_crm.py.

Pitfalls

  • Vague stage definitions — each needs an explicit entry event, not "feels engaged"
  • Auto-advancing without gate checks — positive reply ≠ Meeting stage without booked meeting
  • Stage-skipping — Discovery → Closed-Won without Proposal is data corruption
  • Letting stuck deals linger — surface AND name the missing element
  • Closed-Lost without a reason — lost-reason feeds icp-refinement-loop
  • Bulk auto-correct — always require user authorization before mass stage updates

Verification

  1. Every transition has documented trigger + gate-check result
  2. Stuck-deal flags name specific missing elements
  3. No stage-skips except to Closed-Lost
  4. Deal record PATCHed; interaction:stage-change pushed

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what pipeline-stages does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.