CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

An exemplar overview skill: lean, host-specific, and actionable, with a complete copy-paste scaffold example and a well-organized one-level-deep reference bundle covering every API area. The only gap is the absence of an explicit error-recovery loop in the testing workflow.

DimensionReasoningScore

Conciseness

The body is dense with host-specific constraints ('Sandboxed runtime code can use Web APIs but not Node.js built-ins', 'decoded request/response bodies limited to 8 MiB') and explains nothing Claude already knows. Every sentence carries non-obvious, EmDash-specific information, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It provides copy-paste ready scaffold commands ('pnpm dlx @emdash-cms/plugin-cli init my-plugin'), a complete executable src/plugin.ts example, exact capability identifiers, named test hosts (createPluginTestHost(), createPluginRuntimeTestHost()), and concrete test helpers (host.http.respond(), host.http.requests()). Specific guidance covers the common cases, satisfying anchor 5.

5 / 5

Workflow Clarity

A clear sequence runs choose format → scaffold → declare access → routes/hooks/admin UI → test, with an explicit testing section that maps each test host to the concerns it covers. It sits at anchor 4 rather than 5 because there is no explicit validate → fix → re-run feedback loop or checkpoint ordering within the test workflow itself.

4 / 5

Progressive Disclosure

The body is a concise overview and all 12 detail files live one level deep in ./references/, each clearly signaled inline with descriptive link text ('Read [Hooks](./references/hooks.md)') plus a consolidated References index; all referenced paths exist in the bundle. This matches anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

19

/

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: third-person, concise, and specific, naming the domain's full capability set and an explicit 'Use when' trigger clause. The only minor weakness is limited synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

The description enumerates the full plugin surface — 'sandboxed hooks, routes, storage, content and media APIs, MCP tools, and declarative admin UI, or native React and Astro extensions' — multiple concrete capabilities with comprehensive coverage. It sits at anchor 5 rather than 4 because there are no meaningful coverage gaps within its domain.

5 / 5

Completeness

It explicitly answers both questions: the 'what' ('Create EmDash CMS plugins with sandboxed hooks, routes, storage, content and media APIs, MCP tools, and declarative admin UI...') and the 'when' ('Use when scaffolding or implementing an EmDash plugin') with a concrete trigger phrase. This matches the anchor-5 pattern of the good examples, and is above anchor 4 because the 'when' clause is explicit rather than merely implied or generic.

5 / 5

Trigger Term Quality

Natural phrases like 'scaffolding or implementing an EmDash plugin', 'extensions', and 'hooks' are present and would be said by a user needing this skill. It falls short of anchor 5 because common synonyms such as 'build', 'develop', or 'add a plugin' are absent, leaving a few natural trigger variations uncovered.

4 / 5

Distinctiveness Conflict Risk

The EmDash CMS niche is highly specific with distinct triggers ('EmDash plugin', 'EmDash CMS'), so the risk of firing for an unrelated skill is minimal. It clearly matches anchor 5's 'clear niche with distinct triggers'.

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/creating-plugins/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.