building-emdash-site

Build the site-facing parts of an EmDash CMS project on Astro, including schema and seeds, content queries, Portable Text rendering, menus, taxonomies, widgets, and deployment configuration. Use for EmDash site and theme work; use creating-plugins instead when the task is plugin authoring alone.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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.

A well-structured overview skill: lean gotchas, an actionable API cheat sheet, and a clear workflow pointing to four real one-level-deep references. Minor gains are possible by deduplicating the reference table and adding usage examples for the more opaque site-feature functions.

Suggestions

Drop or shrink the closing Reference Documents table since the same four links are already presented inline in the Workflow section.

Add brief usage examples for the listed site-feature imports (e.g., getTerm/getMenu/getWidgetArea) so the cheat sheet is fully copy-paste ready.

Add a light validation checkpoint in step 6 (e.g., confirm the admin UI loads and a seeded collection renders) so the verify step is more than just starting the dev server.

Dimension	Reasoning	Score
Conciseness	Mostly lean and well-targeted — gotchas, cheat sheet, and workflow assume Claude's competence and avoid explaining generic concepts — but the closing Reference Documents table duplicates the four links already given in the Workflow section, a minor redundancy that could be trimmed.	4 / 5
Actionability	Provides concrete, executable TypeScript signatures (e.g., getEmDashCollection with limit/cursor/orderBy) and a real command (pnpm dev), but a few common calls (getTerm, getMenu) are only listed as imports without usage examples.	4 / 5
Workflow Clarity	A clear six-step sequence (configure → schema → pages → features → seed → run and verify) with each step scoped to a reference file and a final verify step; not capped at 3 since the work is not destructive/batch, though explicit validation checkpoints beyond "pnpm dev" are thin.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references to four real files (configuration.md, schema-and-seed.md, querying-and-rendering.md, site-features.md, all present), appropriately split and easy to navigate via both the workflow and the summary table.	5 / 5
	Total	17 / 20 Passed

Description

92%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.

A strong, specific description that clearly states what the skill builds and when to use it, with a helpful negative boundary against plugin work. Trigger-term coverage is good but lacks synonyms or file extensions that would push it to the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "schema and seeds, content queries, Portable Text rendering, menus, taxonomies, widgets, and deployment configuration" — giving comprehensive coverage of the build surface.	5 / 5
Completeness	Explicitly answers what ("Build the site-facing parts of an EmDash CMS project on Astro, including...") and when ("Use for EmDash site and theme work"), plus a negative boundary ("use creating-plugins instead when the task is plugin authoring alone").	5 / 5
Trigger Term Quality	Natural domain keywords are present ("EmDash CMS", "Astro", "site and theme work", "schema and seeds", "Portable Text"), but no synonyms or file extensions are included, so it stops short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (EmDash on Astro) with distinct triggers and an explicit disambiguation against the sibling creating-plugins skill, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: emdash-cms/emdash
Path: skills/building-emdash-site/SKILL.md
Commit: 9ca2de5

Reviewed: 3 hours ago

Table of Contents

Discovery Implementation Validation

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.