Ideal customer profile
Write a one-page ideal customer profile from real wins, losses and conversations: who buys, why now, what disqualifies, and the signals to search for.
In Lobstack: Skills › Library › Add
What your agent will do.
Before building a lead list, or when outreach replies are thin and nobody can say who the product is really for.
- 01
Gather evidence, not opinions: customers who paid, deals that were lost, replies to outreach, support threads. search_history and the tables are a start; ask the person for what you cannot see.
- 02
Write the profile:
- Who: industry, size, region, team that buys, the job title who signs.
- Why now: the event that makes them look — a hire, a launch, a cost.
- Disqualifiers: what makes a company a bad fit, however big.
- Signals: what can be found on the web to spot one (job ads, pages, technology used), each with an example link.
- 03
Mark every line as seen in N cases or as a guess.
- 04
End with three search queries a lead-list run could start from.
Post it as a document. A profile that fits everyone finds no one: cut until it excludes someone.
The whole SKILL.md: 30 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: ideal-customer-profiledescription: "Write a one-page ideal customer profile from real wins, losses and conversations: who buys, why now, what disqualifies, and the signals to search for."metadata: title: "Ideal customer profile" category: prospecting tags: [sales, strategy]--- ## When to use this Before building a lead list, or when outreach replies are thin and nobody cansay who the product is really for. ## How 1. Gather evidence, not opinions: customers who paid, deals that were lost, replies to outreach, support threads. search_history and the tables are a start; ask the person for what you cannot see.2. Write the profile: - Who: industry, size, region, team that buys, the job title who signs. - Why now: the event that makes them look -- a hire, a launch, a cost. - Disqualifiers: what makes a company a bad fit, however big. - Signals: what can be found on the web to spot one (job ads, pages, technology used), each with an example link.3. Mark every line as seen in N cases or as a guess.4. End with three search queries a lead-list run could start from. Post it as a document. A profile that fits everyone finds no one: cut until itexcludes someone.
- Prospecting
Account research
Build a one-page brief on a company or contact from public sources: what they do, recent news, likely priorities, fit, and who to talk to. Every line sourced.
SKILL.md · App - Prospecting
Build a lead list into a table
Find companies that fit a profile, check each one, and add them to a table yourself with upsert_rows, so the list grows without duplicates.
SKILL.md · App - Prospecting
Enrich the rows in a lead table
Fill in the blanks on rows already in a table — website, size, signal, contact role — from sourced public facts, and write them back with update_rows.
SKILL.md · App - 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