Name: building-emdash-site
Rating: 68.8 (1 reviews)
Author: emdash-cms

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

82%

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

The canonical home for this skill is building-emdash-site in emdash-cms/emdash

Quality

Content

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

Well-structured, mostly lean content with strong progressive disclosure and actionable code, but the workflow's final 'verify' step lacks explicit validation for the database/migration/seed operations it performs.

Suggestions

Add an explicit verification checkpoint to step 6: after `pnpm dev`, instruct the reader to confirm the admin UI loads at http://localhost:4321/_emdash/admin and that seeded collections/pages appear, with a fix-and-retry loop if migrations or seed application fail.

Include a concrete success check for the seed step, e.g. querying a seeded collection from a page and confirming entries render, so the database operation has a feedback loop.

Tighten a few connective sentences (e.g. 'These are the things that silently break sites. Know them before you start.') to lift conciseness toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence (it never explains Astro or what a CMS is) and the API cheat sheet and gotchas earn their tokens, but a few connective phrases like 'Know them before you start' could be trimmed, keeping it just below the top anchor.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready code (imports, getEmDashCollection/getEmDashEntry signatures, UI components) and the `pnpm dev` command, but the common page patterns are deferred to references leaving minor gaps.	4 / 5
Workflow Clarity	The 6-step sequence is clearly numbered and each step points to a reference, but the 'Run and verify' step only describes automatic migration/seed behavior without explicit validation checkpoints for the database/seed operation, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	A clear overview body signals four one-level-deep references both in the numbered workflow and in the Reference Documents table, and all referenced files exist, matching the top anchor for well-signaled easy navigation.	5 / 5
	Total	16 / 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 does and when to use it, with useful boundary guidance against a related plugin-authoring skill. The only minor gap is slightly thinner natural-term/synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (EmDash CMS on Astro) and lists multiple concrete actions — 'schema and seeds, content queries, Portable Text rendering, menus, taxonomies, widgets, and deployment configuration' — for comprehensive coverage matching the anchor.	5 / 5
Completeness	Explicitly answers 'what' (build the site-facing parts including the enumerated features) and 'when' ('Use for EmDash site and theme work'), plus a boundary clause ('use creating-plugins instead when the task is plugin authoring alone'), matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural product/feature terms a user would say ('EmDash CMS', 'Astro', 'Portable Text', 'menus', 'taxonomies', 'site and theme work'), but a few natural synonyms or file extensions are absent, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Clear niche (EmDash on Astro) with the explicit disambiguation against the sibling creating-plugins skill, giving minimal conflict risk as the anchor describes.	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: templates/blog-cloudflare/.agents/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.