REPO PACKAGE
cloudflare workerd
OFFICIAL17skills
12ready to use
LABSCO SUMMARY
Most of what we can see a description for is process for this one codebase: bazel-test-hygiene and find-and-run-tests cover the actual bazel/wd-test/kj_test build-and-test machinery and its wd-test-format skill documents the config format those tests use; kj-style, rust-review, and ts-style are per-language review checklists for the C++, Rust (CXX FFI, JSG conventions), and TypeScript in this repo; workerd-api-review and workerd-safety-review add API-compatibility and memory/thread-safety checklists on top of those; and update-v8 walks through rebasing patches and integrity hashes for a V8 version bump.
A second group is generic team process rather than workerd-specific: identify-reviewer, pr-review-guide, and receiving-code-review govern how a PR review is given and received, commit-categories and markdown-drafts standardize changelog wording and external draft formatting, investigation-notes is a scratch-tracking template for bug hunts, and parent-project-skills bootstraps extra context when workerd is checked out as a submodule of a larger project.
READ THE FULL ANALYSIS
One skill has nothing to do with engineering. dad-jokes tells the agent to "deliver a dad joke to lighten the mood" after any task of more than about five tool calls, and instructs it never to improvise a joke without loading the skill first -- a small, honest sign that this is a real team's working setup copied in as-is, not content assembled for a reader here.
The README says nothing about any of this. workerd's own README is a runtime README -- build instructions across Bazel, clang, and Xcode, a sample Cap'n Proto config, and production deployment notes under systemd -- with no mention of Claude, skills, or agent workflows anywhere in it.
WHAT'S INSIDE
17 showing · 17 totalReady to use
Nothing else to set up — install it and go.
17 of 17
SETUP
Showing all 17 skills
bazel-test-hygiene
Keeps a green test run from being false comfort — when it says everything passed, the tests really did run, on the code you just changed, and a regression test really would have caught the bug.
commit-categories
The workerd project's own table of changelog sections and the folders that map to each one, so two people writing release notes sort the same commit the same way.
dad-jokes
Exactly one joke, pun, or limerick when a long slog finally ends — never a comedy set, never explained afterwards, and skipped entirely when the mood is tense.
find-and-run-tests
You find the exact bazel target for a test — and the right flags to build, run, and debug it — even when you don't know its precise name.
identify-reviewer
A code review that knows which of the comments and commits it is reading are yours, and talks to you about them directly instead of about you in the third person.
investigation-notes
You keep one scratch document that tracks your current focus, hypotheses, code you've already read, and test results during a bug hunt, so you never re-derive the same conclusion twice.
kj-style
How the workerd project writes its C++ — what things are named, how memory and errors are handled, how it is all laid out — so a new change looks like the code already around it.
markdown-drafts
Anything written to be pasted somewhere else — a GitHub issue, a Jira ticket, a wiki page — comes back with its formatting marks still visible instead of already flattened by the chat window.
parent-project-skills
The workerd code is open source, but it often sits inside a company's private repository — this picks up the extra instructions kept there, and keeps anything private from leaking back into the public code.
pr-review-guide
A blunt style of code review: every point tied to a line you can actually see, nothing said just to be polite, and the author told up front that an AI wrote it.
receiving-code-review
You respond to code review feedback with verification and technical reasoning instead of reflexive agreement or blind implementation.
rust-review
The checklist workerd uses to review its Rust code — especially where Rust calls into C++, where the usual safety guarantees stop applying, and where objects get handed to JavaScript.
ts-style
House rules for the JavaScript and TypeScript inside workerd, Cloudflare's Workers runtime — the conventions a change is held to when someone reviews it.
update-v8
Moving workerd onto a newer version of Google's V8 JavaScript engine is a long chore that is easy to get wrong; this walks the whole upgrade through step by step and stops for a human before anything irreversible.
wd-test-format
Every workerd test is described by a small configuration file in the project's own format, and this is how to write one — what the test loads, what it is allowed to reach, and which behaviour flags it turns on.
workerd-api-review
The four questions a change to workerd's APIs has to survive in review: is it fast, does it keep existing code working, is it safe, and does it match the web standard it claims to implement.
workerd-safety-review
Bugs in workerd's C++ are the kind that crash a server or corrupt memory; this is the checklist a reviewer walks every C++ change through — lifetimes, threads, and the seam where the JavaScript engine meets the C++ side.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (17 skills)
npx skills add cloudflare/workerdSINGLE SKILLOr install a single skill
npx skills add cloudflare/workerd --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.