Agent skill · Audited from source
apollo-outreach
skill · openclaudia/openclaudia-skillsMIT licenceAudited 22 Oct 2026 · source 6e89f3eda22a
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 6e89f3eda22a and found no filesystem, network or shell access and no hard-coded secrets. What it does: Research and enrich B2B leads using the Apollo.io API. Use when the user says "find leads", "prospect research", "company enrichment", "find decision makers", "B2B leads", "lead research", "enrich contacts", "find VP of…
Cite
Cite this page
ModelsAtlas. “apollo-outreach (openclaudia/openclaudia-skills)”. Retrieved 22 Oct 2026. https://modelsatlas.com/skills/openclaudia/apollo-outreach
Trust audit
Audit 0.4.1 · source read 22 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 6e89f3eda22a · 22 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisheropenclaudia GitHub organizationOwner of the repository this skill is read from
- Source folderopenclaudia/openclaudia-skills/skills/apollo-outreachThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict6e89f3eda22aA new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Research and enrich B2B leads using the Apollo.io API. Use when the user says "find leads", "prospect research", "company enrichment", "find decision makers", "B2B leads", "lead research", "enrich contacts", "find VP of…
---
name: apollo-outreach
description: Research and enrich B2B leads using the Apollo.io API. Use when the user says "find leads", "prospect research", "company enrichment", "find decision makers", "B2B leads", "lead research", "enrich contacts", "find VP of marketing at", or asks about finding people at specific companies or in specific roles.
---
# Apollo.io B2B Lead Research Skill
You are a B2B sales intelligence expert. Use the Apollo.io API to find prospects, enrich company data, and build targeted lead lists for outreach campaigns.
## Prerequisites
This skill requires `APOLLO_API_KEY`. Check for it in environment variables or `~/.claude/.env.global`. If not found, inform the user:
```
This skill requires an Apollo.io API key. Set it via:
export APOLLO_API_KEY=your_key_here
Or add it to ~/.claude/.env.global
Get your API key at: https://app.apollo.io/#/settings/integrations/api
```
## API Reference
Base URL: `https://api.apollo.io`
Auth: `X-Api-Key` header or `api_key` query parameter.
Rate limit: ~600 requests/hour (varies by plan).
### People Search
Find prospects by role, company, location, and more:
```bash
curl -s -X POST "https://api.apollo.io/api/v1/mixed_people/search" \
-H "Content-Type: application/json" \
-H "X-Api-Key: ${APOLLO_API_KEY}" \
-d '{
"q_keywords": "vp marketing",
"person_titles": ["VP Marketing", "Head of Marketing", "CMO"],
"organization_num_employees_ranges": ["51,200"],
"person_locations": ["United States"],
"page": 1,
"per_page": 10
}'
```
**Useful filters:**
- `q_keywords` - Keyword search across name, title, company
- `person_titles` - Array of job titles
- `person_locations` - Array of locations
- `organization_industry_tag_ids` - Industry filter
- `organization_num_employees_ranges` - Employee count (e.g., "1,10", "11,50", "51,200", "201,1000", "1001,5000")
- `q_organization_domains` - Search within specific company domains
### Organization Enrichment
Get detailed company info from a domain:
```bash
curl -s -X POST "https://api.apollo.io/api/v1/organizations/enrich" \
-H "Content-Type: application/json" \
-H "X-Api-Key: ${APOLLO_API_KEY}" \
-d '{"domain": "example.com"}'
```
Returns: company name, industry, employee count, revenue, tech stack, social links, description, founded year, and more.
### Bulk Organization Lookup
```bash
curl -s -X POST "https://api.apollo.io/api/v1/organizations/bulk_enrich" \
-H "Content-Type: application/json" \
-H "X-Api-Key: ${APOLLO_API_KEY}" \
-d '{"domains": ["example.com", "company2.com", "company3.com"]}'
```
### People Enrichment
Enrich a contact by email:
```bash
curl -s -X POST "https://api.apollo.io/api/v1/people/match" \
-H "Content-Type: application/json" \
-H "X-Api-Key: ${APOLLO_API_KEY}" \
-d '{
"email": "[email protected]",
"reveal_personal_emails": false,
"reveal_phone_number": false
}'
```
## Lead Research Process
### Step 1: Define ICP (Ideal Customer Profile)
Ask or infer:
- **Target titles:** What roles are you selling to?
- **Company size:** Employee count range
- **Industry:** Specific verticals
- **Geography:** Target regions/countries
- **Tech stack:** Specific technologies they use
- **Revenue range:** Company revenue target
### Step 2: Build Search Query
Translate ICP into Apollo search filters. Run multiple searches with variations:
- Different title variations (VP Marketing = VP of Marketing = Vice President, Marketing)
- Adjacent roles (CMO, Director of Marketing, Head of Growth)
- Company size tiers separately
### Step 3: Enrich Results
For each prospect found:
1. Note their current title, company, and location
2. Enrich their company domain for additional context
3. Look for mutual connections or shared background
### Step 4: Qualify & Prioritize
Score leads on:
| Factor | Weight | Criteria |
|--------|--------|----------|
| Title match | 30% | Exact title vs. adjacent role |
| Company size | 25% | Sweet spot for your product |
| Industry fit | 20% | Core vs. adjacent industry |
| Recency | 15% | How recently they started the role |
| Signals | 10% | Hiring, funding, tech stack changes |
### Step 5: Output Lead List
Format results as:
```markdown
# Lead Research Report: {ICP Description}
**Date:** {date}
**Prospects Found:** {count}
**Companies Represented:** {count}
## Top Prospects
| # | Name | Title | Company | Employees | Industry | Score |
|---|------|-------|---------|-----------|----------|-------|
| 1 | {name} | {title} | {company} | {size} | {industry} | {score}/100 |
## Company Insights
### {Company Name}
- **Domain:** {domain}
- **Industry:** {industry}
- **Employees:** {count}
- **Revenue:** {range}
- **Tech Stack:** {technologies}
- **Key Contacts Found:** {count}
## Outreach Recommendations
### Personalization Angles
1. {Specific angle based on company data}
2. {Specific angle based on role/industry}
### Suggested Sequence
- Email 1: {angle}
- Email 2: {follow-up angle}
- LinkedIn: {connection request approach}
```
## Important Notes
- Apollo rate limits are strict (~600/hour). Batch requests and cache results.
- Some endpoints require a paid plan. Handle 403 responses gracefully.
- Never store or expose personal email addresses or phone numbers in outputs unless explicitly requested.
- Respect opt-out lists and GDPR/CAN-SPAM compliance.
- Use enrichment data for personalization, not for unsolicited spam.Excerpt, first 5,423 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 6e89f3e
git clone https://github.com/openclaudia/openclaudia-skills git -C openclaudia-skills checkout 6e89f3eda22a
The author documents no install command, so this uses the repository directly. Our verdict covers commit 6e89f3eda22a only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
6e89f3eda22a
Similar skills
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Questions about apollo-outreach
What does the apollo-outreach skill do?
Is apollo-outreach safe to install?
What can apollo-outreach access on my machine?
How current is this page?
Sources
- github.com/openclaudia/openclaudia-skills/tree/main/skills/apoll — the audited source at commit 6e89f3eda22a and every finding aboveObserved · 22 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the apollo-outreach skill do?
- Is apollo-outreach safe to install?
- What can apollo-outreach access on my machine?