examples
Use when working in the examples/ directory, running an example with wrangler dev, adding a new example, or answering questions about EXPOSE directives and the local Docker dev loop. (project)
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/examples/SKILL.mdQuality
Discovery
75%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 has a clear 'Use when...' clause with explicit triggers and is well-scoped to a specific niche, making it strong on completeness and distinctiveness. However, it could be more specific about the concrete actions it enables and include more natural keyword variations that users might use when seeking help with these topics.
Suggestions
Add more concrete actions like 'scaffold new example projects, configure Dockerfile EXPOSE ports, debug wrangler dev issues' to improve specificity.
Include additional natural trigger terms users might say, such as 'Cloudflare Workers', 'Dockerfile', 'local development', 'port configuration', or 'sample project'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain (examples/ directory, wrangler dev, Docker dev loop, EXPOSE directives) and some actions (running an example, adding a new example, answering questions), but doesn't list multiple concrete specific actions like 'configure Dockerfile EXPOSE ports' or 'scaffold new example projects'. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (working in examples/ directory, running examples, adding new examples, answering questions about EXPOSE directives and Docker dev loop) and 'when' with a clear 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'wrangler dev', 'EXPOSE directives', 'Docker dev loop', and 'examples/ directory', but misses common variations users might say such as 'Cloudflare Workers', 'Dockerfile', 'port mapping', 'local development', or 'sample project'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'examples/ directory', 'wrangler dev', 'EXPOSE directives', and 'local Docker dev loop' creates a very specific niche that is unlikely to conflict with other skills. The '(project)' tag further scopes it. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-written, practical skill that efficiently communicates project-specific knowledge about the examples directory. Its strengths are conciseness and actionability — it provides concrete commands and clear structure without over-explaining. The main weaknesses are the lack of explicit validation checkpoints in the add-new-example workflow and the opportunity to better leverage progressive disclosure through cross-references to individual example READMEs.
Suggestions
Add an explicit validation step to the 'Adding a New Example' workflow, such as running a specific test or lint command to confirm the example is properly integrated.
Link each example name in the table to its respective README or directory for easier navigation and discovery.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Docker is, what wrangler is, or how npm works. Every section delivers information Claude wouldn't already know (project-specific commands, directory structure, EXPOSE behavior in Cloudflare containers). The table format for examples is particularly token-efficient. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready commands (`npm run dev`, `npm run docker:rebuild`), a clear step-by-step process for adding new examples, and specific file paths and config names to update. The troubleshooting tip about deleting stale images includes the exact command to find them. | 3 / 3 |
Workflow Clarity | The 'Adding a New Example' section has a clear 5-step sequence, and the running/rebuilding workflow is well-explained. However, there are no explicit validation checkpoints — step 4 says 'make sure the example builds' but doesn't specify how to verify beyond running `npm run dev`. For a workflow that modifies project structure, a validation step (e.g., running a lint or test command) would strengthen it. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a useful table, but everything is inline in a single file. The reference to `packages/sandbox/README.md` is appropriate, but the examples table could benefit from linking to each example's README. No bundle files are provided, so there's no deeper structure to evaluate, but the skill is borderline long enough that separating the example catalog or development tips could improve navigation. | 2 / 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
- cloudflare/sandbox-sdk
- Commit
3b58a22
- 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.