plugins/cloudflare/skills/d1/SKILL.md
Use this skill when the user asks about Cloudflare D1, serverless SQL databases on Cloudflare, SQLite on the edge, or managing D1 databases with Pulumi.
npx skillsauth add nsheaps/ai-mktpl cloudflare-d1Install 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.
D1 is Cloudflare's serverless SQLite database. It runs on Cloudflare's edge with automatic read replication, point-in-time recovery, and native Worker bindings.
cloudflare.D1Database (docs)export default {
async fetch(request: Request, env: Env): Promise<Response> {
const { results } = await env.DB.prepare("SELECT * FROM users WHERE id = ?").bind(1).all();
return Response.json(results);
},
};
[[d1_databases]]
binding = "DB"
database_name = "my-database"
database_id = "xxxx-xxxx-xxxx"
# Create a database
npx wrangler d1 create my-database
# Run SQL
npx wrangler d1 execute my-database --command "CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)"
# Run migrations
npx wrangler d1 migrations apply my-database
import * as cloudflare from "@pulumi/cloudflare";
const db = new cloudflare.D1Database("my-database", {
accountId,
name: "my-database",
});
export const databaseId = db.id;
| Resource | Free | Paid | | ------------ | -------- | -------------- | | Rows read | 5M/day | $0.001/M | | Rows written | 100K/day | $1.00/M | | Storage | 5 GB | $0.75/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