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/observability-and-run-ledger.md
View on GitHub# Observability And Run Ledger
The SDR loop needs run history before it needs a dashboard. Use this ledger to trace actions, approvals, connector calls, sends, replies, meetings, and memory promotion.
## Required Ledgers
| Ledger | File | Purpose |
|---|---|---|
| Run ledger | `run-ledger.jsonl` | One row per SDR loop run. |
| Action ledger | `action-ledger.jsonl` | One row per proposed or executed action. |
| Connector ledger | `connector-ledger.jsonl` | One row per connector call or dry run. |
| Approval ledger | `approval-ledger.jsonl` | One row per human decision. |
| Suppression ledger | `suppression-ledger.jsonl` | One row per opt-out, bounce block, do-not-contact, or complaint. |
| Memory ledger | `memory-ledger.md` or `memory-ledger.jsonl` | Outcome learnings and promotion status. |
## Run Record
```json
{
"run_id": "run_001",
"workflow": "kai-sdr-operator",
"package_id": "pkg_acme",
"mode": "b2b_sdr_engine",
"started_at": "2026-05-27T00:00:00Z",
"ended_at": null,
"actor": "codex",
"inputs": [],
"outputs": [],
"status": "running",
"blocked_reason": null
}
```
## Action Record
```json
{
"action_id": "act_001",
"run_id": "run_001",
"action_type": "dry_run",
"system": "hubspot",
"entity_count": 12,
"dry_run_path": "workspace/sdr-operator/acme/dry-runs/act_001.json",
"approval_id": null,
"status": "dry_run_complete"
}
```
## Alert Rules
Create an alert or daily briefing note when:
- Any opt-out, complaint, or bounce appears.
- Send cap would be exceeded.
- Connector failure rate exceeds 5% in a run.
- More than 10% of rows are blocked for source or suppression gaps.
- A meeting is booked without meeting prep.
- A follow-up is due within 24 hours.
- Evidence expires before the planned send date.
- A CRM dry run would create duplicates.
## Run Closeout
Every run closeout should state:
- Inputs used.
- Actions proposed.
- Actions approved.
- Actions blocked.
- Sources added.
- Gaps added.
- Replies processed.
- Meetings prepared.
- Memory candidates created.
- Learnings promoted or held.
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 |