---
skill_id: gf-po-kv-binding-checks
evaluation: free
quality: agent-decision-grade
functional: true
price_usd_full: 5.49
price_label: $5.49 / unlock
kind: good
category: Coding
challenge: https://lvlltd.com/api/pay?skill=gf-po-kv-binding-checks
outline: https://lvlltd.com/skills/gf-po-kv-binding-checks/outline.json
runtime_after_unlock: src/index.js createSkill
standards: x402, ERC-7857
completion_pass: functional-v1
---

# Free sample — KV Binding Checks

**Skill ID:** `gf-po-kv-binding-checks`  
**Unlock:** $5.49 / unlock USDC on Base via x402  
**What you get after pay:** runnable sealed pack (`createSkill().run`) + workbook + templates  

## Summary

Cloudflare KV and binding parity checks for Workers and Pages Functions across preview, staging, and production.

Catch missing KV namespaces, wrong binding names, and preview-only secrets before production routes read undefined. Includes parity matrices and smoke assertions. Free outline; sealed x402 unlock. Not legal advice; no uptime guarantees.

## When to use

- Preview deploys succeed while production Functions throw because a KV binding name drifted between wrangler.toml and the dashboard.
- You promote Pages Functions with catalog or rate-limit state in KV and need a binding presence check in CI.
- Multiple environments share similar names and you need a matrix that proves each binding points at the intended namespace.

## Decision-grade outline (free)

1. Enumerate required bindings per environment: KV namespaces, R2, D1, Queues, and secrets presence flags without dumping secret values.
2. Build a parity matrix comparing wrangler config, dashboard bindings, and CI deploy vars for name, namespace ID, and read/write intent.
3. Add smoke assertions: put/get a canary key, verify TTL behavior, and confirm isolation between preview and production namespaces.
4. Flag dangerous patterns: shared prod namespace in preview, missing binding on only one branch, and silent fallbacks that mask failures.
5. Ship a pre-promote gate script checklist operators run before Pages or Workers cutover with fail-closed criteria.

## Capabilities

- Environment binding inventory template for KV, R2, D1, and Queues
- Config-vs-dashboard parity matrix that highlights name and ID drift
- Canary put/get smoke patterns that prove namespace isolation
- Dangerous-pattern detector notes for shared-prod and silent fallbacks
- Pre-promote fail-closed gate checklist for Functions cutovers

## Artifacts after unlock

- `kv-binding-parity-matrix.csv`
- `binding-smoke-assertions.md`
- `pre-promote-binding-gate.md`

## Detailed description

Binding drift is a quiet production killer on Cloudflare. A Workers or Pages Function that reads a KV namespace named CATALOG in preview may ship to production where the binding is still catalog_kv—or worse, preview and production share one namespace and test keys pollute live rate-limit counters. KV Binding Checks is a coding-side reliability good that forces parity before promote. You inventory required bindings per environment: KV, R2, D1, Queues, and secret presence flags (never values). The parity matrix lines up wrangler config, dashboard bindings, and CI variables so name, namespace ID, and intended access mode are explicit. Smoke assertions write and read a canary key, verify TTL where relevant, and prove preview cannot see production keys. Dangerous patterns get called out: shared production namespaces in preview, bindings present on main but missing on the release branch, and catch blocks that swallow missing binding errors into empty catalogs. The pre-promote gate is fail-closed—no green check, no cutover. A free outline is on the listing; the sealed pack unlocks via x402 Base USDC. Operational and coding guidance only—not legal advice, not a Cloudflare partnership, and no guarantees of zero outages or commercial results. Use it so every environment that claims a binding can prove it at gate time.

## Functional runtime (paid)

After verified payment the sealed pack includes:

| Path | Role |
|------|------|
| `src/index.js` | `createSkill`, `run`, `plan`, `checklist` |
| `src/runbook.js` | Outline-driven steps with done_when |
| `src/tools.js` | Tool schemas for agent registries |
| `WORKBOOK.md` | Human/operator procedure |
| `templates/` | Checklist + artifact shells |
| `schemas/output.schema.json` | Result contract |

### Agent snippet (after unlock)

```js
import { createSkill } from "./src/index.js";
const skill = createSkill({ tenantId: "ops", agentId: "buyer" });
const result = await skill.run({
  goal: "Execute KV Binding Checks for my catalog",
  context: { skill_id: "gf-po-kv-binding-checks" },
  dry_run: false,
});
// result.ok, result.steps, result.artifacts
```

## Pay path

1. Free: this sample + outline.json  
2. `GET https://lvlltd.com/api/pay?skill=gf-po-kv-binding-checks` → HTTP 402  
3. Transfer `maxAmountRequired` USDC to `payTo` on Base  
4. `POST /api/pay` with `X-PAYMENT: {"txHash":"0x…","skill":"gf-po-kv-binding-checks"}`  
5. Write `sealed_pack.files` to disk or use install-unlocked-pack.mjs  
6. Re-redeem anytime with the same verified txHash  

## Honesty

- No revenue, conversion, or uptime guarantees  
- Not legal, tax, medical, or investment advice  
- Crypto transfers are irreversible  
- Confirmed unlocks only for proof strips (/api/proof)  

*Public `/sealed/gf-po-kv-binding-checks/` is teaser-only. Full `src/` is paywalled under locked sealed delivery.*
