Autopilot Templates

Autopilot templates are pre-built, runnable AI workers. Each one decomposes a task into roles, runs every step through the gateway governance chain, and produces a shareable HTML report. You don’t wire up agents yourself — you pick a template, give it a task, and get a report back.

There are 22 templates today. They’re registered at startup from SKILL.md contracts (see Authoring a template) and are available from the dashboard command center, the API, and Slack/Teams triggers.

See the output first: View a live sample report ↗ 

The catalog

Engineering

Security & compliance

Finance, data & operations

Sales, marketing & growth

Research & web automation

Running a template

Every template shares the same lifecycle: list → estimate → run → poll → report.

# 1. List available templates
curl https://api.curate-me.ai/api/v1/autopilot/templates \
  -H "Authorization: Bearer $CM_API_KEY"
 
# 2. (optional) Estimate cost before committing
curl -X POST https://api.curate-me.ai/api/v1/autopilot/estimate/news_digest \
  -H "Authorization: Bearer $CM_API_KEY" -H "Content-Type: application/json" \
  -d '{"topics": ["ai agents", "llm governance"]}'
 
# 3. Trigger a run — returns a task_id
curl -X POST https://api.curate-me.ai/api/v1/autopilot/run/news_digest \
  -H "Authorization: Bearer $CM_API_KEY" -H "Content-Type: application/json" \
  -d '{"topics": ["ai agents", "llm governance"]}'
 
# 4. Poll status (or stream events at /tasks/{task_id}/events via SSE)
curl https://api.curate-me.ai/api/v1/autopilot/tasks/$TASK_ID \
  -H "Authorization: Bearer $CM_API_KEY"
 
# 5. Read the report — report_id is always report_{task_id}
curl https://api.curate-me.ai/api/v1/autopilot/reports/report_$TASK_ID

Other lifecycle endpoints: GET /templates/{id}/readiness (check required integrations before running), POST /tasks/{id}/pause · /resume · /cancel, and POST /tasks/{id}/approve-plan · /reject-plan for human-in-the-loop gates.

From the dashboard, the same templates run from the Autopilot command center; from Slack/Teams, via slash command or bot mention (see Slack Integration).

Authoring a template

Templates are defined by a SKILL.md contract — frontmatter declaring name, description, input/output schema, required integrations and permissions, cost budget, and a sample. To add one:

1. Create services/backend/src/services/autopilot/templates/skills/<your_skill>/SKILL.md with the contract frontmatter.
2. Add services/backend/src/services/autopilot/templates/<your_skill>.py implementing the entrypoint and calling register_template().
3. Import it from services/backend/src/services/autopilot/__init__.py so it lands in the registry at startup.
4. Add an execution test under tests/services/autopilot/.

The full contract spec — every required and optional field, registry validation, and failure modes — lives in the Autopilot Template Contract .

Next steps

• Reports — the anatomy of the HTML report every template emits, and how to embed or share it
• Teammates & Roles — templates vs. SDK-managed agents, and how roles map to workers
• Gateway Governance Chain — the policy chain every template step routes through