SkillHub ClubWrite Technical DocsFull StackBackendDevOps

cloudflare-docs

This skill should be used when the user asks about "Cloudflare", "Workers", "Pages", "R2", "D1", "KV", "Durable Objects", "Queues", "Vectorize", "AI Gateway", "Hyperdrive", "Cloudflare API", "Wrangler", "Cloudflare documentation", "how to deploy to Cloudflare", "Cloudflare best practices", "Cloudflare pricing", "Cloudflare limits".

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C2.2

Composite score

2.2

Best-practice grade

C61.2

Install command

npx @skill-hub/cli install florinpopacodes-claude-marketplace-cloudflare-docs

Repository

FlorinPopaCodes/claude-marketplace

Skill path: plugins/cloudflare-toolkit/skills/cloudflare-docs

Open repository

Best for

Primary workflow: Write Technical Docs.

Technical facets: Full Stack, Backend, DevOps, Data / AI, Tech Writer.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: FlorinPopaCodes.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install cloudflare-docs into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/FlorinPopaCodes/claude-marketplace before adding cloudflare-docs to shared team environments
Use cloudflare-docs for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: Cloudflare Documentation Search
description: This skill should be used when the user asks about "Cloudflare", "Workers", "Pages", "R2", "D1", "KV", "Durable Objects", "Queues", "Vectorize", "AI Gateway", "Hyperdrive", "Cloudflare API", "Wrangler", "Cloudflare documentation", "how to deploy to Cloudflare", "Cloudflare best practices", "Cloudflare pricing", "Cloudflare limits".
version: 1.0.0
---

# Cloudflare Documentation Search

Use the `search_cloudflare_documentation` MCP tool for semantic search across Cloudflare's official documentation.

## Tool Reference

**Tool:** `search_cloudflare_documentation`
**Server:** cloudflare-docs
**Input:** Natural language query
**Output:** Relevant documentation snippets

## When to Use

- Answering questions about Cloudflare services
- Looking up API references and configuration options
- Finding deployment guides and tutorials
- Checking pricing, limits, or specifications

## Query Patterns

| Use Case | Pattern | Example |
|----------|---------|---------|
| API reference | "[service] [operation] API" | "Workers fetch API headers" |
| Configuration | "how to configure [feature] in [service]" | "how to configure caching in Workers" |
| Limits/pricing | "[service] limits" or "[service] pricing" | "R2 storage limits" |
| Troubleshooting | "[service] [specific issue]" | "Workers timeout exceeded error" |
| Integration | "[service A] with [service B]" | "Workers with D1 database" |
| Migration | "migrate from [source] to [Cloudflare service]" | "migrate from S3 to R2" |

## Product Reference

| Product | Purpose | Common Topics |
|---------|---------|---------------|
| **Workers** | Serverless compute | Runtime APIs, bindings, limits, deployment |
| **Pages** | Static site hosting | Build config, functions, custom domains |
| **R2** | Object storage | API, pricing, lifecycle, S3 compatibility |
| **D1** | SQL database | SQL syntax, bindings, backups, limits |
| **KV** | Key-value store | API, consistency, limits, pricing |
| **Durable Objects** | Stateful coordination | Alarms, websockets, storage |
| **Queues** | Message queues | Producers, consumers, batching |
| **Vectorize** | Vector database | Indexes, queries, embeddings |
| **AI Gateway** | AI proxy | Caching, rate limiting, logging |
| **Hyperdrive** | Database connector | Connection pooling, supported DBs |
| **Wrangler** | CLI tool | Commands, config, deployment |

## Tips

1. Be specific - include the product name and feature
2. For complex questions, search multiple times with focused queries
3. Include exact error messages when troubleshooting