Systems Lab

Agent skill

handoff-protocol

Hand off SAL-eligible leads from SDR to AE with a complete briefing package and SiriusDecisions SAL acceptance tracking.

slowingNeeds a keyActs undeclared446 words

Filed under Analytics and reporting.

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

What it does when it runs

Hand off SAL-eligible leads from SDR to AE with a complete briefing package and SiriusDecisions SAL acceptance tracking. Use when the user says "hand off to AE", "handoff this deal", "SAL acceptance", or "SDR to AE transfer.

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 handoff-protocol

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 "handoff-protocol"
mkdir -p ~/.claude/skills/handoff-protocol
cp -R "/tmp/gtm-agent-skills/handoff-protocol/." ~/.claude/skills/handoff-protocol/

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/handoff-protocol/SKILL.md, which is licensed MIT (skill frontmatter). 446 words, 6 headings.

Handoff Protocol

Package and deliver an SAL-eligible lead from SDR to AE with a complete briefing: 1-page briefing, MEDDPICC snapshot, conversation history, pre-staged objections, and explicit SAL acceptance criteria. Per SiriusDecisions/Forrester norms: handoffs are explicit acceptance events, not silent assignments.

When to Use

  • Positive reply + meeting booked — hand off to AE
  • Tier-1 founder-led prospect ready for founder takeover
  • Bulk handoff of campaign's positive replies
  • AE rejected the handoff — reroute/fix
  • Deal closed-won — hand off to CSM
  • User says "hand off to AE" or "SAL acceptance needed"

Quick Reference

ConceptValue
Handoff package1-page briefing + MEDDPICC + conversation history + objections + SAL checklist
SAL acceptance criteriaICP fit confirmed + trigger present + within half-life + DM/champion identified + no hard disqualifiers
Acceptance statespending → accepted / rejected (with reason) / takeback
Rejection routingBack to SDR with reason for fix-then-resubmit
Takeback ruleAllowed within 7d post-acceptance; after 7d needs manager approval
Briefing freshness≤24h at handoff (HANDOFF_FRESHNESS_HOURS=24)

Procedure

  1. Validate prerequisites. Confirm SAL-eligible per lead-scoring or pipeline stage. Load receiving rep identity + preference. See ${HERMES_SKILL_DIR}/references/sal-criteria.md.
  2. Pull/refresh briefing. Pull discovery-call-prep briefing. Check freshness ≤24h. Stale → re-prep.
  3. Assemble handoff package. 5 components: briefing, MEDDPICC snapshot, conversation history, pre-staged objections, SAL checklist. See ${HERMES_SKILL_DIR}/references/package-template.md.
  4. Run pre-delivery SAL gates. Verify all 5 SAL criteria pass (ICP fit / trigger present / within half-life / DM-or-champion identified / no hard disqualifiers). If any fail, route back to SDR — don't deliver an unacceptable handoff.
  5. Deliver via rep's channel. Slack DM / email / dashboard per preference. Include accept/reject mechanism.
  6. Track acceptance state. pending → accepted (PATCH deal owner) / rejected (route to SDR with reason) / no response within 24h (escalate).
  7. Handle takebacks. Within 7d: mark takeback, route back to SDR. After 7d: manager approval required.
  8. Push to CRM. interaction:handoff with package + state + audit trail. PATCH deal owner on acceptance. See ${HERMES_SKILL_DIR}/scripts/push_to_crm.py.

Pitfalls

  • Silent handoffs — calendar invite without briefing = AE walks in cold
  • Auto-accepting on silence — no reply ≠ accept; escalate
  • Stale briefings at handoff — >24h → re-prep
  • No rejection reason captured — require reason at rejection for learning
  • Multiple AEs assigned same deal — single owner per deal

Verification

  1. Every handoff has delivery event + acceptance event
  2. SAL pre-checks pass before delivery
  3. Rejection reasons captured; deal owner PATCHed only on accept
  4. Takeback events tracked with timestamps

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 handoff-protocol 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.