Individual skill

email-outreach-prep

Prepare personalized email outreach by researching prospects, verifying email addresses, building company context, and generating relevant talking points. End-to-end outreach preparation from prospect identification to send-ready intelligence.

research/email-outreach-prep/SKILL.md

Read pinned source

Source commit cbab58188611e626ccaf54ac346b437d12ea4729

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
208
Repository last updated
Sep 26, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Email Outreach Prep

Prepare personalized email outreach by researching prospects, verifying email addresses, building company context, and generating relevant talking points. End-to-end outreach preparation from prospect identification to send-ready intelligence. Read [the API map](references/sandbase-api-map.md) before selecting a capability.

## Call SandBase capabilities

Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically.

## Capability identifiers

- `strale_email_validate`
- `strale_email_deliverability_check`
- `apollo_company_enrich`
- `linkedin_web_v2_user_profile`