cloudflare
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task.
57
66%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/opencode/test/fixture/skills/cloudflare/SKILL.mdQuality
Discovery
82%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 description excels at enumerating specific Cloudflare services and technologies, providing excellent trigger term coverage for users working within the Cloudflare ecosystem. Its main weakness is the overly broad 'when' clause ('Use for any Cloudflare development task'), which doesn't provide nuanced guidance on when to select this skill versus potentially more specialized skills. The comprehensive listing of services is a strength for discoverability but the trigger guidance could be more explicit.
Suggestions
Replace 'Use for any Cloudflare development task' with more specific trigger guidance, e.g., 'Use when the user mentions Cloudflare, deploys to Cloudflare Workers/Pages, configures Cloudflare DNS/WAF/DDoS, or works with Cloudflare storage services like KV, D1, or R2.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete services and capabilities across several Cloudflare domains: Workers, Pages, KV, D1, R2, Workers AI, Vectorize, Agents SDK, Tunnel, Spectrum, WAF, DDoS, Terraform, Pulumi. This is highly specific and enumerates concrete technologies. | 3 / 3 |
Completeness | The 'what' is thoroughly covered with the enumeration of services and capabilities. However, the 'when' clause ('Use for any Cloudflare development task') is extremely broad and generic rather than providing explicit trigger guidance. It technically has a 'Use when' equivalent but it's so vague it barely qualifies. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Cloudflare', 'Workers', 'Pages', 'KV', 'D1', 'R2', 'Workers AI', 'Vectorize', 'Tunnel', 'WAF', 'DDoS', 'Terraform', 'Pulumi'. These are all terms a developer would naturally use when asking about Cloudflare tasks. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to the Cloudflare platform with highly specific product names (Workers, D1, R2, Vectorize, etc.) that are unlikely to conflict with other skills. The Cloudflare ecosystem is a distinct niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an exceptionally well-organized navigation index for the Cloudflare platform, with efficient decision trees and comprehensive product tables. However, it provides zero actionable content — no code examples, no commands, no configuration snippets — making it a pure routing document rather than a functional skill. Without bundle files to back up the references, it's essentially a table of contents pointing to potentially nonexistent content.
Suggestions
Add at least a minimal quick-start example for the most common use case (e.g., a basic Workers hello-world with `wrangler init` and `wrangler deploy` commands) so the skill has some standalone actionability.
Include a 'Common Patterns' section with 2-3 executable code snippets for frequent tasks like creating a Worker with KV binding, deploying a Pages site, or querying D1.
Add a brief workflow section showing the typical development cycle (e.g., init → develop → test locally → deploy → verify) with concrete wrangler commands and validation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is highly efficient — decision trees are compact and scannable, tables are minimal, and there's zero explanation of what Cloudflare products are or how they work conceptually. Every token serves navigation or reference purposes. | 3 / 3 |
Actionability | The skill contains no executable code, no concrete commands, no configuration examples, and no specific implementation guidance. It is purely a routing/navigation document that points to reference directories without providing any actionable content itself. | 1 / 3 |
Workflow Clarity | The decision trees provide clear sequencing for product selection, which is a useful workflow. However, there are no implementation workflows, no validation checkpoints, and no guidance on what to do after selecting a product beyond 'load detailed references.' | 2 / 3 |
Progressive Disclosure | The structure is well-organized with clear one-level-deep references to product directories. However, since no bundle files were provided, we cannot verify that any of the referenced paths actually exist, and the skill provides zero quick-start content — it's entirely an index with no usable content at the top level. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- elastic/elastic-ramen
- Commit
2e200ec
- 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.