菜单
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.
用 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.
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.
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.
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 Auth (Cookie & KV) |
| description | 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. |
The cookie/session credential specialist for the Explee cluster. Endpoints, the API-key header,
request templates, and shared error handling live in explee-api-core — this skill owns only the
cookie/session side and the EXPLEE_SECRETS KV model.
Cookie: header authentication. Include the cookie string exactly as issued:
Cookie: <name1>=<...>; <name2>=<...>; ..._gl and _gcl_au are
URL analytics parameters — not valid Cookie header values. Use only real browser cookie
key/value pairs from the Cookie request header.https://api.explee.com/public/api/docs) and confirm
assumptions before any mutating request.Use the four templates in explee-api-core (T1–T4), but swap the auth header:
export EXPLEE_COOKIE='<name1>=<...>; <name2>=<...>'
# replace: -H "X-API-Key: ${EXPLEE_API_KEY}"
# with: -H "Cookie: ${EXPLEE_COOKIE}"
For headless / Worker use, cookie values are stored in a Cloudflare KV namespace EXPLEE_SECRETS
with three keys:
| KV key | Holds |
|---|---|
ex_access | Explee access cookie value |
ex_org | Explee org cookie value |
logto_session | Value of the Logto session cookie (logto_<session_id>) |
A Cloudflare Worker reads these three keys, assembles the Cookie: header, calls Explee, and on
401 / 403 falls back to X-API-Key — this is the cluster's "cookie-first, key-fallback" rule.
The wrangler setup steps live in the repo
README.md. Placeholders only — never commit real cookie values,ex_access/ex_org/logto_sessionvalues, or API keys to this repo.
Deployed implementation: worker/ in this repo (explee-proxy) is exactly this Worker — it gates
inbound calls on X-Proxy-Token, then injects the KV cookies and falls back to the key. Point Explee
calls at the proxy origin instead of api.explee.com; see worker/README.md.
X-API-Key.explee-api-core.