← Cursor Slash Commands · MARKETING
/outreach
First-100 Outbound Notes
15 named people, first DM, day-3 follow-up.
/outreach 15 founders who posted that Cursor rules are a messWhere it installs
# .cursor/commands/outreach.md
# no frontmatter, the file opens with its H1 title# .claude/commands/outreach.md
---
description: ...
argument-hint: [segment, channel, and CTA]
allowed-tools: Read, Grep, Glob, Skill, TodoWrite, Write, ...
---What it does
/outreach is a Cursor slash command. Type it in chat to run a saved workflow: First-100 Outbound Notes.
Builds a short list and writes personal notes. No purchased lists, no fake personalization.
15 named people, first DM, day-3 follow-up. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /outreach for you.
Why it exists
Founders retype the same multi-step prompt until it rots. /outreach exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.
It ships in the Marketing Kit. It is wired to the Outbound Sales Closer (sales-closer) and Brand Identity & Tone Lead (brand-voice) agents. Required skills: Founder Outbound for First 100; The Mom Test Customer Validation Framework; Brand Voice Guidelines & Jargon Elimination.
When to use it
- Use to get the first customers from people already talking about the problem.
- Use /outreach when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
- Start a new chat. Do not run this command in a thread that just touched production SQL.
When not to use it
- Do not run /outreach as a substitute for reading the diff. The command produces files; you still gate them.
- Do not chain it into a 40-turn chat. Fresh context is part of the design.
- Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.
Example workflow
- sales-closer filters ICP from user-supplied posts or names
- Draft first notes + one follow-up
- Compliance and do-not-say check
- Auto-save docs/marketing/outreach.md
Example usage
Type this in Cursor chat: /outreach 15 founders who posted that Cursor rules are a mess
The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.
If a phase fails its gate, stop. Do not add 'just continue'.
Example output
- Expected artifact: docs/marketing/outreach.md
Best practices
- Keep the prompt specific. /outreach 15 founders who posted that Cursor rules are a mess is the shape: object, constraint, and outcome.
- Let the listed agents work in order: sales-closer → brand-voice.
- Save outputs in the repo. Chat-only answers evaporate.
- Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.
Common mistakes
- Typing /outreach with no object ('do the thing'). The pipeline will guess.
- Re-running the command in the same chat after a failed gate instead of fixing the failing file.
- Editing the command file to skip review so it 'goes faster'.
- Skipping the Founder Outbound for First 100 skill that the command depends on.
Frequently asked questions
What does /outreach do in Cursor?
Builds a short list and writes personal notes. No purchased lists, no fake personalization.When should I run /outreach?
Use to get the first customers from people already talking about the problem.What is an example /outreach prompt?
/outreach 15 founders who posted that Cursor rules are a messWhich skills does /outreach load?
Founder Outbound for First 100; The Mom Test Customer Validation Framework; Brand Voice Guidelines & Jargon EliminationIs /outreach a Cursor skill?
No. /outreach is a slash command you type. Skills are playbooks the agent may load. Use both: the command runs the workflow, the skills constrain how it writes.
Run /outreach from your own repo
AgenticKit installs 47 slash commands, 46 agents, and 61 skills. One command installation.