First-touch outreach
Draft a short first email to someone new from real research, with one specific reason for writing now and an easy way to say no. Draft only.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone wants to write to a person they have never spoken to — a prospect, a partner, an investor — and needs a first email worth reading.
- 01
Start from research, not a template. Use an account brief if there is one; otherwise find two or three sourced facts about the company and the person.
- 02
Find one reason to write now that is about them: a launch, a hire, something they wrote, a problem their job ad describes. If there is none, say so rather than inventing one.
- 03
Keep it under 120 words:
- the first line is about them, not us;
- one sentence on what we do that connects to it;
- one small ask, such as a reply or a 15-minute call.
- 04
Make the subject short and specific. No fake "Re:" and no false urgency.
- 05
Give an easy way out ("if this isn't relevant, say so and I won't follow up"), and make no claim you cannot back up.
- 06
Draft one follow-up for a week later that adds something new, instead of "just checking in".
- 07
Post the drafts as a document with the fact behind each line. Never send, add anyone to a sequence or fill in a contact form; that is a person's call.
If you cannot find a real reason to write, recommend not sending.
The whole SKILL.md: 34 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: cold-outreach-draftdescription: "Draft a short first email to someone new from real research, with one specific reason for writing now and an easy way to say no. Draft only."metadata: title: "First-touch outreach" category: sales tags: [sales, email]--- ## When to use this Someone wants to write to a person they have never spoken to -- a prospect, apartner, an investor -- and needs a first email worth reading. ## How 1. Start from research, not a template. Use an account brief if there is one; otherwise find two or three sourced facts about the company and the person.2. Find one reason to write now that is about them: a launch, a hire, something they wrote, a problem their job ad describes. If there is none, say so rather than inventing one.3. Keep it under 120 words: - the first line is about them, not us; - one sentence on what we do that connects to it; - one small ask, such as a reply or a 15-minute call.4. Make the subject short and specific. No fake "Re:" and no false urgency.5. Give an easy way out ("if this isn't relevant, say so and I won't follow up"), and make no claim you cannot back up.6. Draft one follow-up for a week later that adds something new, instead of "just checking in".7. Post the drafts as a document with the fact behind each line. Never send, add anyone to a sequence or fill in a contact form; that is a person's call. If you cannot find a real reason to write, recommend not sending.
- Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Writing
Release notes from merged work
Turn merged work, or a thread about it, into release notes written for the person installing the version rather than the person who built it.
SKILL.md · App - OperationsFeatured
Weekly status report
Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week.
SKILL.md · App - Personal
Meeting notes to action items
Turn a meeting transcript or rough notes into decisions, owned actions with dates, and open questions, and nothing else.
SKILL.md · App