# SKILL.md — [Agent Name]

> The technical counterpart to the Notion SOP. This is what the AI reads at runtime —
> not what the team sees. Keep it synced with the SOP; if they conflict, the SOP wins
> and this file is updated to match.
> Part of the Dr Lead Flow AI Operations Playbook.

## Owner & Approval Matrix

| Role | Person | Approves |
|---|---|---|
| Business owner | | SOP changes, output format |
| Technical owner | | Skill/cron changes, integrations |
| Gate approver | | Gate 1 (plan), Gate 3→4 (go live) |

## Step 0 — Source Access Checks

Before doing any work, verify every data source is reachable. If any check fails,
STOP, post the blocker to the agent's channel, and wait for approval. Never assume
"blocker resolved" means "continue running."

- [ ] Source 1: [system + how to verify access]
- [ ] Source 2:

## Known Errors

Errors seen before and how to handle them. Append new ones — never delete.

| Error | Cause | Handling |
|---|---|---|
| | | |

## Execution Steps

Numbered, explicit, no ambiguity:

1.
2.
3.

## Output Requirements

- Destination: [Slack channel from SOP]
- Format: [structure, headings, length limits]
- Deduplication: [lookback window, how repeats are avoided]

## QA Gate (hard pass/fail)

Every run must pass ALL checks to count as successful. Partial or learning-only runs
are not clean successes unless explicitly approved.

- [ ] Output posted to the correct channel
- [ ] All required sections present
- [ ] Data freshness within [X hours]
- [ ] No duplicate of a prior run's output
- [ ] [Domain-specific accuracy check]

## Error Handling

- Source down at Step 0 → stop, post blocker, wait for approval
- Partial data mid-run → [stop or degrade, specify]
- Third consecutive failed run → pause cron, escalate to technical owner

## Change Control

The AI may propose changes but cannot implement changes to this skill, the cron,
schedules, or outputs without explicit approval. Log every approved change below.

## Change Log

| Date | Change | Approved by |
|---|---|---|
| | | |

## Run Log

| Date | Result (pass/fail) | Notes |
|---|---|---|
| | | |

## Related Shared Source Skills

Check the Shared Source Skills Directory before adding any new connector.

- `shared/[connector-name]` — [what it provides]

## Automation Economics

| Item | Value |
|---|---|
| Model | [Opus for complex work / Sonnet for routine] |
| Est. cost per run | $ |
| Runs per month | |
| Est. monthly cost | $ |
| Human time replaced | hrs/month |