CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudflare-email-service

Implement or troubleshoot Cloudflare Email Sending and Email Routing integrations and their delivery configuration.

Quality

74%

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 ./config/claude/skills/cloudflare-email-service/SKILL.md

The canonical home for this skill is cloudflare-email-service in cloudflare/skills

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 router skill: actionable commands, a clear prerequisite-first workflow, excellent one-level-deep bundle organization, and a high-value Common Mistakes table. The main defect is redundancy in the opening retrieval-source framing.

Suggestions

Merge the two near-duplicate 'your knowledge may be outdated — prefer retrieval over pre-training' paragraphs into a single sentence, keeping the source-of-truth hierarchy once.

Add a minimal inline send example (binding send or REST curl) so the most common case is executable without opening a reference file.

Add an explicit post-send verification step (e.g. check the API response / handle bounces) to the Sending Workflow to complete the feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly dense tables and concrete commands, but 'Prefer retrieval over pre-training' is stated twice in near-identical opening paragraphs and a third paragraph repeats the trust-the-sources point — unnecessary explanation that could be tightened into one statement.

3 / 5

Actionability

Copy-paste-ready commands and exact fixes throughout ('npx wrangler email sending list', 'wrangler email routing addresses create user@gmail.com', the message.raw buffering one-liner, REST vs Workers field-name corrections), with the minor gap that no minimal send example appears inline.

4 / 5

Workflow Clarity

Clear sequence — prerequisite checklist with verification commands, situation-routing table, then 'read the reference before writing code' — plus recovery guidance (domain missing → enable it) and a Common Mistakes table; falls short of 5 because no post-send validation/verification step appears in the body.

4 / 5

Progressive Disclosure

A lean overview with a situation-routing table and a References section where all five bundle files exist, are one level deep, and are clearly signaled with one-line purposes — easy navigation, content appropriately split.

5 / 5

Total

16

/

20

Passed

Description

65%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 distinctive, domain-precise description that clearly states what the skill covers but omits any explicit 'when to use' trigger guidance and enumerates only two actions. Adding a Use-when clause and more concrete capability verbs would round it out.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when sending or receiving email via Cloudflare Workers, setting up Email Routing, fixing email deliverability, or working with the Email Sending REST API.'

Enumerate a few more concrete actions to lift specificity, e.g. 'send transactional email from Workers or via REST, route and forward inbound email, configure SPF/DKIM/DMARC deliverability'.

Include natural synonyms users would say ('transactional email', 'inbound email', 'email forwarding', 'spam folder') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain precisely ('Cloudflare Email Sending and Email Routing integrations and their delivery configuration') with two concrete actions ('Implement', 'troubleshoot'), matching the 1-2-concrete-actions anchor rather than the 'several specific actions' anchor above it.

3 / 5

Completeness

The 'what' is clear (implement/troubleshoot email sending, routing, and delivery configuration) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps this dimension at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'Cloudflare', 'Email Sending', 'Email Routing', 'troubleshoot', and 'delivery configuration' are terms users would naturally say, but common variations like 'send transactional email', 'inbound email', 'forwarding', or 'SPF/DKIM' are missing — good coverage, a few natural terms short of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

'Cloudflare Email Sending and Email Routing' carves out a clear niche with distinct product-name triggers; no plausible conflict with other skills.

5 / 5

Total

15

/

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

freekmurze/dotfiles

Path

config/claude/skills/cloudflare-email-service/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.