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/human-approval-gates.md
View on GitHub# Human Approval Gates
SDR packages can prepare actions. They do not execute live actions without approval.
## Risk Tiers
| Tier | Examples | Approval |
|---|---|---|
| `read_only` | Read local files, inspect trusted exports, score accounts, draft copy. | No approval unless data is sensitive. |
| `paid_read` | Run a connector that spends credits or billable API calls. | Sales owner or operator approval. |
| `data_export` | Export, enrich, or move contact/account data between systems. | Sales owner and compliance owner approval. |
| `crm_mutation` | Create or update CRM records, tasks, notes, owners, stages, or associations. | CRM owner approval. |
| `message_mutation` | Add leads to sequencer, send email, send DM, SMS, call, or calendar invite. | Sales owner and compliance owner approval. |
| `regulated` | Healthcare, finance, legal, employment, housing, credit, minors, political, or sensitive data. | Human review required before production. |
## Required Approval Record
Every approval request must include:
```text
approval_id,action_type,risk_tier,system,account_or_list_scope,row_count,fields_touched,cost_or_credit_cap,dry_run_path,evidence_ids,suppression_list_id,rollback_plan,requested_by,approver,decision,decision_at
```
## Approval Checklists
### Connector Run
- Source and vendor terms are reviewed.
- Fields requested are minimal.
- Cost or credit cap is set.
- Rate and volume limits are set.
- Output destination is declared.
- Sensitive-data risk is checked.
- Dry-run preview exists.
### CRM Mutation
- Duplicate policy is declared.
- External ID or merge key is present.
- Owner assignment is clear.
- Stage mapping is clear.
- Triggered workflows are known.
- Rollback or cleanup plan exists.
### Sequencer Import
- Sender identity is complete.
- SPF/DKIM/DMARC and sender-risk review are done.
- Suppression list is synced.
- Opt-out language is present.
- Claim evidence is attached.
- Campaign is paused or queued, not auto-activated.
### Message Send
- Sequence passed `cold-email.yaml`.
- Recipient rows passed source, suppression, relevance, and claim gates.
- Send volume is within approved limits.
- No deceptive subject lines.
- No sensitive personal attributes.
- Opt-out processing path exists.
### Phone Or SMS
- TCPA and regional consent risk are reviewed.
- Number source and business relationship are clear.
- Script has opt-out or no-call handling when required.
- Call recording consent rules are reviewed if recording is used.
- Routing and logging path are approved.
## Stop Conditions
Stop and request human decision when:
- Source rights are unclear.
- Suppression source is missing.
- A connector would spend credits.
- A live system would change.
- A contact asks to opt out.
- A reply indicates complaint, legal concern, harassment concern, or sensitive topic.
- A regulated category is detected.
- A user asks to bypass terms, access controls, or policy.
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 |