Cloudflare Workers Bindings
This skill should be used when the user asks about "KV namespace", "R2 bucket", "D1 database", "Hyperdrive", "create binding", "list workers", "worker code", "storage binding", "database query", "object storage", "key-value store", "connection pooling", or needs to manage Cloudflare Workers storage and compute resources.
What this skill does
# Cloudflare Workers Bindings Manage Cloudflare Workers storage and compute bindings using the Workers Bindings MCP server. ## Available Tools ### Account Management | Tool | Purpose | |------|---------| | `accounts_list` | List all accounts | | `set_active_account` | Set the active account for subsequent operations | ### Workers | Tool | Purpose | |------|---------| | `workers_list` | List all Workers in the account | | `workers_get_worker` | Get Worker details | | `workers_get_worker_code` | Retrieve Worker source code | ### KV Namespaces | Tool | Purpose | |------|---------| | `kv_namespaces_list` | List all KV namespaces | | `kv_namespace_create` | Create a new KV namespace | | `kv_namespace_get` | Get namespace details | | `kv_namespace_update` | Update namespace settings | | `kv_namespace_delete` | Delete a namespace | ### R2 Buckets | Tool | Purpose | |------|---------| | `r2_buckets_list` | List all R2 buckets | | `r2_bucket_create` | Create a new bucket | | `r2_bucket_get` | Get bucket details | | `r2_bucket_delete` | Delete a bucket | ### D1 Databases | Tool | Purpose | |------|---------| | `d1_databases_list` | List all D1 databases | | `d1_database_create` | Create a new database | | `d1_database_get` | Get database details | | `d1_database_query` | Execute SQL queries | | `d1_database_delete` | Delete a database | ### Hyperdrive | Tool | Purpose | |------|---------| | `hyperdrive_configs_list` | List Hyperdrive configurations | | `hyperdrive_config_create` | Create new config | | `hyperdrive_config_get` | Get config details | | `hyperdrive_config_edit` | Modify config | | `hyperdrive_config_delete` | Delete config | ## Common Workflows ### Set Up Account First Always start by setting the active account: 1. Use `accounts_list` to see available accounts 2. Use `set_active_account` with the desired account ID ### Create Storage Binding 1. Create the resource (`kv_namespace_create`, `r2_bucket_create`, or `d1_database_create`) 2. Note the resource ID returned 3. Add binding to wrangler.toml (manual step) ### Inspect Worker 1. Use `workers_list` to find the worker 2. Use `workers_get_worker` for metadata 3. Use `workers_get_worker_code` to review source ### Query D1 Database 1. Use `d1_databases_list` to find database ID 2. Use `d1_database_query` with SQL statement ## Tips - Always set the active account before other operations - Resource creation returns IDs needed for wrangler.toml bindings - D1 queries support standard SQLite syntax - R2 is S3-compatible for object operations
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.