perf-astro
Astro-specific performance optimizations for 95+ Lighthouse scores. Covers critical CSS inlining, compression, font loading, and LCP optimization. Use when optimizing Astro site performance, improving Astro Lighthouse scores, or configuring astro-critters. Do NOT use for non-Astro sites (use perf-web-optimization or core-web-vitals) or running Lighthouse audits (use perf-lighthouse).
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 hits all the marks. It provides specific concrete actions, includes natural trigger terms, clearly answers both what and when, and proactively distinguishes itself from related skills with explicit negative triggers and alternative skill references. The inclusion of 'Do NOT use' clauses with redirects to other skills is a best practice that further reduces conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'critical CSS inlining, compression, font loading, and LCP optimization' along with a concrete target metric '95+ Lighthouse scores'. | 3 / 3 |
Completeness | Clearly answers both what ('critical CSS inlining, compression, font loading, LCP optimization') and when ('Use when optimizing Astro site performance, improving Astro Lighthouse scores, or configuring astro-critters'). Also includes explicit negative triggers ('Do NOT use for non-Astro sites') with alternative skill references. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Astro', 'Lighthouse scores', 'performance', 'critical CSS', 'font loading', 'LCP', 'astro-critters'. These are terms a developer would naturally use when seeking this help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear Astro-specific niche. Explicitly differentiates from related skills (perf-web-optimization, core-web-vitals, perf-lighthouse) with 'Do NOT use' guidance, making conflict very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted skill that provides concrete, actionable Astro performance optimization guidance with excellent token efficiency. The layout template is particularly valuable as a complete, copy-paste ready reference. The main weakness is the lack of explicit validation steps—there's no feedback loop for verifying that optimizations actually achieved the 95+ Lighthouse target or troubleshooting when they don't.
Suggestions
Add a brief validation/feedback loop after the build step: e.g., 'Run lighthouse, if score < 95 check: (1) critters build output shows inlining, (2) LCP image is preloaded, (3) no render-blocking resources in DevTools'
Consider adding a brief troubleshooting section for common issues (e.g., critters not inlining enough CSS, compress breaking JS, fonts still blocking render)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose with no unnecessary explanations of basic concepts. The brief descriptions of what astro-critters does are justified since they describe library-specific behavior, not general knowledge. | 3 / 3 |
Actionability | Fully executable code examples throughout: install commands, complete astro.config.mjs configuration, a full Layout.astro template with copy-paste ready patterns for font loading, LCP preloading, and script deferral. The lighthouse command is also concrete and runnable. | 3 / 3 |
Workflow Clarity | The skill provides a clear setup sequence and a checklist, but lacks explicit validation/verification steps. After configuring integrations and the layout pattern, there's no guidance on verifying the build output, checking that critters actually inlined CSS correctly, or a feedback loop for when Lighthouse scores don't meet the 95+ target. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from quick setup to integrations to layout pattern to measuring. Cross-references to related skills (perf-lighthouse, perf-web-optimization) are clearly signaled and one level deep. Content is appropriately scoped without being monolithic. | 3 / 3 |
Total | 11 / 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
- tech-leads-club/agent-skills
- Commit
81e7e0d
- 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.