| 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. |
Explee Auth (Cookie & KV)
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.
Operating Rules
- Never hardcode cookies in files. Treat cookies as sensitive credentials; obtain them from
the user (or read them from KV — see below) for the current session.
- Use
Cookie: header authentication. Include the cookie string exactly as issued:
Cookie: <name1>=<...>; <name2>=<...>; ...
- Don't confuse URL tracking params with cookies. Query params like
_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.
- Discover endpoints from docs first (
https://api.explee.com/public/api/docs) and confirm
assumptions before any mutating request.
- Safe progression: test auth on a read-only endpoint first, then perform the operation.
- Be explicit in outputs: report method, endpoint, status, and a summarized response. If
unauthorized, ask for (or refresh) credentials.
Cookie templates
Use the four templates in explee-api-core (T1–T4), but swap the auth header:
