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

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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, highly actionable skill body with executable examples and clean progressive disclosure via real reference files. The main improvement is de-duplicating the capabilities example and adding an explicit verification step.

Suggestions

Remove the duplicate capabilities descriptor example in the 'Plugin Context' section — it repeats the one already shown under 'Capabilities'.

Add an explicit validation/test checkpoint to the build flow (e.g., 'Run the plugin locally in trusted mode and verify the hook fires before publishing').

Tighten the 'Trusted vs Sandboxed' comparison prose where it restates points already covered by the table.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the capabilities descriptor example is duplicated (see the Capabilities section and Plugin Context section) and some prose could be trimmed.	4 / 5
Actionability	Provides complete, copy-paste-ready TypeScript examples for the minimal plugin and a full hooks/routes/storage example, plus package.json exports and CLI commands covering common cases.	5 / 5
Workflow Clarity	Clear sequence from descriptor/definition anatomy through minimal example to an Output Checklist, but lacks an explicit test or validate→fix→retry checkpoint for the build flow.	4 / 5
Progressive Disclosure	A clear overview with seven well-signaled one-level-deep references (hooks, storage, admin-ui, api-routes, block-kit, portable-text-blocks, publishing), all of which exist as real files in ./references/.	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, third-person description that names concrete capabilities and provides explicit trigger guidance. Minor room to add synonyms or file extensions for trigger-term breadth.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'hooks, storage, settings, admin UI, API routes, and Portable Text block types' — giving comprehensive coverage of the plugin surface area.	5 / 5
Completeness	Explicitly answers 'what' (first sentence naming features) and 'when' with a clear 'Use this skill when...' clause and concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('build, scaffold, or implement an EmDash plugin', 'custom block types, admin pages, or content hooks') but offers few synonyms or file/extension variants.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'EmDash CMS plugins' with domain-specific triggers, creating a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 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: 1717d31

Reviewed: 2 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.