CtrlK
BlogDocsLog inGet started
Tessl Logo

building-emdash-site

Build and customize EmDash CMS sites on Astro. Use when creating pages, defining collections, writing seed files, querying content, rendering Portable Text, setting up menus/taxonomies/widgets, configuring deployment, or any task involving an EmDash-powered Astro site. Assumes basic Astro knowledge but provides all EmDash-specific patterns.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A well-structured, token-efficient body that leads with high-signal EmDash-specific gotchas, gives an actionable API cheat sheet, sequences a six-step build workflow ending in verification, and cleanly delegates detail to verified one-level-deep references. It avoids explaining concepts Claude already knows.

DimensionReasoningScore

Conciseness

Lean and efficient: it skips concepts Claude already knows (no "what a CMS/Astro is") and opens with EmDash-specific facts, while the gotchas and API cheat sheet are high-signal and well-commented rather than padded, so every token earns its place.

3 / 3

Actionability

Provides copy-paste-ready guidance: exact gotcha fixes (e.g. `<Image image={post.data.featured_image} /> from "emdash/ui"`), executable TypeScript query/import patterns, and the concrete `npx emdash dev` command, matching the fully-executable anchor.

3 / 3

Workflow Clarity

A clearly numbered 1–6 sequence ends in an explicit "Run and verify" step (`npx emdash dev` runs migrations, seeds, and type generation), and the "Common Gotchas" section functions as a proactive error-prevention checklist; this is not a destructive/batch context so the missing recovery loop does not cap the score.

3 / 3

Progressive Disclosure

A clear overview points to four real, one-level-deep reference files, each signaled in the Workflow steps and summarized in a bottom navigation table, with detail appropriately split out rather than inlined — a textbook match for the well-signaled one-level-deep anchor.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong, third-person description that states a precise niche, lists many concrete capabilities, and provides an explicit multi-trigger "Use when" clause. It is concise yet complete with no vague fluff.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — "creating pages, defining collections, writing seed files, querying content, rendering Portable Text, setting up menus/taxonomies/widgets, configuring deployment" — matching the anchor that lists several specific actions rather than vague language.

3 / 3

Completeness

Explicitly states what it does ("Build and customize EmDash CMS sites on Astro") and when to use it via an explicit "Use when..." clause with multiple triggers, satisfying both halves; not capped at 2 because the trigger clause is present.

3 / 3

Trigger Term Quality

Covers natural phrases users would actually say ("creating pages", "writing seed files", "querying content", "menus", "taxonomies", "widgets", "deployment") alongside the domain name, giving good coverage rather than just technical jargon.

3 / 3

Distinctiveness Conflict Risk

The narrow niche "EmDash CMS sites on Astro" with EmDash-specific trigger terms makes it clearly distinguishable and unlikely to fire for the wrong skill, matching the clear-niche anchor.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
emdash-cms/emdash
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.