agentleFS
Othmane-KhadriOthmane-Khadri/YALC-the-GTM-operating-system/.claude/skills/research-prospect/SKILL.md

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

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
  1. Distinctive:

    Don't summarize the summary — pass through what the CLI returns.

    line 46
  2. Distinctive:

    Read-only on the local DB — research output is rendered in chat, not persisted.

    line 56

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 via enrich-with-signals?"

Notes

  • Requires FIRECRAWL_API_KEY in ~/.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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.