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.

72

Quality

91%

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

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

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.

A well-structured skill body: high-value gotchas, executable code, a clear stepwise workflow, and clean one-level progressive disclosure verified against the actual reference files. The only improvements are minor — slightly tighter plugin section and explicit verification checkpoints in the workflow.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — the gotchas are non-obvious failure modes ('renders [object Object]', 'silent empty results') rather than explanations of known concepts. Minor trimming is possible in the Plugins section, whose bullet list of plugin use-cases partially duplicates the pointer to the creating-plugins skill.

4 / 5

Actionability

Guidance is copy-paste ready: exact API calls with signatures ('getEmDashCollection("posts", { limit: 10, cursor, orderBy: { published_at: "desc" } })'), the correct component usage ('<Image image={post.data.featured_image} />'), the dev command, and a full import cheat sheet covering the common cases.

5 / 5

Workflow Clarity

The six-step workflow (configure, design schema, build pages, wire features, create seed, run and verify) is clearly sequenced with each step mapped to a reference file, and step 6 explains expected startup behavior. It falls short of anchor 5 because there are no explicit validation checkpoints or error-recovery loops (e.g., what to check if pages render empty).

4 / 5

Progressive Disclosure

The body is a genuine overview: gotchas, structure, and a cheat sheet inline, with all detail delegated via well-signaled one-level-deep links ('Read references/schema-and-seed.md for...') to four reference files that all exist in the bundle, plus a closing reference table for navigation.

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.

A strong description: concrete, comprehensive, third-person, with an explicit trigger clause and explicit boundary guidance against a sibling plugin-authoring skill. The only gap is modest synonym coverage in its trigger terms.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities — 'schema and seeds, content queries, Portable Text rendering, menus, taxonomies, widgets, and deployment configuration' — giving comprehensive coverage of the skill's scope with no vague filler.

5 / 5

Completeness

It explicitly answers both questions: 'what' via the capability list and 'when' via the concrete trigger clause 'Use for EmDash site and theme work'. This clearly matches the anchor-5 example pattern of capability list plus explicit 'Use when...' phrasing.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('EmDash site and theme work', 'CMS', 'Astro', 'schema', 'menus', 'taxonomies', 'widgets') that users of this stack would actually say, though common synonyms like 'template', 'frontend', or 'content collections' are missing. It sits above anchor 3 (missing common variations) but below anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (EmDash on Astro) and even adds negative-scope guidance — 'use creating-plugins instead when the task is plugin authoring alone' — which actively prevents collision with the most likely competing skill. Conflict risk is minimal.

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

templates/blank/.agents/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.