
Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing). Use when building email sending (Workers binding or REST API), email routing, Agents SDK email handling, or integrating email into any app — Workers, Node.js, Python, Go, etc. Also use for email deliverability, SPF/DKIM/DMARC, wrangler email setup, MCP email tools, or when a coding agent needs to send emails. Even for simple requests like "add email to my Worker" — this skill has critical config details.
Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable execution, queues, retries, observability, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Review and validate implementation quality — catch workarounds, simulated data, incomplete implementations, and shortcuts. Use when checking if a feature is genuinely working end-to-end.
Master advanced Swift language features: macros, concurrency, generics, networking, testing. Use when working with Swift macros, async/await patterns, protocol design, or optimizing for performance. See swift-ui for SwiftUI-specific patterns.
Cloudflare Durable Objects: stateful workflows, WebSockets, coordination, rate limiting, alarm scheduling. Use when building stateful services on Cloudflare.
Cloudflare Workers fundamentals: module exports, request handling, environment bindings, Wrangler config, multi-environment setup. Use when building serverless edge functions on Cloudflare.
Analyze technical options with structured comparison matrices, scoring, and ADR draft generation. Use when the user needs help choosing between technologies, architectures, or implementation approaches.
Developer inquiry skill for technical investigation, validation, and decision-making. Use when exploring unfamiliar technology, validating approaches with spikes, comparing options, or making architecture decisions. Covers the full thinking process from "I don't know" to confident decision.
Quick morning orientation — surface ClickUp tasks, carry-overs, project gaps, and intensity patterns. Use when starting the workday.
End-of-day capture — ClickUp completion check, uncommitted work, intensity, tomorrow's frog. Use when closing out the workday.
Finalize the weekly plan after reviewing and acting on decisions in ClickUp. Use when the draft weekly plan has been reviewed and is ready to lock.
Define the what and why for a piece of work — objective, success criteria, materials table, and context. The foundational Score document before any spec is written.
SwiftUI implementation patterns for building polished iOS/macOS apps. Use when building views, managing state, creating layouts, implementing animations, or structuring app architecture in SwiftUI.
Review SwiftUI apps for App Store submission readiness — guidelines compliance, code quality, metadata, and testing coverage. Use when preparing to submit iOS/macOS apps, checking App Store metadata, verifying accessibility, or addressing previous rejections.
Clean, human-sounding prose style guide that bans common LLM clichés, filler phrases, dramatic language, and vague vocabulary. Use when writing articles, documentation, blog posts, or any prose that should sound human and direct.
Provide yoga anatomy expertise — biomechanics, contraindications, modifications, and anatomical rationale behind postures. Use when a teacher needs safety guidance or modification options for poses.
Design yoga sequences — class structures, pose progressions, and balanced practices. Use when building a yoga class sequence or evaluating pose flow.
Coordinate yoga class planning by routing queries to specialist skills and synthesizing responses. Use when planning a yoga class, building sequences, or researching poses.
Craft yoga teaching narratives, verbal cues, and thematic arcs that connect poses to meaningful intention. Use when developing the storytelling layer of a yoga class.
Review a completed implementation branch against its spec and acceptance criteria — catch gaps, shortcuts, and quality issues before merge.
Execute an approved spec — create a branch, work through each step, commit progress, and mark complete.
Generate an execution spec from an approved PRD — define approach, steps, deliverables, acceptance criteria, and risks.
Ensure every .orchestra/work/ item has a corresponding ClickUp ticket. Creates missing tickets and writes the ID back into the PRD frontmatter. Use when backfilling a repo's work items into ClickUp.
Write the engineer's journal — session logs, narrative progress notes, and git journals that capture the story behind the commits. The programme notes for whoever works here next.
Evaluate yoga teaching readiness through scenarios, knowledge probes, and guided learning exercises. Use when a teacher wants to test their understanding or prepare for a class.
Review milestones and project progress — diff materials table against repo state, surface gaps, check for orphaned work items, and propose next actions.
Draft the start-of-week plan — project triage, load calculation, and priority setting. Use when beginning a new work week.
Run a review at weekly, monthly, quarterly, or yearly zoom — synthesize notes, surface patterns, generate retrospective. Use when running periodic reviews.
Capture a quick timestamped thought as a knote. Use when logging a thought, observation, decision, or anything worth capturing mid-day.
Audit plugin skills and agents for compliance with Claude Code best practices — checks frontmatter, descriptions, tool restrictions, structure, and naming. Use when improving plugin quality or before publishing.
Cloudflare Workers fundamentals: module exports, request handling, environment bindings, Wrangler config, multi-environment setup. Use when building serverless edge functions on Cloudflare.
Cloudflare Workers AI: edge model inference, text generation, summarization, streaming responses. Use when integrating AI models into Cloudflare Workers.
Cloudflare KV storage: caching, key-value operations, TTL, namespace management. Use when implementing caching or edge storage on Cloudflare Workers.
Hono framework patterns for Cloudflare Workers: routing, middleware, type-safe handlers, request validation, error handling. Use when building APIs with Hono on Cloudflare.
Cloudflare Durable Objects: stateful workflows, WebSockets, coordination, rate limiting, alarm scheduling. Use when building stateful services on Cloudflare.
Cloudflare Workers AI: edge model inference, text generation, summarization, streaming responses. Use when integrating AI models into Cloudflare Workers.
Hono framework patterns for Cloudflare Workers: routing, middleware, type-safe handlers, request validation, error handling. Use when building APIs with Hono on Cloudflare.
Cloudflare KV storage: caching, key-value operations, TTL, namespace management. Use when implementing caching or edge storage on Cloudflare Workers.
Generate Playwright E2E tests by exploring websites and automating browser interactions. Use when the user wants to generate Playwright tests by exploring a website, or needs browser automation.
Capture a work ticket as the starting point for the orchestra loop — read a brief, scaffold the work item folder, and set up for PRD and spec.
Grade the outputs of an orchestra skill run against its eval assertions — reads produced files, checks each assertion, and writes a grading report.
Bootstrap or manage the .orchestra/roadmap.md — interactive project setup when no roadmap exists, or status/update/add commands when one does.
Scaffold the .orchestra/ agent knowledge base in a project — creates folder structure, templates, README, and ADR-000.
Capture an architectural decision record — document a decision that was made during work, why it was made, and its consequences.
Planning conductor — runs the full PRD → Spec → Gherkin loop in a single interactive session with human approval gates.
Generate Gherkin scenarios from an orchestra PRD or spec — produces Feature/Scenario blocks in fenced gherkin markdown.
Generate UML diagrams as Mermaid code and save them to .orchestra/uml/. Supports sequence, class, deployment, component, and state diagram types.
Explain what Orchestra is — a software development lifecycle encoded for agents, its SDLC roots, the pipeline, roles, file structure, status vocabulary, and skill index.
Merge a reviewed implementation branch into main — resolve conflicts, close the work item, and clean up the branch.