gooseworks-ai/goose-skills / skills/marketing/write-outreach
write-outreach
VerifiedCold outreach a person sends to business buyers: email and LinkedIn sequences, a first line per prospect, reply and objection answers, and a read of replies. Use when the marketer says "write a cold email sequence", "what do I send to this list", "write LinkedIn messages for these leads", "how do I reply to this prospect" or "handle this objection", "reply to this demo request", "win back or reconnect with accounts that churned or went quiet", or "why is nobody replying to my outreach". Drafts only; the marketer sends from their own tool. Not for finding the people — use research-audience; not for emails to subscribers or users, or consumer win-back — use email-lifecycle.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.7 KB |
| references/angles-by-signal.md | markdown | 7.3 KB |
| references/email-craft.md | markdown | 5.7 KB |
| references/handoff-and-compliance.md | markdown | 9.1 KB |
| references/linkedin-craft.md | markdown | 3.4 KB |
| references/outreach-by-company-type.md | markdown | 3.3 KB |
| references/reading-results.md | markdown | 5.9 KB |
| references/replies-and-objections.md | markdown | 4.8 KB |
| references/run-memory.md | markdown | 6.0 KB |
| references/sequences.md | markdown | 4.7 KB |
| skill.meta.json | config | 3.7 KB |
| tests/test-by-hand.md | markdown | 3.6 KB |
references/replies-and-objections.md
View on GitHub# Replies and objection answers
Load at step 5 and in replies mode. A reply is the point of the whole sequence: answer fast (the same working day), short, in the sender's voice, with one next step. Never argue, never pressure, never send a second pitch to someone who said stop.
## Reply categories (also the ledger's `reply_category`)
| Category | Looks like | Answer | Ledger status |
|---|---|---|---|
| `interested` | "sure, tell me more", "let's talk" | Two time options this week or a booking link, one line on what the call covers | `replied` → `meeting` when booked |
| `send-info` | "send me something" | One short resource (not a deck), plus one question about their situation | `replied` |
| `question` | "does it work with X?", "how much?" | Answer plainly (only true, signed-off facts), then one question back | `replied` |
| `timing` | "not now", "next quarter", "after our launch" | Thank them, ask permission to follow up at the date they named, offer something useful meanwhile | `replied` + `recontact_after` = the date they named (excluded until then) |
| `using-rival` | "we use X", "already have something" | Respect it; one specific difference that matters to their situation, or a question about what they'd change; graceful close if no opening | `replied`; `not-a-fit` only if they say so |
| `price` | "too expensive", "no budget" | Ask what they compare against; offer the smallest way to start if one exists; never invent a discount | `replied` |
| `wrong-person` | "not me", "talk to Sam" | Thank them, ask for an introduction (or confirm the name they gave), then write to that person referencing the referral | `replied`; new row for the referral |
| `not-interested` | "no thanks" | One line: thanks, won't follow up | `not-a-fit` (6-month timed exclusion) |
| `stop` | "unsubscribe", "remove me", "stop emailing" | No pitch. Remove them; one-line confirmation only if the marketer's tool doesn't do it | `unsubscribed` — **permanent suppression** |
| `how-did-you-get-this` | "how did you get my email?", a data request | Say plainly where the details came from (the public page and date in the row) and offer removal; under GDPR answer any access request within a month | `replied`; suppress if they ask |
| `no-show` | booked, didn't attend | One short, friendly reschedule note; one more after a week, then stop | `meeting` (note no-show) |
| `angry` | complaint, threat to report | Apologise once, confirm removal, no defence | `do-not-contact` — permanent |
| `out-of-office` | auto-reply | Pause; resume after their return date | unchanged |
| `bounce` | delivery failure | Nothing to send | `bounced` — permanent |
## Objections — answers that work
Each answer: acknowledge in a few words, one honest point or question, one small next step. Proof only if signed off; never imply customers, conversations or usage the brand can't show ("most teams we talk to", "brands like yours").
- **"We already use <rival>."** "Makes sense — <rival> is a solid choice. Out of curiosity, is there anything you'd change about how <the job> works today?" Or one specific, true difference that matters to their signal. Never bash the rival.
- **"Not a priority right now."** "Fair. When does <the pain> usually come up for you — <season / quarter>? Happy to check back then."
- **"Send me some info."** One short, specific resource and one question; never a 20-page deck.
- **"How much is it?"** The real price from the brand's pricing page (with its date), and what decides the plan.
- **"We built our own."** Respect it; ask what maintaining it costs them; offer to compare notes, not to replace.
- **"We tried something like this and it didn't work."** Ask what went wrong; say only what's genuinely different.
- **"Does it integrate with <tool>?"** Only what the brand's site or claims say; if unknown, "I'll check and come back" — and say so in the pack as a gap.
- **"I'm new here, still settling in."** Offer one quick win for their first 90 days, or a date to check back.
- **"Procurement / security review takes months."** Ask about the process early; offer what the brand publishes (security page, terms).
## Leads who don't fit
| Situation | What to send |
|---|---|
| Right company, wrong person | A referral ask to the right role (warmer than cold) |
| Close, not yet (too small, too early, wrong region for now) | A polite "let's stay in touch"; re-check after funding, a headcount jump, a new leader, or 6 months |
| Clearly outside the fit | A gracious no that keeps the door open |
| Competitor's employee | Nothing; mark `do-not-contact` |
| Existing customer | Nothing from outreach; flag to the marketer |
## Writing the reply
Short (under 80 words), in the sender's voice, no new pitch beyond the one point, one next step. Always say in the pack which ledger status the reply gives the row; the marketer updates their tool, and pastes outcomes back for the ledger.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |