cloudflare-images
Store and transform images with Cloudflare Images API and transformations. Use when: uploading images, implementing direct creator uploads, creating variants, generating signed URLs, optimizing formats (WebP/AVIF), transforming via Workers, or debugging CORS, multipart, AVIF limits, metadata stripping, cache issues, or error codes 9401-9413.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill cloudflare-images87
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
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities, includes a comprehensive 'Use when:' clause with both common use cases and debugging scenarios, uses natural trigger terms users would actually search for, and is clearly scoped to Cloudflare's specific image service to avoid conflicts with other image-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'uploading images', 'implementing direct creator uploads', 'creating variants', 'generating signed URLs', 'optimizing formats', 'transforming via Workers', plus specific debugging scenarios with error codes. | 3 / 3 |
Completeness | Clearly answers both what ('Store and transform images with Cloudflare Images API') and when with explicit 'Use when:' clause listing specific trigger scenarios including both common tasks and debugging situations. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'uploading images', 'signed URLs', 'WebP/AVIF', 'CORS', 'multipart', 'cache issues', and specific error codes '9401-9413' that users would search for when troubleshooting. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Cloudflare Images API' as the clear niche, plus specific technical terms like 'direct creator uploads', 'Workers', and Cloudflare-specific error codes that wouldn't conflict with generic image processing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent executable code examples and clear workflows. The comprehensive error documentation is valuable but makes the file lengthy; moving detailed issue documentation to a reference file would improve token efficiency while maintaining the skill's practical utility.
Suggestions
Move the detailed 16 documented issues to a separate 'references/common-issues.md' file, keeping only the top 3-5 most critical issues (CORS, file field naming, loop errors) inline with brief summaries
Condense the Advanced Topics section by moving R2 integration details and Product Merge Migration notes to reference files, keeping only brief pointers
Remove explanatory phrases like 'Why It Happens' headers - Claude can infer causation from the prevention code patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose sections, particularly the 16 documented issues which could be condensed or moved to a reference file. The advanced topics section also contains explanatory content that could be trimmed. | 2 / 3 |
Actionability | Excellent executable code examples throughout - curl commands, TypeScript/JavaScript snippets, and HTML examples are all copy-paste ready. Each issue includes concrete prevention code with correct vs wrong patterns clearly marked. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints. The Quick Start provides numbered steps, Direct Creator Upload shows the correct architecture flow, and troubleshooting sections provide systematic diagnostic approaches. | 3 / 3 |
Progressive Disclosure | References templates/, references/, and scripts/ directories appropriately, but the main file is quite long (~600 lines). The 16 documented issues section could be moved to a separate reference file, with only the top 3-5 most critical issues inline. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (717 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 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.