OpenOutreach Skill
What it does
Open-source AI agent for B2B lead generation — describe your product, it finds the people who fit, explains why each one does, and emails them from your mailbox. Self-hosted CLI, one install.
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category 自動化とエージェント
作者向け:README にバッジを付ける
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/eracle-openoutreach)似た Skill
同じ種類の作業。Skill 一覧と同じ並び
eracle による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
Skill と MCP の違い
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
使えるアプリ
Claude CodeCodexCursor
提供元の README と repo のフォルダから判断
インストール
Is it safe?
- Who made it
GitHub account eracle (person), 13 years old
- Use and upkeep
★ 3,722 stars · code last changed 2026年11月14日
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 85c9367 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
Option 1Upload to claude.ai (web and app)
Download from GitHub
This skill uses the GPL-3.0 license, which is not on the list we redistribute, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the skills/find-leads folder again. The ZIP must have a find-leads folder with SKILL.md at the top level, no loose files
Open Skills on claude.ai and upload
+Create skillUpload a skillpick find-leads.zip
No Upload button? Turn on file creation first
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Claude Code にインストールしてもらう
この文をコピーして Claude Code のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code を開き直し、/find-leads と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
For Terminal users
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
提供元のおすすめの方法
コマンドを確認中 · 確認が通るとコピーボタンが出ます
提供元の README から引用。提供元のコードをダウンロードして実行します
ターミナルを開く
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
skill フォルダを ~/.claude/skills にコピー
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Claude Code を開き直し、/find-leads と入力するか関連する作業を頼むと Claude が自動で使います
ChatGPT デスクトップアプリ
ChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
Option 1ChatGPT にインストールしてもらう
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2自分でフォルダを置く
find-leads フォルダを ~/.agents/skills/find-leads に置きます
~ はホームフォルダ($HOME)です
For Terminal users
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
ターミナルを開く
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
skill フォルダを ~/.agents/skills にコピー
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
インストールしたあと
- ChatGPT デスクトップアプリ:サイドバーの Skills を開いて Skill があるか確認します
- 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
- Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Web 版とモバイル版の ChatGPT
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1Codex にインストールしてもらう
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
For Terminal users
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
ターミナルを開く
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
skill フォルダを ~/.agents/skills にコピー
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Codex を開き直して関連する作業を頼むと、Codex が skill を一覧に出します
Option 1Cursor にインストールしてもらう
この文をコピーして Cursor のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor の Agent チャットで / を入力し find-leads を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
For Terminal users
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
ターミナルを開く
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
skill フォルダを ~/.cursor/skills にコピー
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Cursor の Agent チャットで / を入力し find-leads を選ぶ
Option 1Let the AI install it
Skill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
元の SKILL.md を見る
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: find-leads
description: Find qualified B2B leads with OpenOutreach — run `openoutreach find N [emails]`, read the CSV it prints on stdout, and hand the rows to whatever sends. Use when the user wants leads, prospects, an ICP-matched contact list, or asks what a campaign already has. Also covers first-run setup (`openoutreach init`), `openoutreach status`, when a lookup costs money, and the verbs that actually send mail (`send`, `run`) — which you never run unasked.
user-invocable: true
argument-hint: [N] [emails]
---
# Finding leads with OpenOutreach
OpenOutreach is a self-hosted CLI lead finder. You describe a product and a target market once;
each run discovers candidates from a licensed data source, has an LLM judge each one against that
ICP, **writes down why**, and prints every lead it has as CSV on stdout.
It is one bounded command: ask for an amount, get rows, exit. **There is no daemon, no background
job, no file the tool writes for the operator, and nothing to poll.** If you find yourself wanting
to tail a log or wait for something, you have the wrong model of this tool.
**It can also send** — `send` mails what is stored, and `run` is find-then-send in one pass. Both
put mail in strangers' inboxes under the user's own identity, so **never run either one unless the
user asked for mail to go out.** `find` is the default answer to "get me leads"; its deliverable is
a CSV for whatever they already send with.
## Is it installed?
```bash
openoutreach status # human summary
openoutreach status --json # the same document, for you to parse
```
If the command is missing, run it through `uvx` instead — `uvx openoutreach ...` — or install it
with `pip install openoutreach`. Inside a checkout of the repo, `python manage.py <verb>` is the
same entry point.
`status` never blocks and never spends. It answers `onboarding` (complete or which
`OPENOUTFIND_*` variables are missing), the counts, the credit balance, anything `blocked`, and a
`next_action` — start there whenever you are unsure what state the user is in. It reports the
finding half; the sending half reports itself when `send` runs.
## Setup, if `status` says onboarding is incomplete
```bash
openoutreach init # interactive wizard on a TTY; environment otherwise
```
`init` creates the database, asks for whatever this install has not been told, and stops **before
spending anything**. It is one flow over both halves — the finding first, then what only the sending
needs. Every answer can come from the environment instead of a prompt, which is what makes a
headless setup possible:
| Step | Environment variables |
|------|----------------------|
| campaign | `OPENOUTFIND_PRODUCT_DOCS`, `OPENOUTFIND_CAMPAIGN_TARGET` |
| llm | `OPENOUTFIND_AI_MODEL`, `OPENOUTFIND_LLM_API_KEY` |
| bettercontact | `OPENOUTFIND_BETTERCONTACT_API_KEY` |
| account | `OPENOUTFIND_OPERATOR_EMAIL`, `OPENOUTFIND_OPERATOR_COUNTRY` |
| the sender | `OUTSEND_OPERATOR_NAME` (who signs the mail), `OUTSEND_MAILBOX_ADDRESS`, `OUTSEND_MAILBOX_PASSWORD` (the provider's **app password**), optional `OUTSEND_BOOKING_LINK` |
**A variable you export is an answer already given**, and the wizard skips that question rather than
asking for it again. The fields both halves share — what you sell, who for, the model and its key —
are asked once and exported under each child's own name (`OPENOUTFIND_PRODUCT_DOCS` and
`OUTSEND_PRODUCT_DOCS` are the same answer), so there is no second copy to keep in step. On a
machine with no TTY, an incomplete install fails naming every variable that would have completed it.
The product description and target market are pages of prose, so pass them as files rather than
shell-quoted strings — quoting a markdown paragraph on a command line corrupts it quietly:
```bash
openoutreach init --product-docs product.md --target target.md
```
**Never guess the mailbox credentials** — ask the user for them.
**`init` is the only verb that asks.** `find` creates the database if it has to, but it never
prompts: given an unconfigured install it stops with `onboarding_incomplete`, naming every variable
that would have satisfied it. So run `init` when the user has not configured anything — it fails
cheaply, before any work.
## The work verb you reach for
```bash
openoutreach find 10 # ten more qualified leads — free, and cannot spend
openoutreach find 10 --emails # ...and buy an address for whatever cleared the gate
openoutreach find 10 emails # ten more *carrying* a verified email (≤10 credits)
openoutreach find 0 # no work at all — just print what is already there
```
Three things about `N` that are easy to get wrong:
- **`N` is how many *more*, not a total.** A store with 30 leads answers `find 10` by working
until it has 40. Runs are fully resumable; re-running continues rather than restarting.
- **`find 0` does no work and spends nothing.** It is how you re-export, or answer "what do we
have?" without running a job.
- **`N` is a budget when the unit is `emails`.** The provider bills one credit per verified hit, so
`find 10 emails` is capped at ten credits by construction — the number typed is in the same unit
as the invoice.
### What costs money
Discovery and qualification are free (they cost only the user's own LLM key). **The address lookup
is the only paid step**, and it is opt-in:
- a bare `find N` **cannot** spend a credit, however many leads are queued past the confidence gate;
- `--emails` permits buying for whatever is ready;
- the `emails` unit implies `--emails`, because a goal counted in addresses cannot be met without
buying them.
**Do not add `emails` or `--emails` unless the user asked for email addresses.** If they said
"find me leads", run the free form and tell them the paid form exists. A lead with no address still
exports — the row carries the person, the company and the reason with a blank `email`.
### Other flags
| Flag | What it does |
|------|--------------|
| `--new` | Print only the rows *this run* produced, instead of every lead in the store. Use this when you are reading stdout into your own context rather than into a file. |
| `--json` | The rows as JSON Lines on stdout (the full record, `profile_text` included); the run's metadata — goal, outcome, `next_action` — as one JSON object on stderr, and nothing else there. Prefer it when you are going to parse. |
| `--batch` | Hold everything until the job ends, then print every lead once — the old, pre-streaming shape. Output is progressive *by default* now (see below); reach for `--batch` only if whatever you are piping into cannot handle a stream — a strict single-document JSON parser, for instance. Not something you need for reading into your own context — that is what `--new` is for. |
| `--debug` | Show the discovery walk's reasoning on stderr. For diagnosing a run that finds nothing. |
| `--open` | Opens each new lead's profile in a browser. **Never pass this** — it is for a human at a terminal, and it errors out headless. |
| `--db PATH` | Work against a SQLite file other than `~/.openoutreach/data/db.sqlite3` (same as `OPENOUTREACH_DB`). Accepted by every verb. |
| `--agent-qualify` | Opt out of `AI_MODEL` for the qualify step — see *Answering qualify yourself* below. |
A run can take a while: each lead is an LLM call, and paid lookups are polled. Give it a generous
timeout rather than a short one plus a retry — a killed run wastes the work, though nothing already
qualified is lost.
## Answering qualify yourself, with no second LLM key
If you (the calling agent) are already reasoning about these leads in this conversation,
`OPENOUTFIND_LLM_API_KEY` is a second, redundant LLM bill for a verdict you can write yourself. Add
`--agent-qualify` and the run stops at the first candidate needing one instead of calling `AI_MODEL`
— and in this mode `openoutreach status`/`find` never require a model key at all:
```bash
openoutreach find 10 --話し合い
質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
GitHub の情報
- GitHub スター
- 3,722
- 提供元
- eracle
- ライセンス
- GPL-3.0
- 最終コード更新
- 2026年11月14日
- repo 内の SKILL.md(翻訳版とテンプレートを含む)
- 1
- トピック
- agentic, agentic-ai, agentic-workflow, ai-agents, ai-sdr, b2b, cold-email, cold-outreach, email-automation, icp, lead-generation, lead-qualification