creating-plugins

Create EmDash CMS plugins with hooks, storage, settings, admin UI, API routes, and Portable Text block types. Use this skill when asked to build, scaffold, or implement an EmDash plugin, or when creating plugin features like custom block types, admin pages, or content hooks.

Quality

86%

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

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable examples and a clean reference structure, though it is somewhat long with repeated descriptor examples and lacks an explicit validation checkpoint in the build workflow.

Suggestions

Consolidate the repeated descriptor examples (minimal, capabilities, complete) into a single canonical example to reduce length and redundancy.

Add an explicit validation step to the build flow — e.g., type-check or run `emdash plugin bundle` validation before declaring the plugin done — so the Output Checklist has a verification checkpoint.

Trim explanatory prose around the trusted/sandboxed table where it restates the table's contents.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly avoids explaining concepts Claude already knows, but it is lengthy and repeats the descriptor example across the minimal, capabilities, and complete-example sections, so it could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript examples, a complete package.json exports block, and copy-paste-ready CLI commands, meeting the top anchor for concrete guidance.	3 / 3
Workflow Clarity	The Output Checklist sequences deliverables and the Complete Example walks through a build, but there is no explicit validation or verification checkpoint in the main flow, so it sits below the top anchor.	2 / 3
Progressive Disclosure	A clear overview in SKILL.md points to seven well-signaled, one-level-deep reference files (all verified present), with details appropriately split out for easy navigation.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-rich, and explicitly pairs capabilities with a 'Use when' clause, all in third person. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "hooks, storage, settings, admin UI, API routes, and Portable Text block types" — rather than vague language, matching the top anchor.	3 / 3
Completeness	Clearly states what it does ("Create EmDash CMS plugins with...") and when to use it ("Use this skill when asked to build, scaffold, or implement..."), satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes natural phrases a user would say — "build, scaffold, or implement an EmDash plugin", "custom block types, admin pages, or content hooks" — giving good coverage of likely request terms.	3 / 3
Distinctiveness Conflict Risk	The niche is clearly scoped to "EmDash CMS plugins" with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: emdash-cms/emdash
Path: skills/creating-plugins/SKILL.md
Commit: 53dbf22

Reviewed: 8 days 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.