CtrlK
BlogDocsLog inGet started
Tessl Logo

astro

Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/astro/SKILL.md

The canonical home for this skill is astro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%Scale 1-5

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, highly actionable Astro skill with excellent executable code examples covering the full spectrum of Astro features. Its main weaknesses are moderate verbosity (the overview and 'when to use' sections explain things Claude already knows) and a monolithic structure that would benefit from splitting advanced examples into separate bundle files. The workflow is logically sequenced but lacks explicit verification steps.

Suggestions

Trim the Overview and 'When to Use This Skill' sections significantly — Claude knows what Astro is and can infer when to use it from the skill description and content.

Split advanced examples (RSS feed, API endpoints, React islands) into a separate EXAMPLES.md bundle file and reference it from the main skill.

Add a brief verification step after project setup (e.g., 'Verify: `npm run dev` should show the site at localhost:4321') and after build (`npm run build && npm run preview`).

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some unnecessary explanation Claude would already know (e.g., the Overview section explaining what Astro is, what Islands Architecture means, listing supported frameworks). The 'When to Use This Skill' section is somewhat redundant. However, the code examples themselves are lean and well-targeted. Overall, it could be tightened by ~30%.

3 / 5

Actionability

Excellent actionability throughout — every section includes copy-paste ready code examples covering project setup, component syntax, routing, content collections, hydration directives, layouts, SSR config, RSS feeds, API endpoints, and React islands. The examples are complete and executable, covering all common use cases.

5 / 5

Workflow Clarity

The steps are clearly sequenced from project setup through increasingly advanced features (components → routing → content collections → islands → layouts → SSR). However, there are no explicit validation checkpoints — e.g., no 'verify the dev server runs' after setup, no 'check build output' step. Since this isn't a destructive/batch operation skill, the missing validation doesn't cap the score, but it would benefit from a build/verify step.

4 / 5

Progressive Disclosure

The content is well-structured with clear section headers, but it's a long monolithic file (~250+ lines) with no references to external files for advanced topics. The API endpoints, RSS feed, and React island examples could be split into separate reference files. The 'Related Skills' section is a nice touch but doesn't compensate for the lack of bundle files to offload detailed examples.

3 / 5

Total

15

/

20

Passed

Description

53%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies Astro as the target framework and lists its key architectural features, providing reasonable specificity for the domain. However, it lacks an explicit 'Use when...' clause, relies more on describing Astro's characteristics than concrete skill actions, and misses common natural trigger terms users would employ when requesting Astro-related help.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about Astro, static sites, content-driven websites, .astro files, or content collections.'

Include more concrete actions beyond 'Build', such as 'configure routing, create content collections, set up integrations, add interactive islands'.

Add natural synonyms and related terms like 'static site', 'SSG', 'blog', '.astro files', and 'content collections' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Astro websites) and lists architectural features (zero JS, islands architecture, multi-framework components, Markdown/MDX), but these describe Astro's characteristics rather than concrete actions the skill performs. Only one action verb ('Build') is present.

3 / 5

Completeness

Has a clear 'what' (build content-focused websites with Astro and its features), but there is no explicit 'when' clause. The description lacks a 'Use when...' statement or equivalent trigger guidance, which caps this dimension at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes 'Astro', 'Markdown', 'MDX', and 'websites' which are relevant keywords, but misses natural user phrases like 'static site', 'SSG', 'blog', '.astro files', 'content collections', or 'Astro project'. Terms like 'islands architecture' are more technical jargon than natural trigger terms.

3 / 5

Distinctiveness Conflict Risk

Mentioning 'Astro' specifically makes it fairly distinct from other web framework skills (e.g., Next.js, Gatsby). However, 'content-focused websites' and 'Markdown/MDX support' could overlap with other static site generator or content management skills.

4 / 5

Total

13

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.