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
100
100%
Does it follow best practices?
Impact
Pending
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. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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 that efficiently covers Astro framework usage with executable code examples, clear workflow steps for content collections, and appropriate progressive disclosure. It respects token budget by avoiding unnecessary explanations while remaining comprehensive across project structure, components, routing, layouts, and integrations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Astro is or how frameworks work in general, assumes Claude's competence, and every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples for components, content collections, routing, and queries. The code is copy-paste ready with real Astro syntax, TypeScript types, and Zod schemas. Client directive mappings are specific and practical. | 3 / 3 |
Workflow Clarity | The content collections workflow is clearly sequenced (steps 1-5) with explicit validation checkpoints including running build, checking TypeScript errors, and running validation scripts. The feedback loop of 'ensure pnpm build exits zero' provides a clear verification gate. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, and explicitly references REFERENCE.md for anti-patterns and SSR details. The content is appropriately split — core concepts inline, extended details one level deep. | 3 / 3 |
Total | 12 / 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
f5c8508
- 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.