code-review
Reviews Workers and Cloudflare Developer Platform code for type correctness, API usage, and configuration validity. Load when reviewing TypeScript/JavaScript using Workers APIs, wrangler.jsonc/toml config, or Cloudflare bindings (KV, R2, D1, Durable Objects, Queues, Vectorize, AI, Hyperdrive).
90
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (Cloudflare Workers/Developer Platform code review), lists specific actions (type correctness, API usage, configuration validity), and provides explicit trigger conditions with comprehensive keyword coverage. The enumeration of specific Cloudflare bindings ensures both accurate skill selection and clear distinctiveness from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'type correctness', 'API usage', and 'configuration validity' review. Also enumerates specific technologies and bindings (KV, R2, D1, Durable Objects, Queues, Vectorize, AI, Hyperdrive). | 3 / 3 |
Completeness | Clearly answers both 'what' (reviews code for type correctness, API usage, configuration validity) and 'when' ('Load when reviewing TypeScript/JavaScript using Workers APIs, wrangler.jsonc/toml config, or Cloudflare bindings'). The 'Load when' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user or Claude would encounter: 'Workers', 'Cloudflare', 'TypeScript/JavaScript', 'wrangler.jsonc/toml', and a comprehensive list of Cloudflare bindings (KV, R2, D1, Durable Objects, Queues, Vectorize, AI, Hyperdrive). These are the exact terms developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Cloudflare Workers and Developer Platform specifically. The enumeration of Cloudflare-specific bindings and config formats (wrangler.jsonc/toml) makes it very unlikely to conflict with generic code review or other cloud platform skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured code review skill with clear workflows, concrete tooling commands, and domain-specific guidance that Claude would need for Cloudflare Workers reviews. Its main weakness is moderate verbosity in the anti-patterns and rules tables, where some explanations are redundant with Claude's existing knowledge, and the inability to verify referenced bundle files. The categorization framework (Illustrative/Demonstrative/Executable) and risk assessment tiers are particularly effective for guiding review depth.
Suggestions
Trim the 'Why it matters' column in the anti-patterns table — Claude understands why hardcoded secrets and `any` types are problematic; keep only Workers-specific rationale.
Consider moving the detailed anti-patterns and rules tables into a reference file and keeping only a compact checklist in the main SKILL.md to improve conciseness and progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured and avoids explaining basic concepts, but some tables are verbose and could be tightened. The anti-patterns table and rules table contain explanations Claude likely already knows (e.g., why hardcoded secrets are bad, why `any` defeats type safety). However, the Workers-specific guidance is domain-specific enough to justify most of the content. | 2 / 3 |
Actionability | The skill provides concrete, executable commands (`npx tsc --noEmit`, `npx eslint <files>`, `git log --oneline -5 -- <file>`), specific file paths to read for validation, exact patterns to flag with code examples, a clear output format with severity levels, and precise rules with code-level specificity (e.g., `env.X` vs `this.env.X`). | 3 / 3 |
Workflow Clarity | The 5-step review process is clearly sequenced (Build Context → Categorize → Validate with Tools → Check Against Rules → Assess Risk), with explicit validation steps (run tsc, eslint, validate against schema). The category table provides a decision framework, and the risk assessment provides clear escalation triggers. The output format enforces structured reporting. | 3 / 3 |
Progressive Disclosure | The skill references multiple external files (`references/workers-types.md`, `references/wrangler-config.md`, `references/common-patterns.md`) with clear signaling of what each contains, which is good structure. However, no bundle files were provided, so we cannot verify these references exist. Additionally, the quick-reference rules table duplicates content that presumably lives in those reference files, creating potential redundancy — the inline content could be trimmed if the references are comprehensive. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- cloudflare/cloudflare-docs
- Commit
9a170b9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.