creating-plugins

Create EmDash CMS plugins with sandboxed hooks, routes, storage, content and media APIs, MCP tools, and declarative admin UI, or native React and Astro extensions. Use when scaffolding or implementing an EmDash plugin.

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.

The body is a well-structured, lean overview with strong progressive disclosure and good executable scaffolding. Weakest spots are the inlined capabilities table (conciseness) and the lack of an explicit validate-fix-retry loop and a full worked example (workflow clarity / actionability).

Suggestions

Move the large emdash-plugin.jsonc capabilities table into a dedicated reference file (e.g. references/capabilities.md) and keep only a short summary inline, to tighten the main SKILL.md and lift conciseness.

Add an explicit validate→fix→retry loop in the 'Test the production boundary' section (run test host, inspect failure, fix, re-run) — especially for content:write / content:publish paths — to raise workflow clarity.

Include one compact end-to-end worked example (scaffold → declare access → add a hook → run the test host) inline so the common case is fully actionable without jumping to references.

Dimension	Reasoning	Score
Conciseness	Body is dense and assumes Claude's intelligence (no 'what is a CMS/plugin' padding), with every section earning its place. Not a 5 because the large inlined capabilities table (~25 rows) is reference material that could live in a reference file; not a 3 because there is no noticeable verbosity or unnecessary explanation.	4 / 5
Actionability	Provides copy-paste-ready scaffold commands ('pnpm dlx @emdash-cms/plugin-cli init my-plugin') and a complete TypeScript plugin example plus concrete test-host function names. Not a 5 because most feature sections (hooks, routes, admin UI) point to references rather than giving inline executable examples for the common cases.	4 / 5
Workflow Clarity	There is a clear build sequence (choose format → scaffold → declare access → implement features → test the production boundary) with checkpoints like 'pnpm run test' and a dedicated boundary-test section. Not a 5 because no explicit validate→fix→retry feedback loop is shown; not a 3 because verification steps are present, so the destructive-operation cap does not apply.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references (e.g. 'Read [Hooks](./references/hooks.md)') and a consolidated References list; all 12 referenced files exist in ./references/. Matches the score-5 anchor for clear overview with easy navigation and content appropriately split.	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.

The description is strong: third-person voice, explicit what-and-when, and a comprehensive, concrete capability list tied to a distinct product niche. The only minor gap is trigger-term synonym breadth.

Dimension	Reasoning	Score
Specificity	Quotes 'sandboxed hooks, routes, storage, content and media APIs, MCP tools, and declarative admin UI, or native React and Astro extensions' — a comprehensive list of concrete plugin capabilities, matching the score-5 anchor 'lists multiple specific concrete actions; comprehensive coverage'. Not a 4 because coverage is broad and specific rather than having minor gaps.	5 / 5
Completeness	Explicitly answers what ('Create EmDash CMS plugins with …') and when ('Use when scaffolding or implementing an EmDash plugin') with a concrete trigger clause. Matches the score-5 anchor for both what and when; not a 4 because the when is explicit and specific rather than weakly implied.	5 / 5
Trigger Term Quality	Quotes 'scaffolding or implementing an EmDash plugin' plus 'Create EmDash CMS plugins' — good natural domain terms a user would say. Not a 5 because there is limited synonym variation and no file-extension/CLI-style triggers; not a 3 because the natural phrases are present and relevant.	4 / 5
Distinctiveness Conflict Risk	The 'EmDash CMS' niche is highly specific with distinct triggers ('EmDash plugin', 'scaffold', 'native React and Astro extensions'), giving minimal conflict risk with other skills. Matches the score-5 'clear niche with distinct triggers' anchor.	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/creating-plugins/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.