CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agents-sdk

Build, debug, or review Cloudflare Agents SDK applications using the agents package.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/agents-sdk/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable reference skill: executable code and config throughout, verified one-level-deep references organized by category, and a sensible retrieval-first stance. The two weaknesses are triplicated capability cataloging that inflates token cost without adding information, and the lack of any validation checkpoint (dev-server smoke test or deploy verification) in the implied build sequence.

Suggestions

Consolidate the three overlapping catalogs — the Retrieval Sources table's "Use for" column, the Capabilities bullet list, and the References descriptions — into one mapping (e.g. topic → docs URL → reference file) to cut roughly a third of the body's tokens.

Add a validation checkpoint after the Agent Class example, such as "Smoke test: `npx wrangler dev` then hit `/agents/counter/test` and confirm the state persists", turning the implied sequence into a workflow with explicit verification.

Fold the Gotchas list into the Wrangler Configuration section as immediate do/don't checks rather than trailing prose, so config mistakes are caught at the step where they occur.

DimensionReasoningScore

Conciseness

The body is mostly efficient — terse tables, commands, and a retrieval-first directive with no explanations of concepts Claude already knows — but the same capability space is cataloged three times (the 31-row Retrieval Sources table's "Use for" column, the 17-bullet Capabilities list, and the 20-entry References section), which is unnecessary duplication that could be consolidated. This matches anchor 3 (mostly efficient, some content that could be tightened) better than anchor 4's minor-trimmings bar.

3 / 5

Actionability

Guidance is fully executable: copy-paste install commands ("npm install agents @cloudflare/ai-chat ai @ai-sdk/react"), a complete wrangler.jsonc snippet, a complete runnable Agent class with routing export and default fetch handler, and a Core APIs table with real syntax for every common task. It matches anchor 5 (copy-paste ready, covers common cases) and exceeds anchor 4 because there are no material gaps in the core examples.

5 / 5

Workflow Clarity

A rough sequence is implied (prefer retrieval → verify installation → configure wrangler → define agent class → route → client hooks), but validation checkpoints are absent: no local smoke test (e.g. `npx wrangler dev`), no deploy/verify step, and the "Gotchas" are stated as facts rather than as checkpoints in a flow. This matches anchor 3 (sequence present, checkpoints missing or implicit); it is more structured than anchor 2's poorly defined steps but lacks the explicit verification of anchor 4. No destructive/batch cap applies.

3 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references: all 20 referenced files exist in references/, none point to further nested references, links are bolded with one-line descriptions, and they are grouped into thematic sections (Core, Chat & Streaming, Background Processing, Integrations, Experimental). Inline content (config snippet, agent class, API table) is appropriate overview material with bulk detail correctly split out, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, distinctive description with concrete verbs and good natural keyword coverage for the SDK's name and package. Its main weakness is the absence of any explicit 'when to use' trigger clause, which caps completeness and leaves triggering to implicit domain matching. Adding a Use-when line with concrete trigger phrases (Workers, Durable Objects, useAgent, AIChatAgent) would lift it into the top tier.

Suggestions

Add an explicit trigger clause, e.g. "Use when building Cloudflare Workers with Durable Objects, using the agents or agents-sdk package, or when the user mentions useAgent, AIChatAgent, or AgentWorkflow."

Include one or two signature API names (setState, @callable, AIChatAgent) in the description to broaden natural trigger-term coverage beyond just the SDK name.

Optionally name the concrete task types covered (chat agents, scheduled tasks, durable workflows, MCP servers) to make the capability list more comprehensive.

DimensionReasoningScore

Specificity

"Build, debug, or review Cloudflare Agents SDK applications using the agents package" names three concrete actions (build, debug, review) plus the target domain and package. It falls short of anchor 5's comprehensive coverage because it stays at the verb level and never names specific sub-capabilities (state, scheduling, chat agents, workflows) that would make the action list comprehensive.

4 / 5

Completeness

The 'what' is clearly stated (build, debug, or review Agents SDK applications), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The 'when' is only weakly implied by the domain name itself, matching anchor 3 (clear what, missing/weak when) rather than anchor 4 which requires both.

3 / 5

Trigger Term Quality

Natural trigger phrases are present — "Cloudflare Agents SDK", "agents package", "build, debug, or review ... applications" — which users of this SDK would genuinely say. It misses common variations and synonyms like "Cloudflare Workers", "Durable Objects", "useAgent", or "AIChatAgent", so it does not reach anchor 5's comprehensive synonym coverage but sits above anchor 3's partial keyword set.

4 / 5

Distinctiveness Conflict Risk

"Cloudflare Agents SDK" and "the agents package" carve out a clear niche with distinct triggers; only another Cloudflare Agents skill could overlap, and the specific SDK/package naming minimizes that risk, matching anchor 5. It is clearly more distinct than anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

16

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

cloudflare/skills

Path

skills/agents-sdk/SKILL.md

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.