cloudflare cloudflare-docs
OFFICIALLABSCO SUMMARY
contributing is the entry point for that work: it routes a writer to the right reference for the task in front of them rather than holding the rules itself. eli5 rewrites dense technical text into plainer explanations for use inside those docs. pr covers this repository's branch naming, title conventions, and PR body structure. The remaining four — dependabot-review, reconcile-code-review, spam-and-off-topic-filter, and style-guide-review — are pieces of Cloudflare's automated review pipeline: they check whether a bumped dependency needs action beyond merging, reconcile a specialist's findings against prior review comments, triage incoming issues and PRs for spam, and lint changed MDX files against the docs style guide.
If you came here to build something of your own rather than to contribute documentation, only one skill applies to you: 2026-deprecation walks a Sandbox SDK codebase through Cloudflare's June 2026 deprecations — deprecated transports, exposePort, default sessions, and the stream-specific file and command APIs — with the exact rg search to find affected code and the sequence of API swaps to make.
READ THE FULL ANALYSIS
Several of the review skills are not standalone. dependabot-review's own instructions open with "you are running as a Cloudflare Worker with no shell access" and call tools named get_pr_context and get_npm_package_info that exist only inside Cloudflare's bot infrastructure. reconcile-code-review and spam-and-off-topic-filter are the same shape: both work only on data — a findings list, a fetched issue — that Cloudflare's own automation hands them as input. Install any of these three outside that pipeline and there is nothing for them to act on.
The rest need real local setup. workers-code-review reads type definitions straight out of node_modules/wrangler and node_modules/@cloudflare/workers-types, so it only works from inside a checkout with those installed. contributing expects pnpm run check to exist. pr needs an authenticated GitHub CLI or equivalent integration already configured.
Checked 16 September 2026, against each skill's own instructions rather than against Cloudflare's actual bot deployment, which we have not observed running.
ALSO IN THIS PACKAGE
docs
ALWAYS use this when writing docs
WHAT'S INSIDE
4 showing · 4 totalNothing else to set up — install it and go.
contributing
Cloudflare's documentation repository keeps a separate rulebook for each kind of change; this is the index that points at the right one and names the checks to run before you finish.
eli5
Rewrites a technical page in plain language for readers who don't already know the subject, without changing any of the facts.
pr
Writes and maintains the description of a proposed change to Cloudflare's documentation, in the shape the project's reviewers expect to read.
workers-code-review
A code review for Cloudflare Workers that checks every API call and config field against the versions actually installed in the project, not against half-remembered older ones.
HOW TO GET IT
npx skills add cloudflare/cloudflare-docsnpx skills add cloudflare/cloudflare-docs --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.