2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill ai-cloudflare- _meta.json477 B
- SKILL.md2.5 KB
Overview
This skill generates Cloudflare Workers configuration and code from plain English prompts. It produces wrangler.toml, Worker TypeScript/JavaScript files, and wiring for KV, R2, and other bindings so you can deploy edge functions quickly. Designed for one-command use with sensible defaults and common middleware patterns.
How this skill works
You provide a short description of the desired Worker; the tool outputs the project files including wrangler.toml, route configuration, and Worker source. It detects needed bindings (KV namespaces, R2 buckets, Durable Objects) and inserts correct bindings and environment handling. The generated code follows Cloudflare conventions and includes error handling, routing, and optional middleware like auth or caching.
When to use it
- Creating a new Cloudflare Worker from a feature description without writing boilerplate.
- Prototyping edge APIs, redirects, or caching strategies that require KV or R2.
- Adding auth, rate limiting, or middleware to an existing edge-experience quickly.
- Learning Cloudflare Workers with working, deployable examples.
- Preparing deployments that require correct wrangler.toml and runtime bindings.
Best practices
- Keep Workers small and focused to stay within edge size and performance limits.
- Use KV for read-heavy data and R2 for large object storage; prefer Durable Objects for consistency-critical state.
- Explicitly handle errors and edge cases; include clear logging for local testing.
- Test locally with wrangler dev before deploying to production.
- Treat environment secrets carefully and avoid committing them to source control.
Example use cases
- API proxy with rate limiting and per-user KV counters for throttling.
- Geolocation-based redirects that route users to country-specific sites.
- REST API storing user preferences in KV and serving cached responses at the edge.
- Edge caching layer that caches upstream responses for a configurable TTL.
- JWT authentication middleware applied to selected API routes with secret binding.
FAQ
No install is required; run via npx. Node.js 18+ is recommended and an OPENAI_API_KEY environment variable is needed for generation.
Will it create bindings for KV, R2, or Durable Objects automatically?
Yes. Based on your description it will include the appropriate bindings in wrangler.toml and reference them in the generated Worker code.