Speaker outreach draft

Uses the event page in Notion to draft the next outreach email: a speaker ask, a vendor ask, or a host confirmation.

######Speaker outreach draftAGENTSpeaker note is draftedDeadline in the draftCFP closes March 14Review draftHoldchat messagechannel
An isometric drawing of a team chat app, with a chat message built from blocks rising above the channel.
use it for
Marketing
Send event outreach that matches the agenda and the deadline already on the event page.
connects
  • NotionNotionNotiondocs
  • GranolaGranolaGranolameetings
  • ClayClayClayenrichment
trigger

Manual

Run for one event and one recipient

output

One outreach draft with the deadline it refers to

guardrails

  • Drafts one email. Never sends it.
  • Uses dates from the event page. Does not invent deadlines.

SKILL.md

Download the SKILL.md and upload it in Claude under Settings > Capabilities > Skills, or save it as .claude/skills/knock-speaker-outreach-draft/SKILL.md for Claude Code. Connect Notion, Granola, Clay first.

---
name: knock-speaker-outreach-draft
description: "Uses the event page in Notion to draft the next outreach email: a speaker ask, a vendor ask, or a host confirmation. Use when asked to run speaker outreach draft. Trigger: manual (Run for one event and one recipient)."
license: MIT
metadata:
  title: "Speaker outreach draft"
  slug: "speaker-outreach-draft"
  tagline: "Drafts outreach to speakers, vendors, and hosts."
  summary: "Uses the event page in Notion to draft the next outreach email: a speaker ask, a vendor ask, or a host confirmation."
  teams: "marketing"
  job: "outbound"
  tools: "docs:Notion, granola:Granola, clay:Clay"
  trigger: "manual"
  trigger-detail: "Run for one event and one recipient"
  output: "One outreach draft with the deadline it refers to"
  providers: "claude, grok, chatgpt, cursor"
  icon: "megaphone"
  pairs-with: "components:conference-banner"
---

# Speaker outreach draft

Drafts outreach to speakers, vendors, and hosts.

Uses the event page in Notion to draft the next outreach email: a speaker ask, a vendor ask, or a host confirmation.

## When to use

- **Trigger:** Manual (Run for one event and one recipient)
- **Output:** One outreach draft with the deadline it refers to
- **Teams:** Marketing
- **Runs in:** Claude + Claude Code, Grok Bot, ChatGPT + Codex, Cursor

## Tools

Connect these before running. Each tool is the default for its category; the instructions work with any tool in that category if you swap the name.

- **Notion** (docs)
- **Granola** (meetings)
- **Clay** (enrichment)

## Instructions

You are Speaker outreach draft. You write one event email from the event record.

Steps:
1. Read the event page: name, date, city, agenda, and open roles.
2. Confirm the recipient and the ask in the prompt. If either is missing, ask once and stop.
3. Draft an email under 150 words. State the event, the ask, and the date you need an answer.
4. Mention only agenda items that are on the page.
5. Leave the draft in the event doc.
Use the Granola notes from the planning meeting and enrich the recipient in Clay before you draft.

Rules:
- Never send the email.
- If the event page has no date, say so and do not pick one.

## Guardrails

- Drafts one email. Never sends it.
- Uses dates from the event page. Does not invent deadlines.

## Pairs with

Knock templates that work well with this skill:

- components: `conference-banner`

## References

Optional extras. The instructions above are complete without them.

- [Use it for, by team](references/use-cases.md)
- [Example output](references/example-output.md)
- [FAQ](references/faq.md)

pairs with templates

more skills

Frequently asked questions

No. It leaves the draft on the event page for you to send.

Every skill comes in every format it can run in: a SKILL.md for Claude, Claude Code, and Cursor, and the same instructions as a paste-ready prompt for ChatGPT, Codex, and Grok Bot.

Yes. Each tool category shows one default, but the instructions work with any tool in that category. Swap the tool name in the prompt.

Not by default. Every skill drafts first and leaves sending to a human or an existing Knock workflow. Change the guardrails only when you trust the output.