More screenshots
Works with the AI Agents you already use
Repair Next.js Edge Cache Cookie Variant Mixup
Fix edge-cache response crossover between session cookie variants
$1
Repair Next.js Edge Cache Cookie Variant Mixup
Example session with this skill installed
Anonymous cache entries appear under signed-in personalized routes.
Available evidence: edge cache headers (partial). Additional evidence requested: state and configuration snapshot, error and recovery logs, deployment and alert timeline. Review the case, identify open evidence gaps, and do not invent a live test or production change.
- Read your context and instructions
- Compiled the repair next js
Repair Next.js Edge Cache Cookie Variant Mixup — EVIDENCE-LIMITED REVIEW
Scenario received
Anonymous cache entries appear under signed-in personalized routes.
Source register
- S1: edge cache headers — PARTIAL SOURCE PROVIDED.
- S2: state and configuration snapshot — NOT PROVIDED; REQUIRED TO VERIFY.
- S3: error and recovery logs — NOT PROVIDED; REQUIRED TO VERIFY.
- S4: deployment and alert timeline — NOT PROVIDED; REQUIRED TO VERIFY.
Concrete checks
- inspect cache keys and Vary header handling — PRELIMINARY, NOT VERIFIED.
- test authenticated and anonymous request variants — AWAITING CORROBORATING EVIDENCE.
- crosscheck source timestamps identifiers and changed versions — AWAITING CORROBORATING EVIDENCE.
- record exceptions and reversible verification gates — AWAITING CORROBORATING EVIDENCE.
Deliverables / acceptance gates
- edge cache headers evidence map: DRAFT / INCOMPLETE until evidence is validated.
- cache crossover exception register: DRAFT / INCOMPLETE until evidence is validated.
- isolated cache validation plan: DRAFT / INCOMPLETE until evidence is validated.
Decision
INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair Next.js Edge Cache Cookie Variant Mixup is a ToolForge Labs Cursor Skill workflow. Fix edge-cache response crossover between session cookie variants.
What this skill checks
- inspect cache keys and Vary header handling.
- test authenticated and anonymous request variants.
- crosscheck source timestamps identifiers and changed versions.
- record exceptions and reversible verification gates.
What to provide
- edge cache headers.
- state and configuration snapshot.
- error and recovery logs.
- deployment and alert timeline.
Deliverables
- edge cache headers evidence map.
- cache crossover exception register.
- isolated cache validation plan.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions and missing inputs; no unperformed live tests, external changes, or approvals are claimed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Cannot verify inaccessible environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 20 days ago
Permissions
Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.