cloudflare-agents
Build AI agents on Cloudflare Workers with MCP integration, tool use, and LLM providers.
62
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/cloudflare-agents/skills/cloudflare-agents/SKILL.mdQuality
Discovery
32%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 specific technical domain (Cloudflare Workers AI agents) but relies on feature listing rather than concrete actions. The critical weakness is the complete absence of explicit trigger guidance ('Use when...'), which makes it difficult for Claude to know when to select this skill from a large skill library.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when building serverless AI agents, deploying agents to Cloudflare, or integrating MCP tools with edge workers'
Replace feature list with concrete actions: 'Create, deploy, and configure AI agents on Cloudflare Workers' rather than just 'Build AI agents'
Include natural user phrases and file/project indicators like 'wrangler.toml', 'Workers AI', 'edge deployment', or 'Cloudflare agent project'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AI agents on Cloudflare Workers) and lists some capabilities (MCP integration, tool use, LLM providers), but these are high-level features rather than concrete actions like 'create', 'deploy', or 'configure'. | 2 / 3 |
Completeness | Describes what (build AI agents with certain features) 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 'AI agents', 'Cloudflare Workers', 'MCP', 'LLM providers', but missing common user variations like 'serverless agents', 'edge AI', 'model context protocol', or action-oriented terms users might say. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Cloudflare Workers' and 'MCP integration' provides some distinctiveness, but 'AI agents' and 'LLM providers' are generic enough to potentially overlap with other agent-building or LLM-related skills. | 2 / 3 |
Total | 7 / 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 conciseness and progressive disclosure, providing a clean overview that efficiently points to detailed resources. However, the Quick Start code is not fully executable due to the undefined `processWithLLM` function, and there's no clear workflow for getting started with Cloudflare Agents from scratch.
Suggestions
Replace the Quick Start with fully executable code - either use the actual agents-sdk API or reference a complete template file
Add a brief numbered workflow: 1) Install dependencies, 2) Configure wrangler.toml, 3) Create agent, 4) Deploy - pointing to relevant templates/docs for each step
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information without explaining concepts Claude already knows. No verbose explanations of what agents, tools, or LLMs are. | 3 / 3 |
Actionability | The Quick Start provides executable TypeScript code, but the `processWithLLM` function is undefined/pseudocode. The Agent Pattern section is also incomplete - it shows structure but not actual implementation. | 2 / 3 |
Workflow Clarity | For a simple overview skill, the structure is adequate, but there's no clear workflow for building an agent from scratch. No validation steps or sequence for setting up the environment, configuring wrangler, or deploying. | 2 / 3 |
Progressive Disclosure | Excellent organization with clear one-level-deep references. Resources are well-categorized (Core Documentation, Integration Guides, Advanced Features, Templates) with helpful line counts and descriptions. | 3 / 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
- secondsky/claude-skills
- Commit
90d6bd7
- 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.