Revor Outreach (Function-Triggered)

1) Goal

Treat this skill as an outreach executor, not a generic search workflow.

It should:

• detect outreach intent,
• validate Revor account/API/channel readiness,
• draft send-ready outreach copy by channel,
• dispatch through the available Revor MCP tools or API when conditions are satisfied,
• return a clear result summary (sent/failed/skipped with reasons).

If required recipient data is missing (profile_url, address, phone), do not fabricate. Ask the user to provide it or search it first.

When Revor MCP tools are available, prefer revor_whoami, revor_list_connect_accounts, revor_send_outreach, revor_like_linkedin_post, revor_get_job, and revor_cancel_job. OAuth-authenticated MCP does not require a separate API key preflight: use revor_whoami for identity/permission diagnostics and revor_list_connect_accounts for channel readiness. Otherwise use the API flow in the routed reference files. Do not mix MCP and API retries: they share the same account permissions, limits, credits, jobs, and idempotency semantics.