cloudflare-mcp-server
Build MCP (Model Context Protocol) servers on Cloudflare Workers with tools, resources, and prompts.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill cloudflare-mcp-serverOverall
score
66%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear technical niche (MCP servers on Cloudflare Workers) which provides good distinctiveness, but lacks explicit trigger guidance and concrete action verbs. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill from a large skill library.
Suggestions
Add a 'Use when...' clause with trigger terms like 'MCP server', 'Cloudflare Workers', 'Model Context Protocol', 'edge deployment', or 'serverless MCP'.
Expand the capability list with specific actions: 'scaffold projects', 'define tool handlers', 'configure resource endpoints', 'deploy to Cloudflare'.
Include common user phrasings like 'deploy MCP to the edge', 'create a Cloudflare MCP server', or 'build serverless MCP tools'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (MCP servers on Cloudflare Workers) and mentions components (tools, resources, prompts), but doesn't list concrete actions like 'create endpoints', 'configure authentication', or 'deploy workers'. | 2 / 3 |
Completeness | Describes what it does (build MCP servers) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'MCP', 'Model Context Protocol', 'Cloudflare Workers', but misses common variations users might say like 'deploy', 'serverless', 'edge functions', or 'API server'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'MCP servers' and 'Cloudflare Workers' creates a clear, specific niche that is unlikely to conflict with other skills - this is a very targeted use case. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at token efficiency and progressive disclosure, providing a clean overview with well-organized references to detailed documentation. However, it lacks a clear workflow sequence for the multi-step process of building and deploying MCP servers, and some code examples are incomplete (using `[...]` placeholder syntax).
Suggestions
Add a numbered workflow section showing the complete build-deploy sequence: 1. Create project → 2. Define tools → 3. Test locally → 4. Deploy → 5. Verify
Replace `{ results: [...] }` with actual executable code or a concrete return value example
Add a brief validation step or link to testing guidance after the Quick Start example
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean content that assumes Claude's competence. No unnecessary explanations of what MCP is or how Workers function - just actionable code and organized references. | 3 / 3 |
Actionability | Provides executable TypeScript examples for basic setup and tool definition, but the tool handler example uses incomplete syntax (`[...]`) and lacks complete copy-paste ready code for the full workflow. | 2 / 3 |
Workflow Clarity | No explicit workflow sequence for building and deploying an MCP server. The skill lists concepts and examples but doesn't guide through the multi-step process of setup -> development -> deployment with validation checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent structure with concise overview pointing to well-organized references. Clear one-level-deep navigation with descriptive annotations (line counts, purpose) for each reference file and template. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.