# Shared Source Skills Directory

> Registry of reusable data connectors. Check here FIRST before building any new
> integration — never duplicate what already exists. When an API changes, update
> one connector and every agent that references it benefits.
> Part of the Dr Lead Flow AI Operations Playbook.

## How to use this directory

1. Before Gate 1, search this table for the systems your agent needs.
2. If a connector exists, reference it in your SKILL.md under "Related Shared
   Source Skills" — do not rebuild it.
3. If it doesn't exist, propose the new connector in your Gate 1 plan and add it
   here when approved.

## Blocking classification

Every connector is classified by what happens to dependent agents when it breaks:

- **HARD-BLOCKING** — dependent agents cannot run at all. Step 0 failure. Agents
  stop and wait for approval.
- **SOFT-BLOCKING** — dependent agents can run with degraded output. The run must
  say what's missing.
- **NON-BLOCKING** — enrichment only. Runs proceed normally, note the gap.

## Connector Registry

| Connector | System | What it provides | Auth method | Blocking class | Used by (agents) | Owner | Last verified |
|---|---|---|---|---|---|---|---|
| `shared/crm` | [CRM] | Contacts, pipelines, appointments | | HARD | | | |
| `shared/call-transcripts` | [Call platform] | Call recordings + transcripts | | SOFT | | | |
| `shared/ad-platform` | [Ads] | Spend, campaigns, performance | | SOFT | | | |
| | | | | | | | |

## Adding a connector

Each new entry requires:

- [ ] Gate 1 approval naming the connector
- [ ] Access check procedure documented (used by every agent's Step 0)
- [ ] Blocking classification assigned
- [ ] Known Errors section started
- [ ] Owner assigned

## Change protocol

When a connector's API changes: update the connector once, run each dependent
agent's Step 0 checks, then note the change in this table's "Last verified" column.