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.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone asks for more prospects, leads or accounts, and there is a table to keep them in (Leads, Prospects, Accounts) — or they want one started.
- 01
Read the table first with query_table: its columns, what a good row looks like, and who is already there. Never re-add a company it holds.
- 02
Pin the profile: who fits, who does not, and the signal that makes a company worth writing to now. Ask only if nothing in the thread says.
- 03
Search with web_search, then read each candidate's own site with web_fetch. Keep a company only when you can link the signal.
- 04
Add them yourself with upsert_rows, matching on Website or Company, a few rows at a time: every column the table has, the signal link in its own column, Status left for the person. Do not paste rows for someone to copy.
- 05
Reply with what you added, what you skipped and why, and the table's new row count.
If a tool refuses (the table is not shared with you, or read-only), quote its words and say where the person changes that. Never claim you have no tools without calling them first.
The whole SKILL.md: 31 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: lead-list-builddescription: "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."metadata: title: "Build a lead list into a table" category: prospecting tags: [leads, tables, research]--- ## When to use this Someone asks for more prospects, leads or accounts, and there is a table tokeep them in (Leads, Prospects, Accounts) -- or they want one started. ## How 1. Read the table first with query_table: its columns, what a good row looks like, and who is already there. Never re-add a company it holds.2. Pin the profile: who fits, who does not, and the signal that makes a company worth writing to now. Ask only if nothing in the thread says.3. Search with web_search, then read each candidate's own site with web_fetch. Keep a company only when you can link the signal.4. Add them yourself with upsert_rows, matching on Website or Company, a few rows at a time: every column the table has, the signal link in its own column, Status left for the person. Do not paste rows for someone to copy.5. Reply with what you added, what you skipped and why, and the table's new row count. If a tool refuses (the table is not shared with you, or read-only), quote itswords and say where the person changes that. Never claim you have no toolswithout calling them first.
- 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
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 - Prospecting
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.
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