prospect
Build targeted account or contact lists using Common Room's Prospector. Triggers on 'find companies that match [criteria]', 'build a prospect list', 'find contacts at [type of company]', 'show me companies hiring [role]', or any list-building request.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 3.6w
- Forks
- 3.9k
01 前言 Front Matter
- name
- prospect
- description
- Build targeted account or contact lists using Common Room's Prospector. Triggers on 'find companies that match [criteria]', 'build a prospect list', 'find contacts at [type of company]', 'show me companies hiring [role]', or any list-building request.
02 资源文件 1
- 参考文档references/prospect-guide.md1.9 KB
03 SKILL.md 正文
Prospecting
Build targeted account and contact lists using Common Room's Prospector. Supports iterative refinement through natural conversation, intent-based discovery, and both net-new prospecting and signal-based queries against existing accounts.
Critical Distinction: Two Object Types
Common Room's Prospector operates against two fundamentally different object types. Always clarify which one is in play before running a query:
ProspectorOrganization — Companies not yet in Common Room
- Net-new companies that match specified criteria
- Available fields are firmographic only: name, domain, size, industry, capital raised, annual revenue, location
- Fewer filter options — no signal-based filters, no scores, no activity history
- Use when: building a brand-new target list, territory planning, top-of-funnel expansion
Organization (in Common Room) — Companies already in your CR workspace
- Full signal data available: product usage, community activity, CRM fields, scores, custom fields
- Much richer filter set — includes signal-based, score-based, segment-based, and firmographic filters
- Use when: finding warm accounts to prioritize, identifying expansion candidates, surfacing intent signals within existing pipeline
When a user's request could apply to both (e.g., "Show companies hiring AI engineers this month"), clarify:
"Are you looking for net-new companies not yet in Common Room, or filtering accounts already in your workspace?"
The catalog should make this distinction explicit so the LLM can select the right Prospector endpoint.
Step 0: Load User Context (Me)
Fetch the Me object to get the user's segments. When prospecting against Organization records (accounts already in CR), default to filtering within "My Segments" unless the user asks for a broader search.
Step 1: Gather Targeting Criteria
If criteria are already provided, proceed. Otherwise ask:
"What kind of accounts or contacts are you looking for? For example: company size, industry, job titles, signals like recent product activity or community engagement, geographic region, or specific intent signals like recent funding or job postings."
Use the Common Room object catalog to see available filters for each object type. The key distinction:
- ProspectorOrganization — firmographic and technographic filters only (industry, size, geography, funding, tech stack)
- Organization — all firmographic filters plus signal-based, score-based, segment-based, and CRM filters
Lookalike search: If the user asks to "find companies like [X]", first look up the reference company in Common Room (or via web search if not in CR). Extract its key attributes — industry, employee range, tech stack, funding stage, geography — and propose those as filter criteria. Present the derived criteria to the user for confirmation before running the search, since lookalike targeting works best when the user can refine which attributes matter most.
Step 2: Support Iterative Refinement
Prospecting is conversational. Support multi-turn refinement naturally:
- Run initial query with provided criteria
- If results are large (50+), summarize and offer: "I found [N] results. Want to narrow by [suggested filter]?"
- If results are too few (< 5), suggest: "Only [N] results with those filters — I can broaden by relaxing [specific criterion]."
- Apply each refinement as a follow-up query, not a new search from scratch
Example flow:
- Rep: "Find cybersecurity companies in California." → 500 results
- Rep: "Only show ones over 300 employees using AWS." → 47 results
- Rep: "Focus on the ones with recent hiring activity." → 12 results ✓
Step 3: Run the Query and Present Results
Execute the Prospector query with confirmed criteria. Sort by signal strength or fit score where available (not alphabetically).
For ProspectorOrganization (net-new) results:
| Company | Domain | Industry | Size | Capital Raised | Revenue | Location |
|---|
For Organization (in CR) results:
| Company | Industry | Size | Top Signal | Signal Date | Score | CRM Stage |
|---|
Flag any results where data is thin or the most recent signal is older than 90 days.
Step 3.5: Enrich Net-New Results with Web Search
For ProspectorOrganization results (net-new companies not in CR), run a quick web search on the top 3–5 companies to add context beyond firmographics. CR has no behavioral signals for these companies, so web search fills the gap — look for recent funding, product launches, leadership changes, or news coverage. Include findings as brief annotations next to each company in the results.
Step 4: Offer Next Steps
- "Want me to draft outreach for the top 3–5 prospects?"
- "Should I run a full account brief on any of these?"
- "Want to refine the criteria or add another filter?"
- "I can format this as a CSV if you'd like to export it."
- "For any net-new companies here, I can add them to Common Room for enrichment." (future capability)
Quality Standards
- Always confirm which object type (ProspectorOrg vs Organization) before running the query
- Default to "My Segments" when querying Organization records, unless user specifies otherwise
- Support iterative refinement — treat each follow-up as a filter adjustment, not a fresh start
- Never mix result fields from ProspectorOrganization and Organization in the same list
- Fewer high-quality results beat a long unqualified list
- Only show data the query returned — leave blank or "—" for missing fields, don't invent values
Reference Files
references/prospect-guide.md— filter types, signal-based sorting, object type distinctions, and list-building strategies
04 同仓库更多 Skills
ticket-deflector
Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."
tax-season-organizer
Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."
tax-prep
Prepares tax materials as a two-link chain — month-end-prep confirms the books are closed and reconciled first, then tax-season-organizer calculates the quarterly estimated payment or builds the year-end 1099-NEC list and accountant packet from those closed numbers. Requires a ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); uses Gusto, PayPal, and Stripe when connected, else CSV upload. US federal tax math; a non-US business gets the closed-books packet. Prep material for a CPA, never tax advice, nothing filed. Trigger on "quarterly taxes," "estimated tax payment," "how much should I set aside," "1099s," "1099-NEC," "W-9s," "year-end tax prep," "get my books ready for my accountant," any phrasing that suggests a tax deadline is coming, or a question about net profit or YTD income that sounds like worry about a tax bill. An owner who says the period's books are already closed routes to tax-season-organizer directly.
speed-to-lead
Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like "leads are going cold," "did anyone answer that inquiry," "I keep missing form submissions," "nothing falls through the cracks," "handle my inbound," "respond to this lead," or "we lose people because nobody gets back fast enough." Reach for it for a single unanswered inquiry as readily as for a standing setup.
social-content-engine
Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including "I need to post more," "we've gone quiet on Instagram," "what should we post this month," "make the content," "give me a month of posts," "write this in my voice," "repurpose this," or "set up our content calendar." Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.
smb-router
The front door to the Small Business plugin. Listens to what the owner needs right now — vague or specific — and routes them to the best skill or slash command for the moment. Also serves as a guide: explains what's available, suggests what to try next, and adapts recommendations based on stored business context. Trigger whenever the owner asks "what can you do," "help me with my business," "what should I focus on," "I don't know where to start," or any open-ended business request that doesn't clearly match a single skill.