More screenshots
Works with the AI Agents you already use
Repair Cloudflare Worker KV Stale Config Rollout
Reconcile stale Worker KV configuration across edge locations
$1
Repair Cloudflare Worker KV Stale Config Rollout
Example session with this skill installed
A feature switch remains inconsistent after a Worker deployment.
Available evidence: KV version snapshots (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 cloudflare worker
Repair Cloudflare Worker KV Stale Config Rollout — EVIDENCE-LIMITED REVIEW
Scenario received
A feature switch remains inconsistent after a Worker deployment.
Source register
- S1: KV version snapshots — 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
- compare config propagation and cache max-age — PRELIMINARY, NOT VERIFIED.
- validate safe fallback and update checks — 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
- kv version snapshots evidence map: DRAFT / INCOMPLETE until evidence is validated.
- stale config exception register: DRAFT / INCOMPLETE until evidence is validated.
- consistent edge 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 Cloudflare Worker KV Stale Config Rollout is a ToolForge Labs Cursor Skill workflow. Reconcile stale Worker KV configuration across edge locations.
What this skill checks
- compare config propagation and cache max-age.
- validate safe fallback and update checks.
- crosscheck source timestamps identifiers and changed versions.
- record exceptions and reversible verification gates.
What to provide
- KV version snapshots.
- state and configuration snapshot.
- error and recovery logs.
- deployment and alert timeline.
Deliverables
- kv version snapshots evidence map.
- stale config exception register.
- consistent edge 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.