CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudflare-workers-ai

Cloudflare Workers AI for serverless GPU inference. Use for LLMs, text/image generation, embeddings, or encountering AI_ERROR, rate limits, token exceeded errors.

61

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/cloudflare-workers-ai/skills/cloudflare-workers-ai/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 reference skill with copy-paste-ready code, a clear quick-start sequence, and exemplary progressive disclosure through the When-to-Load-References table. The main cost is redundancy: rate limits appear in three places and dated version/pricing details are inlined, which could be consolidated into the referenced files.

Suggestions

Consolidate rate-limit information into a single place (the model tables or the Rate Limits & Pricing section) and point to references/models-catalog.md for the rest, instead of repeating it across three sections.

Move time-sensitive version numbers and pricing figures (wrangler@4.81.0, $0.011 per 1,000 neurons, verification dates) into references/models-catalog.md or a clearly dated section, keeping the SKILL.md body stable.

Complete the runnable context for the common patterns: show the Hono app setup for Pattern 1 and the Vectorize binding configuration for the RAG pattern so the examples are fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly efficient (tables, executable code, no conceptual padding), but rate-limit information is repeated across the model tables, the Rate Limits & Pricing section, and the Limits Summary table, and time-sensitive dated info (wrangler@4.81.0, 'Information last verified: 2025-01-14', per-neuron pricing) is inlined rather than isolated. This places it between the efficient-4 and noticeably-verbose-2 anchors.

3 / 5

Actionability

The quick start (wrangler.jsonc binding + complete TypeScript worker), streaming example, RAG pattern, and AI Gateway snippet are concrete and executable. Minor gaps remain: Pattern 1 uses a Hono `app.post` handler without app setup, and the RAG pattern relies on an unshown `env.VECTORIZE` binding, keeping it below the fully copy-paste-ready 5 anchor.

4 / 5

Workflow Clarity

The numbered Quick Start (add binding, run first model, add streaming) gives a clear sequence, and the Production Checklist provides explicit pre-deploy checkpoints. Validation/error-recovery feedback loops are only pointed at via `references/best-practices.md` rather than presented inline, so it does not reach the 5 anchor's explicit validation steps.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references ('Load references/models-catalog.md', 'references/best-practices.md', 'references/integrations.md'), all of which exist, plus a dedicated 'When to Load References' table mapping each file to load conditions. Content is appropriately split between inline summaries and detail files with easy navigation.

5 / 5

Total

16

/

20

Passed

Description

75%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 solid description with an explicit Use-for clause, concrete capability keywords, and distinctive platform-specific error triggers. Its main weakness is a what-clause that names the platform rather than the skill's actions, leaving minor overlap risk on generic LLM terms.

DimensionReasoningScore

Specificity

The description names the domain ("Cloudflare Workers AI for serverless GPU inference") and lists several concrete capabilities ("LLMs, text/image generation, embeddings") plus error conditions. It falls short of 5 because coverage has gaps (vision, streaming, chat, RAG are not mentioned) but exceeds 3 since more than 1-2 specific capabilities are named.

4 / 5

Completeness

Both what and when are present: "Use for LLMs, text/image generation, embeddings, or encountering AI_ERROR, rate limits, token exceeded errors" is an explicit when-clause with concrete triggers. The what ("Cloudflare Workers AI for serverless GPU inference") describes the platform rather than the skill's actions, keeping it below the fully explicit 5 anchor.

4 / 5

Trigger Term Quality

Phrases like "LLMs", "text/image generation", "embeddings", "AI_ERROR", "rate limits", "token exceeded" are natural terms a user would say when needing this skill. A few natural terms are missing (chat, vision, specific model IDs), so it matches the good-but-not-comprehensive anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Cloudflare Workers AI" and "AI_ERROR" establish a clear niche with minimal conflict risk against unrelated skills. Generic triggers like "LLMs" and "rate limits" could overlap with other AI-provider skills, so it sits at mostly-distinct rather than the minimal-conflict 5 anchor.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/cloudflare-workers-ai/skills/cloudflare-workers-ai/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.