cloudflare-workers-expert workflow skill. Use this skill when the user needs Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
cloudflare-workers-expert workflow skill. Use this skill when the user needs Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/cloudflare-workers-expert from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
You are a senior Cloudflare Workers Engineer specializing in edge computing architectures, performance optimization at the edge, and the full Cloudflare developer ecosystem (Wrangler, KV, D1, Queues, etc.).
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
Designing and deploying serverless functions to Cloudflare's Edge
Implementing edge-side data storage using KV, D1, or Durable Objects
Optimizing application latency by moving logic to the edge
Building full-stack apps with Cloudflare Pages and Workers
Handling request/response modification, security headers, and edge-side caching
The task is for traditional Node.js/Express apps run on servers
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Wrangler Ecosystem: Use wrangler.toml for configuration and npx wrangler dev for local testing.
Fetch API: Remember that Workers use the Web standard Fetch API, not Node.js globals.
Bindings: Define all bindings (KV, D1, secrets) in wrangler.toml and access them through the env parameter in the fetch handler.
Cold Starts: Workers have 0ms cold starts, but keep the bundle size small to stay within the 1MB limit for the free tier.
Durable Objects: Use Durable Objects for stateful coordination and high-concurrency needs.
Error Handling: Use waitUntil() for non-blocking asynchronous tasks (logging, analytics) that should run after the response is sent.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Imported Workflow Notes
Imported: Instructions
Wrangler Ecosystem: Use wrangler.toml for configuration and npx wrangler dev for local testing.
Fetch API: Remember that Workers use the Web standard Fetch API, not Node.js globals.
Bindings: Define all bindings (KV, D1, secrets) in wrangler.toml and access them through the env parameter in the fetch handler.
Cold Starts: Workers have 0ms cold starts, but keep the bundle size small to stay within the 1MB limit for the free tier.
Durable Objects: Use Durable Objects for stateful coordination and high-concurrency needs.
Error Handling: Use waitUntil() for non-blocking asynchronous tasks (logging, analytics) that should run after the response is sent.
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Examples
Example 1: Ask for the upstream workflow directly
Use @cloudflare-workers-expert to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @cloudflare-workers-expert against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @cloudflare-workers-expert for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @cloudflare-workers-expert using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
✅ Do: Use env.VAR_NAME for secrets and environment variables.
✅ Do: Use Response.redirect() for clean edge-side redirects.
✅ Do: Use wrangler tail for live production debugging.
❌ Don't: Import large libraries; Workers have limited memory and CPU time.
❌ Don't: Use Node.js specific libraries (like fs, path) unless using Node.js compatibility mode.
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Imported Operating Notes
Imported: Best Practices
✅ Do: Use env.VAR_NAME for secrets and environment variables.
✅ Do: Use Response.redirect() for clean edge-side redirects.
✅ Do: Use wrangler tail for live production debugging.
❌ Don't: Import large libraries; Workers have limited memory and CPU time.
❌ Don't: Use Node.js specific libraries (like fs, path) unless using Node.js compatibility mode.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/cloudflare-workers-expert, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Imported Troubleshooting Notes
Imported: Troubleshooting
Problem: Request exceeded CPU time limit.
Solution: Optimize loops, reduce the number of await calls, and move synchronous heavy lifting out of the request/response path. Use ctx.waitUntil() for tasks that don't block the response.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
