astro-framework
Creates pages/layouts, defines content collections, configures hydration directives, and wires integrations. Use when adding or modifying Astro pages, layouts, components, or content collections. Trigger terms: Astro, content collection, client:load, client:visible, astro:content
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 covers all key dimensions well. It provides specific concrete actions, includes both a 'Use when' clause and explicit trigger terms with Astro-specific keywords, and is clearly distinguishable from other web framework skills. The description is concise yet comprehensive, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating pages/layouts, defining content collections, configuring hydration directives, and wiring integrations. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates pages/layouts, defines content collections, configures hydration directives, wires integrations) and 'when' (explicit 'Use when' clause plus explicit trigger terms section). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'Astro', 'content collection', 'client:load', 'client:visible', 'astro:content', plus contextual terms like 'pages', 'layouts', 'components', and 'hydration directives'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Astro-specific terminology like 'client:load', 'client:visible', 'astro:content', and 'content collection' that clearly distinguish it from generic web framework skills. Unlikely to conflict with other 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 solid, actionable Astro skill with executable code examples covering the key framework concepts (components, content collections, routing, layouts). The content collection workflow stands out with clear sequencing and validation steps. The main weaknesses are minor verbosity in some sections and a reference to REFERENCE.md that doesn't exist in the bundle, undermining the progressive disclosure strategy.
Suggestions
Provide the referenced REFERENCE.md file in the bundle, or inline the critical anti-patterns if the file won't be included.
Trim explanatory phrases Claude already knows (e.g., 'file-based routing', 'serves static assets as-is') to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples and minimal fluff, but some sections include explanations Claude already knows (e.g., 'file-based routing', explaining what public/ does, listing what astro add supports). The content could be tightened in places like the client directives descriptions and the layouts section. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for components, content collections, routing, and querying. The content collection workflow includes specific commands (pnpm build, pnpm dev) and concrete TypeScript/Astro code with real schemas and queries. | 3 / 3 |
Workflow Clarity | The content collection workflow is clearly sequenced (steps 1-5) with explicit validation checkpoints: running build, checking TypeScript errors, and verifying collection imports. Step 5 explicitly validates that pnpm build exits zero and TypeScript reports no errors, providing a proper feedback loop. | 3 / 3 |
Progressive Disclosure | References REFERENCE.md for anti-patterns which is good progressive disclosure, but REFERENCE.md is not provided in the bundle, making the reference unverifiable. The main content is reasonably well-structured with clear sections, but some content (like the full routing example and API routes section) could potentially be split out for better organization. | 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
- monkilabs/opencastle
- Commit
7a69a05
- 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.