Menu
Sweep stale extension caches before activation, then fall back to a sticky manual-refresh flag if the live refresh fails.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Collapse multiple change sources into one caller-facing boolean so headless bootstraps know whether a downstream refresh is necessary.
After awaiting persistence work, update the shared budget state for each `tool_use_id` exactly once so no concurrent reader ever sees a half-committed decision.
Issue continuation nudges while the turn stays under budget, then halt once diminishing returns or the budget cap justify stopping.
Lazily extract referenced files for bundled skills so large prompts stay offline until needed.
Persist a cache-safe stop-hook context snapshot only for main session queries so later helpers can resume from stable state without fork pollution.
Warm the authoritative cache path first, then fan out cache-only readers in parallel so derived loaders never race stale state.
| name | cache-sweep-activation-fallback |
| description | Sweep stale extension caches before activation, then fall back to a sticky manual-refresh flag if the live refresh fails. |
| metadata | {"author":"ychampion"} |
Domain: extensions-mcp
Trigger: Apply when newly materialized extension sources must be activated immediately, but the live refresh can fail and needs a recoverable fallback.
Source Pattern: Distilled from reviewed extension lifecycle and source-reconciliation patterns.
Treat installation and activation as separate phases. After a background reconcile changes what is on disk, clear the marketplace cache, attempt a full activation refresh, and degrade gracefully if that refresh throws. The fallback path should clear plugin caches again, log the failure, and set a sticky manual-refresh bit so the system admits that runtime state is stale instead of pretending activation succeeded.
If a background extension installer clones a new command marketplace during startup, clear the source cache, try a full runtime reload, and if the reload fails mark the UI with a single “reload extensions” prompt while preserving the newly cloned files for recovery.
