astro-project-starter
Scaffold an Astro 5.x project with content collections, islands architecture, framework integrations (React/Vue/Svelte), MDX, view transitions, and multi-adapter deployment.
84
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./frontend/astro-project-starter/SKILL.mdQuality
Discovery
67%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 description excels at specificity and distinctiveness by naming concrete Astro-specific features and the framework version. However, it lacks an explicit 'Use when...' clause which is critical for Claude to know when to select this skill, and could benefit from more natural trigger terms users might say when requesting Astro help.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user wants to create an Astro site, build a static website, or mentions Astro, .astro files, or islands architecture.'
Include common user terms like 'static site generator', 'SSG', 'create new Astro project', or 'Astro website' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: scaffold project, content collections, islands architecture, framework integrations (with specific frameworks named), MDX, view transitions, and multi-adapter deployment. | 3 / 3 |
Completeness | Clearly describes WHAT the skill does (scaffold Astro projects with various features), but lacks an explicit 'Use when...' clause to indicate WHEN Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good technical terms like 'Astro 5.x', 'React/Vue/Svelte', 'MDX', 'islands architecture', but missing common user phrases like 'static site', 'SSG', 'create Astro app', or file extensions like '.astro'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Astro 5.x' as a clear niche identifier. The specific framework name and version, combined with Astro-specific features like 'islands architecture' and 'content collections', make it unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and conciseness. It provides comprehensive, executable examples covering the full Astro 5.x feature set without unnecessary explanation. The main weakness is the monolithic structure - the content would benefit from progressive disclosure by splitting advanced topics into separate files for better navigation.
Suggestions
Split advanced topics (SSR Mode, Content Collections, View Transitions) into separate reference files and link from a condensed SKILL.md overview
Add a 'Quick Reference' section at the top with the most common patterns, relegating detailed examples to linked files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary explanations about what Astro is or how frameworks work. | 3 / 3 |
Actionability | Fully executable code throughout - from scaffold commands to complete component examples, config files, and API endpoints. All examples are copy-paste ready with proper TypeScript types and real-world patterns. | 3 / 3 |
Workflow Clarity | Clear 'First Steps After Scaffold' section provides explicit sequenced steps with validation checkpoint (step 5: 'Run npx astro check to confirm diagnostics pass'). The scaffold process and common commands are well-organized and unambiguous. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting advanced topics (SSR, content collections, view transitions) into separate reference files. No external file references are provided. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (532 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.