Agent skill

Find Me Leads

Surface fresh leads in a segment from a source you pick: your CRM closed-won lookalikes, a LinkedIn comment thread, a recent-funding feed, a Google Maps search, or a subreddit.

MITAuto-check passedSales & Support

Install Find Me Leads

skills CLI

$ npx skills add gethouston/houston --skill find-me-leads -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install gethouston/houston find-me-leads --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/gethouston/houston.git skills-src && mkdir -p .claude/skills && cp -r skills-src/store/agents/sales/.agents/skills/find-me-leads .claude/skills/find-me-leads && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "find-me-leads" agent skill from https://github.com/gethouston/houston/tree/main/store/agents/sales/.agents/skills/find-me-leads into .claude/skills/find-me-leads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-me-leads", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/gethouston/houston/tree/main/store/agents/sales/.agents/skills/find-me-leads

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add gethouston/houston --skill find-me-leads -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install gethouston/houston find-me-leads --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gethouston/houston.git skills-src && mkdir -p .agents/skills && cp -r skills-src/store/agents/sales/.agents/skills/find-me-leads .agents/skills/find-me-leads && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "find-me-leads" agent skill from https://github.com/gethouston/houston/tree/main/store/agents/sales/.agents/skills/find-me-leads into .agents/skills/find-me-leads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-me-leads", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add gethouston/houston --skill find-me-leads -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install gethouston/houston find-me-leads --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gethouston/houston.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/store/agents/sales/.agents/skills/find-me-leads .cursor/skills/find-me-leads && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "find-me-leads" agent skill from https://github.com/gethouston/houston/tree/main/store/agents/sales/.agents/skills/find-me-leads into .cursor/skills/find-me-leads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-me-leads", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/gethouston/houston.git --path store/agents/sales/.agents/skills/find-me-leads

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add gethouston/houston --skill find-me-leads -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install gethouston/houston find-me-leads --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gethouston/houston.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/store/agents/sales/.agents/skills/find-me-leads .gemini/skills/find-me-leads && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "find-me-leads" agent skill from https://github.com/gethouston/houston/tree/main/store/agents/sales/.agents/skills/find-me-leads into .gemini/skills/find-me-leads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-me-leads", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install gethouston/houston find-me-leads

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add gethouston/houston --skill find-me-leads -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/gethouston/houston.git skills-src && mkdir -p .github/skills && cp -r skills-src/store/agents/sales/.agents/skills/find-me-leads .github/skills/find-me-leads && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "find-me-leads" agent skill from https://github.com/gethouston/houston/tree/main/store/agents/sales/.agents/skills/find-me-leads into .github/skills/find-me-leads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-me-leads", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add gethouston/houston --skill find-me-leads -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install gethouston/houston find-me-leads --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gethouston/houston.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/store/agents/sales/.agents/skills/find-me-leads .opencode/skills/find-me-leads && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "find-me-leads" agent skill from https://github.com/gethouston/houston/tree/main/store/agents/sales/.agents/skills/find-me-leads into .opencode/skills/find-me-leads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-me-leads", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: find-me-leads
GitHub stars: 118
Token cost: ~1.3k tokens
SKILL.md length: 600 words
Files: 1
Skills in repo: 10
Repo updated: Oct 11, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Surface fresh leads in a segment from a source you pick: your CRM closed-won lookalikes, a LinkedIn comment thread, a recent-funding feed, a Google Maps search, or a subreddit.

Works in 8 steps: Read ledger + playbook. Gather missing… → Pick source. Based on segment + user… → Pull candidates. Via composio search per… → …
Signal that surfaced them
SKILL.md covers When to use, Connections I need, Information I need and Steps, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Find Me Leads is an agent skill from gethouston/houston. Surface fresh leads in a segment from a source you pick: your CRM closed-won lookalikes, a LinkedIn comment thread, a recent-funding feed, a Google Maps search, or a subreddit. I quick-score each against your playbook's hard disqualifiers and only keep GREEN and YELLOW. Every row cites the trigger signal that surfaced them.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support. It works with LinkedIn, Reddit and Google Maps Platform. The repository describes itself as: Open source platform for AI-native products. Pre-built AI agents with real tools and 1000+ integrations, in a Rust engine + Tauri desktop app. Free forever. The licence is MIT.

When your agent uses it

Signal that surfaced them

Example prompts

“/find-me-leads”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

Read ledger + playbook. Gather missing required fields
Pick source. Based on segment + user intent, ask
Pull candidates. Via composio search per picked
Per-candidate quick-score - apply playbook's hard
Write batch file to `leads/batches/{segment-slug}-{YYYY-
Append to leads.json. Per surviving candidate, append
Append to outputs.json
Summarize to user. Top 3 leads inline + full file

What it can do on your machine

Read from SKILL.md and the folder at commit e0fd637. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Find Me Leads loads about 1.3k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 600 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~85
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gethouston/houston at commit e0fd637, republished under its MIT licence (© gethouston). 600 words, ~1,320 tokens.

Download SKILL.mdSave it as .claude/skills/find-me-leads/SKILL.md (or your agent's skills folder).

name: find-me-leads
description: Surface fresh leads in a segment from a source you pick: your CRM closed-won lookalikes, a LinkedIn comment thread, a recent-funding feed, a Google Maps search, or a subreddit. I quick-score each against your playbook's hard disqualifiers and only keep GREEN and YELLOW. Every row cites the trigger signal that surfaced them.
version: 1
category: Sales
featured: yes
image: handshake
integrations: hubspot, salesforce, attio, linkedin, twitter, reddit, firecrawl
x_houston.created_by: houston
x_houston.skill_schema: 1

Find Me Leads

Surface net-new leads in segment.

When to use

"find me {N} leads in {segment}".
"surface leads I can reach out to this week".
"compile leads from {LinkedIn post / subreddit / event}".
Scheduled: weekly prospecting routine.

Connections I need

I run external work through Composio. Before this skill runs I check that the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.

CRM - expand from lookalikes of your closed-won accounts. Required if you pick that source.
Social - pull commenters from a LinkedIn post or thread. Required if you pick that source.
Search / research - pull recent-funding or recent-hire signals. Required if you pick that source.
Scrape - parse a Google Maps results page or a subreddit. Required if you pick that source.

If none of the source categories are connected I stop and ask you to connect at least one (CRM is the strongest place to start because closed-won lookalikes convert best).

Information I need

I read your sales context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.

Your sales playbook - Required. Why I need it: I need your ideal customer profile and disqualifiers to quick-score candidates honestly. If missing I ask: "I don't have your playbook yet - want me to draft it now?"
The segment you want leads in - Required. Why I need it: "leads" is too broad to filter against your ideal customer profile. If missing I ask: "Which segment should I pull from - industry, company size, role, geography?"
How many leads you want - Required. Why I need it: caps the search and the file. If missing I ask: "How many leads do you want me to surface - 10, 20, 50?"
Where to source from - Required. Why I need it: each source uses a different connected tool. If missing I ask: "Should I expand lookalikes from your CRM, pull commenters from a LinkedIn post, scan a recent-funding feed, scrape a Google Maps area, or surface a subreddit thread?"

Show full SKILL.md (286 more words)Show less

Steps

<!-- houston-workflow:v1 -->

Read ledger + playbook. Gather missing required fields (ONE question each, best-modality first). Write atomically.
Pick source. Based on segment + user intent, ask which source (unless named):
- Connected CRM - expand from lookalike of closed-won.
- LinkedIn comment thread - paste post URL; compile commenters.
- Search engine / funding feed - recent-funding or recent-hire signals in segment.
- Google Maps - local-biz segments.
- Subreddit / community - recent high-engagement posts.
Pull candidates. Via composio search <category> per picked source. Cap ~3× requested count for filtering.
Per-candidate quick-score - apply playbook's hard disqualifiers. Drop RED. Per surviving candidate, capture:
- Company + LinkedIn / website URL.
- Primary contact name + title + LinkedIn (if available).
- Trigger signal that surfaced them (hiring post, Series B, commented on X thread, 4.8-star review - cite specifically).
- Quick fit: GREEN / YELLOW (skip RED - dropped).
Write batch file to leads/batches/{segment-slug}-{YYYY- MM-DD}.md (atomic *.tmp → rename) - query, source, date, lead list with trigger signals cited.
Append to leads.json. Per surviving candidate, append new row with status: "new", source (slug of this search), fitScore (GREEN/YELLOW). No duplicates - check existing rows by company + name. Read-merge-write atomic.

Append to outputs.json:

json

{
  "id": "<uuid v4>",
  "type": "lead-batch",
  "title": "Leads  -  {segment}",
  "summary": "<N leads surfaced from {source}. Top signal: {signal}.>",
  "path": "leads/batches/{segment-slug}-{date}.md",
  "status": "ready",
  "createdAt": "<ISO>",
  "updatedAt": "<ISO>",
  "domain": "outbound"
}

Summarize to user. Top 3 leads inline + full file path. Suggest: "research-an-account depth=enrich-contact on #1 next?" or "score-my-pipeline subject=lead-fit in bulk across these?".

What I never do

Invent leads, names, titles, trigger signals. Every lead ties to real tool response or URL observation.
Contact anyone or push leads into CRM without approval.
Hardcode tool names - Composio discovery at runtime only.

Outputs

leads/batches/{segment-slug}-{YYYY-MM-DD}.md
Appends to leads.json (new rows only).
Appends to outputs.json with type: "lead-batch", domain: "outbound".

Files

Just SKILL.md in store/agents/sales/.agents/skills/find-me-leads of gethouston/houston.

Open the folder on GitHubat commit e0fd637

Compare with similar skills

Find Me Leads next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Find Me Leads compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Find Me Leads this skillgethouston/houston	118	—	~1.3k	Automated safety check: Pass	MIT	today
Apify Multi-Platform Scraperapify/agent-skills	2.4k	2 repos	~1.4k	Automated safety check: Notes	None	2 days ago
Octolenssundial-org/awesome-openclaw-skills	663	—	~2.9k	Automated safety check: Pass	MIT	7 mo ago
Agent ReachPanniantong/Agent-Reach	95k	—	~1.4k	Automated safety check: Pass	MIT	3 days ago
Paid Ads AuditAgriciDaniel/claude-ads	9.9k	—	~1.5k	Automated safety check: Pass	MIT	3 days ago
Prospectingcoreyhaines31/marketingskills	54k	—	~5k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Apify Multi-Platform Scraper
apify/agent-skills
Official
Scrapes public data from social, maps, search and review platforms by choosing from about a hundred Apify Actors and running them through the Apify CLI.
2.4k GitHub starsUsed in 2 repos~1.4k tokens
Data & AnalyticsAuto-check: notes
Octolens
sundial-org/awesome-openclaw-skills
Query and analyze brand mentions from Octolens API. An agent skill from sundial-org/awesome-openclaw-skills.
663 GitHub stars~2.9k tokensUpdated 7 mo ago
Sales & SupportAuto-check passed
Agent Reach
Panniantong/Agent-Reach
Routes web research and platform lookups across 16 sites, including Twitter, Reddit, YouTube, Bilibili, Xiaohongshu and GitHub, through one command-line tool.
95k GitHub stars~1.4k tokensUpdated 3 days ago
Productivity & AutomationAuto-check passed
Paid Ads Audit
AgriciDaniel/claude-ads
Runs a source-grounded paid advertising audit across up to 12 ad platforms, with parallel platform workers, deterministic scoring and a versioned JSON bundle.
9.9k GitHub stars~1.5k tokensUpdated 3 days ago
Marketing & SEOAuto-check passed
Prospecting
coreyhaines31/marketingskills
When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.
54k GitHub stars~5k tokensUpdated 2 days ago
Sales & SupportAuto-check passed
Sales Os
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
139 GitHub stars~2k tokensUpdated 1 mo ago
Sales & SupportAuto-check passed

Questions about Find Me Leads

What does Find Me Leads do?

Surface fresh leads in a segment from a source you pick: your CRM closed-won lookalikes, a LinkedIn comment thread, a recent-funding feed, a Google Maps search, or a subreddit. Find Me Leads is an agent skill from gethouston/houston. Surface fresh leads in a segment from a source you pick: your CRM closed-won lookalikes, a LinkedIn comment thread, a recent-funding feed, a Google Maps search, or a subreddit.

When should I use Find Me Leads?

Find Me Leads fits situations like: signal that surfaced them.

How do I install Find Me Leads in Claude Code?

Run `npx skills add gethouston/houston --skill find-me-leads -a claude-code`. Or copy the skill folder (store/agents/sales/.agents/skills/find-me-leads in gethouston/houston) into .claude/skills/find-me-leads in your project. Claude Code loads it when a task matches its description.

How do I install Find Me Leads in Codex?

Run `npx skills add gethouston/houston --skill find-me-leads -a codex`. Or copy the skill folder (store/agents/sales/.agents/skills/find-me-leads in gethouston/houston) into .agents/skills/find-me-leads in your project. Codex loads it when a task matches its description.

Can I use Find Me Leads in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gethouston/houston --skill find-me-leads -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/find-me-leads, .gemini/skills/find-me-leads, .github/skills/find-me-leads and .opencode/skills/find-me-leads in your project.

What does Find Me Leads need to run?

SKILL.md names no scripts, command-line tools or credentials: Find Me Leads is instructions for the agent only.

Does Find Me Leads access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Find Me Leads safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Find Me Leads use?

Find Me Leads is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Find Me Leads use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Find Me Leads?

Skills that share tags, products or a category with Find Me Leads: Apify Multi-Platform Scraper (apify/agent-skills, 2.4k stars), Octolens (sundial-org/awesome-openclaw-skills, 663 stars), Agent Reach (Panniantong/Agent-Reach, 95k stars) and Paid Ads Audit (AgriciDaniel/claude-ads, 9.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Find Me Leads?

gethouston (a GitHub organization) maintains it in gethouston/houston, which has 118 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 11, 2026.

Source: gethouston/houston on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Find Me Leads

Install Find Me Leads

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Find Me Leads

When to use

Connections I need

Information I need

Steps

What I never do

Outputs

Files

Compare with similar skills

Similar skills

Apify Multi-Platform Scraper

Octolens

Agent Reach

Paid Ads Audit

Prospecting

Sales Os

More from gethouston/houston

Find My Bottlenecks

Linkedin Comment To Outreach

Profile My Customer

Acompanhar Minhas Metas

Acompanhar Minhas Promessas

Acompanhar Minhas Renovacoes

Questions about Find Me Leads

Install Find Me Leads

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Find Me Leads

When to use

Connections I need

Information I need

Steps

What I never do

Outputs

Files

Compare with similar skills

Similar skills

More from gethouston/houston

Related

Questions about Find Me Leads