Website contact enrichment agent skill for Claude Code and agents

This skill gives an agent instructions and a script for collecting public emails, phone numbers and social profile links from websites through an Apify Actor.

Folder on GitHub Run on Apify

The Website Contact Page Email & Phone Crawler Actor prioritises contact, about, team, support and imprint pages. The skill packages the runner, example input and reference files for preparing website scans that return a normalised contact record per site.

Install

Copy the folder website-contact-page-email-and-phone-crawler from GitHub, or save the three files below into it.
Place it in ~/.claude/skills/website-contact-page-email-and-phone-crawler/ for Claude Code, or ~/.agents/skills/website-contact-page-email-and-phone-crawler/ for Codex and other skill-aware agents.
Export APIFY_TOKEN, start the agent and ask for the job in plain words; the description tells the agent when to use the skill.
Or let the skills CLI place the Actor's SKILL.md for your agent: npx skills add https://recipeforagents.com --skill website-contact-page-email-and-phone-crawler (the SKILL.md only; the runner script comes from the GitHub folder).

SKILL.mdwebsite-contact-page-email-and-phone-crawler/SKILL.md

---
name: website-contact-page-email-and-phone-crawler
description: "Crawl a website's contact, about and team pages and collect its public emails, phone numbers, and social media profile links in one normalized record per site. Output fields: websiteUrl, status, emails, primaryEmail, phones and more, as JSON rows. Use it for requests like \"Find emails and phone numbers from a list of websites\", \"website email extractor\", \"contact page scraper\", or a CSV/JSON export of public Any website data."
---

# Website Contact Page Email & Phone Crawler

Crawl a website's contact, about and team pages and collect its public emails, phone numbers, and social media profile links in one normalized record per site.

- Actor: https://apify.com/nimbryxo-studio/website-contact-page-email-and-phone-crawler (ID `nimbryxo-studio~website-contact-page-email-and-phone-crawler`)
- n8n workflow for the same Actor: https://github.com/bolvein-firex/scraping-n8n-workflows/blob/main/docs/website-contact-page-email-and-phone-crawler.md
- Example input: `references/example-input.json`
- Input schema: `references/input-schema.json`
- Output fields: `references/output-fields.json`

Short video breakdown:
- [The email is already on the website](https://www.youtube.com/shorts/MHdeuiVwMZA)

## When to use

Use this skill when the user wants:

- Find emails and phone numbers from a list of websites
- website email extractor
- contact page scraper
- a repeatable export of public Any website data as CSV or JSON

Do not use it for private, login-protected or paywalled data.

## What it returns

One JSON row per result. Columns from the Actor's README (Output section):

- `websiteUrl`: Website Url
- `status`: Status
- `companyName`: Company Name
- `emails`: Emails
- `primaryEmail`: Primary Email
- `roleEmails`: Role Emails
- `namedEmails`: Named Emails
- `emailDetails`: Email Details
- `phones`: Phones
- `primaryPhone`: Primary Phone
- `phoneDetails`: Phone Details
- `socialLinks`: Social Links
- `socialProfiles`: Social Profiles
- `address`: Address
- `contactPageUrl`: Contact Page Url
- `contactForms`: Contact Forms
- `pagesCrawled`: Pages Crawled
- `pagesCrawledUrls`: Pages Crawled Urls
- `maxDepthReached`: Max Depth Reached
- `skippedByRobots`: Skipped By Robots

All 26 declared fields: `references/output-fields.json`.

## Inputs

| Field | Type | Required | Default | Notes |
|---|---|---|---|---|
| `urls` | array | yes |  | Websites to scan for public contact details. You can paste full URLs or bare domains; duplicates are removed. |
| `maxPagesPerSite` | integer | no | 20 | Maximum number of pages to fetch per website. Contact, about, team and imprint pages are prioritised. |
| `maxConcurrency` | integer | no | 5 | How many pages of the same website may be fetched in parallel. |
| `maxSitesConcurrency` | integer | no | 3 | How many websites are scanned in parallel. Lower this if you hit rate limits. |
| `requestTimeoutSecs` | integer | no | 15 | Maximum time to wait for one page before trying the next proxy tier. |
| `defaultCountry` | string | no |  | ISO 3166-1 alpha-2 country used to interpret phone numbers written without an international prefix. Leave empty to infer from the website domain. |
| `useProxy` | boolean | no | false | Start with the Apify proxy ladder instead of trying direct requests first. The actor always retries blocked requests through the proxy ladder automatically. |
| `smartPrioritise` | boolean | no | true | Try common contact, about, team, imprint and support paths first, and queue contact-like links ahead of other internal links. |
| `respectRobotsTxt` | boolean | no | true | Skip pages that the website's robots.txt disallows. Turn this off only when you own the site or have permission to crawl it. |
| `useSitemap` | boolean | no | true | Read sitemap.xml and robots.txt sitemap entries to find contact and about pages that are not linked from the homepage. |
| `renderFallback` | boolean | no | true | If plain HTML contains no email or phone, render up to two pages in a headless browser to capture contacts loaded by JavaScript. |
| `onlyWithContacts` | boolean | no | false | Drop records for websites where no email, phone, social profile or contact form was found. |
| `includeNamedEmails` | boolean | no | true | Include personal addresses such as jane.smith@company.com. When off, only role addresses such as info@, sales@ and support@ are kept. |

Example (`references/example-input.json`):

```json
{
  "urls": [
    "https://apify.com",
    "https://n8n.io"
  ],
  "maxPagesPerSite": 10
}
```

The input passes the Actor's input schema (checked at every publish). The run size follows the number of inputs you pass.

## Run it

Set `APIFY_TOKEN`, then call the synchronous endpoint for small and medium runs (it waits up to 300 seconds):

```bash
curl -s -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~website-contact-page-email-and-phone-crawler/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @references/example-input.json > output.json
```

Or with Node 18+: `node scripts/run.mjs [input.json]`.

For large runs, start an async run and read its dataset when it finishes:

```bash
RUN=$(curl -s -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~website-contact-page-email-and-phone-crawler/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
  -d @references/example-input.json)
RUN_ID=$(echo "$RUN" | jq -r '.data.id'); DATASET=$(echo "$RUN" | jq -r '.data.defaultDatasetId')
curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID?waitForFinish=60" -H "Authorization: Bearer $APIFY_TOKEN" | jq -r '.data.status'
curl -s "https://api.apify.com/v2/datasets/$DATASET/items?format=json" -H "Authorization: Bearer $APIFY_TOKEN" > output.json
```

## Cost and limits

- Apify bills the Actor's usage on your account; the Actor's Pricing tab shows the current price.
- Keep the limit in the input small for a first run.

## Guardrails

- Public data only. Do not pass cookies, sessions or private account data.
- Do not use the output for spam, harassment or unlawful discrimination.
- Check the target site's terms and local law before running at scale.

Checked against the Agent Skills format and the Actor's input schema: 15 of 15 checks pass

SKILL.md starts with YAML front matter
name is 1-64 lowercase letters, digits and single hyphens
name matches the skill folder name
description is present, at most 1024 characters and has no angle brackets
front matter uses only spec fields
compatibility is at most 500 characters
body has instructions
field descriptions end on whole sentences
no credential values are embedded
the token is read from APIFY_TOKEN
Example input: all 1 required input field is present
Example input: every input key exists in the published input schema
Example input: every value has the type the schema declares
Example input: every choice field uses one of its published options
Example input: numbers respect the published minimum and maximum

Runner scriptwebsite-contact-page-email-and-phone-crawler/scripts/run.mjs

// Minimal runner: node scripts/run.mjs [input.json | '{"json": "input"}']
// Needs Node 18+ and APIFY_TOKEN. Without an argument it uses references/example-input.json.
import fs from 'node:fs';
import path from 'node:path';
import { fileURLToPath } from 'node:url';

const token = process.env.APIFY_TOKEN;
if (!token) {
  console.error('Set APIFY_TOKEN');
  process.exit(1);
}
const actorId = process.env.ACTOR_ID || "nimbryxo-studio~website-contact-page-email-and-phone-crawler";
const here = path.dirname(fileURLToPath(import.meta.url));
const arg = process.argv[2];
const raw = !arg
  ? fs.readFileSync(path.join(here, '..', 'references', 'example-input.json'), 'utf8')
  : (arg.trim().startsWith('{') ? arg : fs.readFileSync(arg, 'utf8'));
const input = JSON.parse(raw);

const res = await fetch(`https://api.apify.com/v2/acts/${actorId}/run-sync-get-dataset-items`, {
  method: 'POST',
  headers: { 'Content-Type': 'application/json', Authorization: `Bearer ${token}` },
  body: JSON.stringify(input)
});
if (!res.ok) {
  console.error(`HTTP ${res.status}: ${(await res.text()).slice(0, 500)}`);
  process.exit(1);
}
console.log(JSON.stringify(await res.json(), null, 2));

Example inputwebsite-contact-page-email-and-phone-crawler/references/example-input.json

{
  "urls": [
    "https://apify.com",
    "https://n8n.io"
  ],
  "maxPagesPerSite": 10
}

Using it

Use Node 18+ and set APIFY_TOKEN in the environment available to the runner. Check that scripts/run.mjs references APIFY_TOKEN and the intended Actor endpoint, with no embedded credentials.
Edit references/example-input.json to supply urls and a deliberate maxPagesPerSite limit. Check that the file is valid JSON and matches references/input-schema.json.

Prefer MCP? The Website Contact Page Email & Phone Crawler page has configs for eight clients and a shorter, API-only SKILL.md.

Questions

Can the input contain bare domains?

urls accepts full website URLs or bare domains, and duplicate inputs are removed. The Actor treats subdomains within the same registrable domain as part of the same site.

Can it exclude personal email addresses?

Set includeNamedEmails to false to keep role addresses such as info@, sales@ and support@. Review the retained addresses against the purpose of the contact collection.

Sources

scraping-skills repository
Agent Skills specification, checked 2026-11-10