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.

64

Quality

76%

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/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

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable, copy-paste-ready examples and a clearly sequenced seven-step workflow. It is well-structured and concise, with only minor over-explanation and some inlined content that could be split into reference files.

Suggestions

Tighten the Overview paragraph — Astro's Islands Architecture is well-known to Claude; reduce it to the essential trigger context.

Move the Examples and the full integrations list into a reference bundle file (e.g. references/examples.md) and link to it from SKILL.md to improve progressive disclosure.

Add a brief verification checkpoint (e.g. run `npm run build` after routing/content-collection changes) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Efficient overall with mostly executable, purposeful code blocks, though the Overview paragraph explaining Islands Architecture and a few inline comments restate concepts Claude likely already knows and could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready code across setup, component syntax, routing, content collections, islands, layouts, SSR, RSS, and API endpoints, covering the common cases.

5 / 5

Workflow Clarity

Seven numbered steps are clearly sequenced with concrete commands and code, but there are no explicit validation/verification checkpoints between steps; acceptable here since the operations are not destructive or batch-oriented.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, though a fair amount of reference-like content (the Examples section, integrations list) is inlined in a single ~360-line file rather than split into separate bundle files.

4 / 5

Total

17

/

20

Passed

Description

71%Weight 40%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 is specific and lists concrete capabilities clearly, but it lacks an explicit 'Use when...' trigger clause, which caps completeness and slightly weakens trigger-term quality. It is distinct from competing framework skills with only minor overlap risk.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building a blog, docs site, marketing page, or portfolio with Astro, or when the user mentions .astro files, content collections, or client: directives.'

Include natural user phrases and file extensions as trigger terms, such as 'build a blog', 'docs site', and '.astro' files, to improve keyword coverage.

Maintain third-person voice (already correct) but ensure the description pairs the 'what' with a concrete 'when' to lift completeness above 3.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Build content-focused websites with Astro', 'zero JS by default', 'islands architecture', 'multi-framework components', and 'Markdown/MDX support' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Has a clear 'what' but no 'when' clause — there is no 'Use when...' trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage ('Astro', 'Markdown/MDX', 'websites') but missing natural phrases a user would say such as 'build a blog' or 'docs site', and no file-extension or synonym coverage like '.astro'.

4 / 5

Distinctiveness Conflict Risk

The 'Astro' niche is clear and distinct, with only minor overlap risk against related web framework skills like Next.js or SvelteKit.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.