plugins/cloudflare/skills/kv/SKILL.md
Use this skill when the user asks about Cloudflare Workers KV, key-value storage on Cloudflare's edge, distributed KV stores, or managing KV namespaces with Pulumi.
npx skillsauth add nsheaps/ai-mktpl cloudflare-kvInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Workers KV is a global, low-latency key-value data store. It's eventually consistent with reads served from the nearest edge location.
cloudflare.WorkersKvNamespace (docs)export default {
async fetch(request: Request, env: Env): Promise<Response> {
await env.MY_KV.put("key", "value", { expirationTtl: 3600 });
const value = await env.MY_KV.get("key");
return new Response(value);
},
};
[[kv_namespaces]]
binding = "MY_KV"
id = "xxxx"
import * as cloudflare from "@pulumi/cloudflare";
const kv = new cloudflare.WorkersKvNamespace("my-kv", {
accountId,
title: "my-kv-namespace",
});
export const kvNamespaceId = kv.id;
| Resource | Free | Paid | | -------- | -------- | -------------- | | Reads | 100K/day | $0.50/M | | Writes | 1K/day | $5.00/M | | Deletes | 1K/day | $5.00/M | | Lists | 1K/day | $5.00/M | | Storage | 1 GB | $0.50/GB/month |
tools
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
tools
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
tools
Manages spec files for requirements capture and validation
tools
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su