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 a strong skill description that clearly identifies the Astro framework domain with specific capabilities, explicit trigger guidance, and framework-specific terminology that minimizes conflict risk. It uses proper third-person voice and is concise without being vague. The inclusion of both a 'Use when' clause and explicit trigger terms makes it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates pages/layouts, defines content collections, configures hydration directives, and wires 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' list). | 3 / 3 |
Trigger Term Quality | Includes excellent natural keywords users would say: 'Astro', 'content collection', 'client:load', 'client:visible', 'astro:content', plus terms like 'pages', 'layouts', 'components'. These cover both framework-specific directives and general terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to Astro-specific terminology like 'client:load', 'client:visible', 'astro:content', and 'hydration directives'. These are unique to the Astro framework and unlikely to conflict with other web framework 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 with validation checkpoints, and appropriate progressive disclosure. It respects token budget by avoiding unnecessary explanations while remaining comprehensive across project structure, components, content collections, 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 querying. The code is copy-paste ready with real TypeScript/Astro syntax, specific directives with clear use-case mappings, and concrete commands like `pnpm build`. | 3 / 3 |
Workflow Clarity | The content collections workflow is clearly sequenced (steps 1-5) with explicit validation checkpoints (run build, verify TypeScript types, ensure zero exit code). The feedback loop of build → validate → confirm typing is well-defined. | 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. Content is appropriately split with one-level-deep references clearly signaled. | 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
18c6f2c
- 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.