research-prospect
Skill298 starsChanged 6 months agoMITView on GitHub
Run ad-hoc web research on a prospect (company URL or person) — Firecrawl scrapes the marketing site, key pages (pricing, careers, blog), and surfaces a brief. Read-only. Use when the user says 'research this prospect', 'tell me about [company]', 'do a deep dive on [domain]', 'pull a brief on this lead', or 'crawl the marketing site for [name]'. Side-effecting on the Firecrawl side (API call), no local DB writes.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- aberson/skill-meshtheir own version, first seen Oct 24, 2026
- Duckz289/Pipeline-to-proposal-Plugin-STANDARDtheir own version, first seen Jul 27, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- aberson/skill-mesh★ 2same name
- Duckz289/Pipeline-to-proposal-Plugin-STANDARD★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- answer-linkedin-commentsSkill
- build-routineSkill
- campaign-dashboardSkill
- campaign-strategySkill
- claap-weekly-recapSkill
- cross-platform-schedulerSkill
- debuggerSkill
- enrich-with-signalsSkill
- find-lookalikesSkill
- fullenrich-content-engagersSkill
- fullenrich-event-attendeesSkill
- fullenrich-network-activationSkill
- fullenrich-plg-reverse-lookupSkill
- icp-importSkill
- import-leadsSkill
- integrate-with-yalcSkill
- launch-linkedin-campaignSkill
- lemlist-campaign-from-icpSkill
- list-adaptersSkill
- lost-deal-revival-agentSkill
- notion-reviewSkill
- personalize-messageSkill
- predictleads-dashboardSkill
- predictleads-lookalikesSkill
- predictleads-signalsSkill
- prospect-discovery-pipelineSkill
- provider-builderSkill
- qualify-leadsSkill
- run-competitive-intelSkill
- run-doctorSkill
- scrape-post-engagersSkill
- send-cold-emailSkill
- setupSkill
- show-routineSkill
- track-campaignsSkill
- yalc-orientationSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 46
Don't summarize the summary — pass through what the CLI returns.
- Distinctive: line 56
Read-only on the local DB — research output is rendered in chat, not persisted.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Research Prospect
I'll wrap research. Take a URL, run a Firecrawl scrape against the canonical pages, and produce a brief.
When This Skill Applies
- "research this prospect"
- "tell me about [company]"
- "do a deep dive on [domain]"
- "pull a brief on this lead"
- "crawl the marketing site for [name]"
NOT this skill (use enrich-with-signals instead):
- "pull buying signals" — that's structured PredictLeads data, not narrative research.
NOT this skill (use personalize-message with --enrich instead):
- "personalize a message for them" — that auto-pulls research as part of the personalization.
Workflow
Step 0 — Ask for the URL
"What's the company URL or LinkedIn profile?"
Step 1 — Validate URL
Step 2 — Shell out
cd ~/Desktop/gtm-os && set -a && source .env.local && set +a && \
npx tsx src/cli/index.ts research --url <url>Step 3 — Parse output
CLI emits a brief markdown summary + key facts table.
Step 4 — Render the brief verbatim
Don't summarize the summary — pass through what the CLI returns.
Step 5 — Offer follow-ups
"Want me to (a) personalize a message for someone at this company via
personalize-message, (b) check buying signals viaenrich-with-signals?"
Notes
- Requires
FIRECRAWL_API_KEYin~/.gtm-os/.env. - Firecrawl call cost varies by depth (default: 1 credit per ~5 pages).
- Read-only on the local DB — research output is rendered in chat, not persisted.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

