astroflare
Astro x Tailwind v4 projects on Cloudflare Workers. Use when working with Astro projects deployed to Cloudflare.
73
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
57%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 identifies a specific technology stack (Astro, Tailwind v4, Cloudflare Workers) which provides good distinctiveness, but fails to articulate what concrete actions or capabilities the skill provides. The 'Use when' clause is present but narrow, and the description reads more like a label than a functional guide for skill selection.
Suggestions
Add specific actions the skill enables, e.g., 'Creates, configures, and deploys Astro x Tailwind v4 projects on Cloudflare Workers'
Expand trigger terms to include related concepts users might mention: 'static site', 'edge functions', 'SSR', '.astro files', 'wrangler'
Broaden the 'Use when' clause to cover more scenarios: 'Use when creating Astro projects, configuring Tailwind v4, deploying to Cloudflare Workers, or setting up edge-rendered sites'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Astro, Tailwind v4, Cloudflare Workers) but lacks concrete actions. It doesn't specify what actions can be performed - no verbs like 'create', 'deploy', 'configure', or 'build'. | 2 / 3 |
Completeness | Has a 'Use when...' clause which is good, but the 'what' portion is weak - it only names technologies without explaining what the skill actually does with them. The trigger is also narrow (only Cloudflare deployment). | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Astro', 'Tailwind v4', and 'Cloudflare Workers/Cloudflare' that users might mention, but misses common variations like 'static site', 'SSR', 'edge deployment', or file extensions like '.astro'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Astro + Tailwind v4 + Cloudflare Workers is a specific tech stack that creates a clear niche. Unlikely to conflict with generic web development or other framework-specific skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates strong organization and conciseness, effectively serving as an overview document that points to detailed references. However, it would benefit from at least one concrete code example showing the Astro + Cloudflare Workers pattern in action, and could include a basic workflow for common tasks like adding a new server island or deploying changes.
Suggestions
Add a concrete code example showing a server island component with `server:defer` directive to make the guidance immediately actionable
Include a brief workflow for common development tasks (e.g., adding a new page with server action) with validation steps
Add a minimal example of the Cloudflare adapter configuration mentioned in the deployment target section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section provides specific, actionable information without padding or unnecessary context about what Astro, Tailwind, or Cloudflare are. | 3 / 3 |
Actionability | While the skill provides clear principles and project structure, it lacks executable code examples. The guidance is specific but mostly descriptive (e.g., 'Use server:defer directive') rather than showing concrete implementation patterns that are copy-paste ready. | 2 / 3 |
Workflow Clarity | The skill provides good organizational structure but lacks explicit multi-step workflows with validation checkpoints. For deployment and build processes, there are no clear sequences or feedback loops - it just references external files for these details. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to detailed guidance files. The references section clearly maps topics to specific files for deeper exploration. | 3 / 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.
- 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.