More screenshots
Works with the AI Agents you already use
Repair Next.js ISR Cache Tag Invalidation Fanout
Diagnose stale ISR pages when cache tag invalidation fails to propagate between deploy replicas
$1
Repair Next.js ISR Cache Tag Invalidation Fanout
Example session with this skill installed
A price update invalidates the product tag but two edge nodes still serve an old price.
Available sources: revalidateTag calls, route cache settings (partial excerpts only). Additional evidence requested: deployment topology, stale response headers. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair next js
Repair Next.js ISR Cache Tag Invalidation Fanout — EVIDENCE-LIMITED REVIEW
Scenario received
A price update invalidates the product tag but two edge nodes still serve an old price.
Source register
- S1: revalidateTag calls — partial extract available.
- S2: route cache settings — partial extract available.
- S3: deployment topology — NOT PROVIDED; REQUIRED FOR VERIFICATION.
- S4: stale response headers — NOT PROVIDED; REQUIRED FOR VERIFICATION.
Concrete findings and verification
- trace tags from write to route — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
compare cache namespaces across replicas — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
3. identify race with regeneration — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
4.
propose targeted cache tests and fallback — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
Deliverables and review gates
- tag-to-route map: DRAFT ONLY; do not infer unsupported outcomes.
- stale-node evidence matrix: DRAFT ONLY; do not infer unsupported outcomes.
- safe invalidation fix: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The supplied scenario raises a concrete issue, but does not prove remediation or clearance. Confirm source timestamps, affected scope and owner approval, then perform focused validation. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair Next.js ISR Cache Tag Invalidation Fanout is a ToolForge Labs ChatGPT Skill workflow. Diagnose stale ISR pages when cache tag invalidation fails to propagate between deploy replicas.
What this skill checks
- trace tags from write to route.
- compare cache namespaces across replicas.
- identify race with regeneration.
- propose targeted cache tests and fallback.
What to provide
- revalidateTag calls.
- route cache settings.
- deployment topology.
- stale response headers.
Deliverables
- tag-to-route map.
- stale-node evidence matrix.
- safe invalidation fix.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions, reports missing inputs, and never claims an unperformed live test, compliance approval, or production change.
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 systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.
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 24 days ago
Permissions
Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.