CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a well-structured overview that leads with high-value, non-obvious gotchas, provides copy-paste-ready API guidance, and cleanly delegates depth to four well-signaled one-level-deep references. The only refinements are removing the duplicated reference table and adding an explicit error-recovery loop to the run-and-verify step.

DimensionReasoningScore

Conciseness

The body is dense with EmDash-specific, non-inferable knowledge ('Image fields are objects, not strings', 'entry.id vs entry.data.id are different things', cacheHint registration) and explains nothing Claude already knows. It is not 5 because the Reference Documents table repeats the same four links and content summaries already given in the workflow steps, and the plugin use-case bullets add mild padding; not 3 because nearly every line is high-value and non--generic.

4 / 5

Actionability

The cheat sheet gives copy-paste-ready code with real imports and destructured return shapes ('const { entries, nextCursor, cacheHint } = await getEmDashCollection("posts", {...})'), gotcha #1 shows the exact wrong-vs-right fix ('Use <Image image={post.data.featured_image} /> from "emdash/ui"'), and there are concrete commands (pnpm dev) and URLs (http://localhost:4321/_emdash/admin). It is not 4 because the executable snippets cover the common cases directly; deeper patterns are appropriately delegated rather than missing.

5 / 5

Workflow Clarity

A clear six-step sequence (configure → schema → pages → features → seed → run and verify) with a verify step describing expected startup behavior (migrations, seed application, type generation). It is not 5 because there are no explicit feedback loops or error-recovery checkpoints (no validate → fix → retry guidance in step 6); not 3 because a run-and-verify step with concrete expectations is present and the sequence is unambiguous.

4 / 5

Progressive Disclosure

The body is a true overview (5 gotchas, file structure, cheat sheet) and delegates detail to four real, one-level-deep reference files, each linked from its workflow step with a content summary and indexed again in a navigation table; verified the references only cross-link siblings and external docs, with no nested chains. It is not 4 because the split and signaling are clean: every reference is discoverable, purpose-labeled, and shallow.

5 / 5

Total

18

/

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.

The description is strong: concrete, comprehensive capability listing in third person, an explicit 'Use for' trigger clause, and explicit boundary routing to the creating-plugins skill. The only minor gap is trigger-term coverage, which is domain-thorough but stops short of synonym- and file-extension-level breadth.

DimensionReasoningScore

Specificity

Quotes 'schema and seeds, content queries, Portable Text rendering, menus, taxonomies, widgets, and deployment configuration' — seven concrete capabilities plus the framing action 'Build the site-facing parts of an EmDash CMS project on Astro', matching the comprehensive multi-action anchor. It is not 4 because coverage spans the full scope of site work with no meaningful gaps.

5 / 5

Completeness

Explicitly answers both: what — 'Build the site-facing parts of an EmDash CMS project... including schema and seeds...' — and when — 'Use for EmDash site and theme work; use creating-plugins instead when the task is plugin authoring alone'. It is not 4 because the when-clause is explicit with concrete triggers plus disambiguation, matching the clearly-explicit-both anchor.

5 / 5

Trigger Term Quality

Natural terms users would say are well covered: 'EmDash', 'CMS', 'Astro', 'site', 'theme', 'schema', 'seeds', 'taxonomies', 'widgets', matching 'good keyword coverage; a few natural terms missing'. It is not 5 because it lacks synonym/variation-level coverage (e.g., 'content', 'pages', 'blog', file names like seed.json or astro.config.mjs); not 3 because the domain keywords present are exactly what a user working in this niche would say.

4 / 5

Distinctiveness Conflict Risk

Clear niche (EmDash CMS on Astro) with distinct triggers, and it actively routes the nearest competing case away: 'use creating-plugins instead when the task is plugin authoring alone'. It is not 4 because it does more than minimize overlap — it explicitly disambiguates against the most closely related skill.

5 / 5

Total

19

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

emdash-cms/emdash

Path

skills/building-emdash-site/SKILL.md

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.