メニュー
Route user intent to the correct Explee product skill (Search, Enrichment, Agents, AutoGTM), using cookie-first auth with API-key fallback. USE WHEN a user has an Explee task but hasn't named the specific product.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Shared reference for all Explee skills: base URL, full endpoint catalog, API-key authentication, canonical curl templates, and shared error/retry/guardrail rules. Other Explee skills reference this instead of repeating boilerplate.
Cookie/session and EXPLEE_SECRETS KV credential model for Explee: build the Cookie header, the cookie-first/key-fallback rule, and the cookie-vs-tracking-param pitfalls. USE WHEN setting up or refreshing Explee auth. Endpoints and API-key auth: see explee-api-core.
Orchestrate an end-to-end AutoGTM flow: ICP query → account/person discovery → enrichment → prioritized outreach list. USE WHEN building a full GTM pipeline from a natural-language objective.
Use Explee Search APIs to find companies and people with natural-language targeting and optional AI scoring. USE WHEN finding accounts, prospects, or converting an ICP to filters.
Run Explee pre-built and custom AI agents, then poll run status and return structured outputs. USE WHEN running agent workflows for extraction, reasoning, or automation.
Use Explee enrichment APIs to find emails for contacts in single or batch mode and track async task status. USE WHEN completing outreach data or finding/verifying work emails.
| name | Explee Orchestrator |
| description | Route user intent to the correct Explee product skill (Search, Enrichment, Agents, AutoGTM), using cookie-first auth with API-key fallback. USE WHEN a user has an Explee task but hasn't named the specific product. |
The single entry skill for Explee tasks. It decides which product workflow to run and which credential mode to use, then delegates the mechanics.
explee-search — companies / people / ICP → filtersexplee-enrichment — single & batch email finding, task statusexplee-agents — pre-built & custom agent runs + pollingexplee-autogtm — end-to-end GTM pipeline (composes search + enrichment)explee-auth-cookie — cookie/session + EXPLEE_SECRETS KV authexplee-api-core — shared base URL, endpoint catalog, templates, errors, guardrailsexplee-search: find companies / accounts / prospects, find people by
role/title/domain, or convert a natural-language ICP to filters.explee-enrichment: find/verify work emails, run single or batch enrichment,
or track task status.explee-agents: run pre-built agent workflows, run custom agents with
prompts/schemas, or poll agent runs.explee-autogtm: build an end-to-end GTM pipeline, turn an ICP into a prioritized
outreach list, or chain search + enrichment + ranking.Preference order (mechanics in explee-auth-cookie and explee-api-core):
EXPLEE_SECRETS KV is available.X-API-Key when the cookie is unavailable or rejected.401 / 403 with a cookie, retry once with the API key; if both fail, ask
the user to refresh credentials.When deployed as a Worker (worker/ in this repo — explee-proxy), this order runs server-side:
callers hit the proxy with X-Proxy-Token: <token> and it injects the cookies / falls back to the
key automatically. See explee-auth-cookie and worker/README.md.
See the shared guardrails in explee-api-core (don't print full credentials, flag credit impact,
pilot before scaling, confirm scope on mutating / high-cost actions).