cloudflare-guide
Use this skill when the user asks about "Cloudflare Workers", "Cloudflare Pages", "Wrangler configuration", "R2", "D1", "KV", "Durable Objects", "Workers AI", or any Cloudflare deployment/development question. It uses the cloudflare-docs-fetcher agent to fetch official documentation, keeping the main context clean.
What this skill does
# Cloudflare Development Assistant ## Core Principle **Use the `cloudflare-docs-fetcher` agent to fetch and analyze official Cloudflare documentation.** This keeps the main conversation context clean while ensuring answers are based on the latest official documentation. ## How to Use When a user asks a Cloudflare-related question, spawn the `cloudflare-docs-fetcher` agent: ``` Task( subagent_type: "general-purpose", description: "Fetch Cloudflare docs for [brief topic]", prompt: "User question: [THE EXACT USER QUESTION]" ) ``` The agent will: 1. Determine which official docs URL to fetch 2. Fetch and analyze the documentation 3. Return a concise answer with exact syntax from the docs ## When to Trigger Trigger this skill when the user mentions: - **Workers**: runtime, handlers, bindings, Wrangler - **Pages**: deployment, build config, Pages Functions - **Storage**: R2, D1, KV, Durable Objects, Queues - **AI**: Workers AI, AI Gateway, Agents SDK, Vectorize - **Config**: `wrangler.toml`, `wrangler.jsonc`, compatibility flags - **Deployment**: `wrangler deploy`, `wrangler dev`, environments ## Quick Commands (No Fetch Needed) These common commands don't require documentation lookup: ```bash # Create new project npm create cloudflare@latest # Local development npx wrangler dev # Deploy npx wrangler deploy # Workers npx wrangler pages deploy # Pages # Manage secrets npx wrangler secret put <KEY> # D1 database npx wrangler d1 create <NAME> npx wrangler d1 execute <DB> --command "SQL" # KV namespace npx wrangler kv:namespace create <NAME> # R2 bucket npx wrangler r2 bucket create <NAME> ``` ## Example Interaction **User**: "How do I add a D1 database binding to my Worker?" **Your action**: ``` Task( subagent_type: "general-purpose", description: "Fetch D1 binding docs", prompt: "User question: How do I add a D1 database binding to my Worker?" ) ``` **Agent returns** (concise answer with exact wrangler.toml syntax) **You**: Provide the answer to the user, citing the official source. ## What NOT to Do 1. ❌ **Don't WebFetch in main process** - Use the agent to keep context clean 2. ❌ **Don't guess config syntax** - Let the agent fetch current docs 3. ❌ **Don't skip for "simple" questions** - Cloudflare APIs change frequently ## Additional Resources - **`../agents/cloudflare-docs-fetcher.md`** - The agent that fetches official docs - **`references/official-sources.md`** - Complete URL index
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.