AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Caching Revalidation

skill-m-binimran-dev-pack-caching-revalidation · by m-binimran

Get Next.js App Router caching right — static vs dynamic rendering, fetch cache, revalidatePath/revalidateTag, and ISR. Use when data is stale, a page won't update, or you're tuning performance vs freshness.

↗ Repository
— No reviews yet
0 installs
29 views
0.0% view→install

Install

$ agentstack add skill-m-binimran-dev-pack-caching-revalidation

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ● Network access Used
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-m-binimran-dev-pack-caching-revalidation)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Caching Revalidation? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

caching-revalidation

Next.js caches aggressively by default. Most "my data won't update" bugs are caching, not logic.

Decide freshness per route

  • Static (default where possible): marketing/content pages. Fast, cached at the edge.
  • ISR: mostly-static with periodic refresh — export const revalidate = 3600 (seconds).
  • Dynamic: per-request/user data — reads of cookies/headers/searchParams, or export const dynamic = 'force-dynamic'.

Invalidate on write

  • After a mutation (server action/route handler) that changes displayed data, call revalidatePath('/path')

or revalidateTag('tag') so caches refresh. Tag fetches you'll need to bust: fetch(url, { next: { tags: ['projects'] } }).

  • For user-specific/never-cache reads, opt out: fetch(url, { cache: 'no-store' }).

Common fixes

  • "Stale after save" → you mutated but didn't revalidatePath/Tag.
  • "User sees another user's data" → a per-user route got statically cached; make it dynamic.
  • "Slow every load" → over-using no-store; cache + revalidate instead.

Output

  • Per affected route: static / ISR / dynamic, plus the revalidation call wired to each mutation.

Guardrails

  • Never cache per-user/authenticated data at a shared layer.
  • Don't blanket force-dynamic to "fix" caching — target the actual route.
  • Verify freshness by actually triggering the mutation and reloading (don't assume).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Databases