cgallic/kai-cmo-harness / harness/skills/kai-sdr-operator
kai-sdr-operator
VerifiedBuild a plug-in-ready SDR operator package for sales development and outbound pipeline work: ICP definition, compliant lead-source plan, enrichment/research workflow, account scoring, outbound assets, CRM handoff, reply triage, meeting prep, approval gates, and loop memory. Use when "SDR", "sales development", "outbound SDR", "operator room", "lead gen pipeline", "prospecting pipeline", "ICP targeting", "Apify", "RapidAPI", "Clay", "Apollo", "agentic SDR workflow", "sales operating loop", "sales dashboard handoff", or any request to package outbound sales workflows that can later connect to data tools, CRMs, or operator surfaces.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.0 KB |
| references/compliance-matrix.md | markdown | 3.4 KB |
| references/connector-action-contracts.md | markdown | 2.8 KB |
| references/connector-recipes.md | markdown | 7.8 KB |
| references/evaluation-harness.md | markdown | 3.4 KB |
| references/external-loop-research.md | markdown | 4.7 KB |
| references/human-approval-gates.md | markdown | 2.9 KB |
| references/loop-events-and-transitions.md | markdown | 3.2 KB |
| references/observability-and-run-ledger.md | markdown | 2.0 KB |
| references/operating-loop.md | markdown | 4.3 KB |
| references/sdr-data-model.md | markdown | 5.3 KB |
| references/vertical-packs.md | markdown | 4.7 KB |
references/loop-events-and-transitions.md
View on GitHub# Loop Events And Transitions
Use this state table so accounts, contacts, replies, meetings, and CRM handoffs move through the SDR loop predictably.
## Account Transitions
| From | Event | To | Required Evidence |
|---|---|---|---|
| `sourced` | `source_checked` | `source_approved` | `source_id`, terms note |
| `source_approved` | `suppression_checked` | `ready_for_enrichment` | suppression source |
| `ready_for_enrichment` | `enrichment_complete` | `enriched` | field provenance |
| `enriched` | `score_complete` | `scored` | scoring model |
| `scored` | `human_approved` | `approved_for_contact_mapping` | approval record |
| `approved_for_contact_mapping` | `contact_mapped` | `approved_for_copy` | contact role evidence |
| `approved_for_copy` | `copy_ready` | `queued` | cold email gate |
| `queued` | `test_cohort_sent_or_handoff` | `sent` | approval record |
| `sent` | `reply_received` | `replied` | reply record |
| `replied` | `meeting_booked` | `meeting_booked` | meeting record |
| `meeting_booked` | `meeting_completed` | `meeting_completed` | notes or transcript |
| `meeting_completed` | `sales_accepted` | `opportunity_created` | AE or owner acceptance |
| any | `blocked` | `blocked` | blocker reason |
| any | `suppressed` | `suppressed` | suppression event |
| any | `disqualified` | `disqualified` | disqualification reason |
## Reply Transitions
| Reply Category | Event | Next State | Action |
|---|---|---|---|
| `interested` | `meeting_requested` | `meeting_prep_needed` | Trigger `/kai-sales-meeting-prep`. |
| `objection` | `response_allowed` | `response_draft_needed` | Draft one response with evidence. |
| `referral` | `permission_captured` | `new_contact_review` | Create referred contact candidate. |
| `not_now` | `reminder_allowed` | `nurture_task_proposed` | Propose reminder task. |
| `wrong_person` | `routing_allowed` | `routing_request_draft` | Ask for owner only if appropriate. |
| `opt_out` | `suppression_required` | `suppressed` | Add global suppression. |
| `bounce` | `invalid_contact` | `blocked` | Block the address. |
| `complaint` | `human_review_required` | `held_for_review` | Stop sequence and route owner. |
## Meeting Transitions
| From | Event | To | Required Evidence |
|---|---|---|---|
| `meeting_prep_needed` | `prep_complete` | `ready_for_meeting` | meeting brief |
| `ready_for_meeting` | `completed` | `follow_up_needed` | notes or transcript |
| `ready_for_meeting` | `no_show` | `no_show_follow_up_review` | calendar or owner note |
| `follow_up_needed` | `follow_up_drafted` | `crm_handoff_needed` | draft follow-up |
| `crm_handoff_needed` | `sales_accepted` | `opportunity_created` | owner approval |
## Event Record
```yaml
event_id: evt_...
entity_type: account
entity_id: acct_...
from_state: sourced
event: source_checked
to_state: source_approved
actor: kai-sdr-operator
evidence_ids: []
approval_id: null
created_at: 2026-05-27T00:00:00Z
```
## Stale State Rules
- Evidence older than its `expires_at` cannot support new outreach.
- `queued` rows older than 14 days require review before send.
- `not_now` reminders must include a user-approved date or business trigger.
- No-show follow-up requires meeting owner approval.
- Suppression events never expire unless a compliance owner removes them.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |