wordpress-plugin-to-emdash

Port a WordPress plugin to EmDash CMS. Use this skill when asked to migrate, convert, or port a WordPress plugin, theme functionality, or custom post type to EmDash. Provides concept mapping and implementation patterns.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/wordpress-plugin-to-emdash/SKILL.md

Quality

Content

68%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, actionable porting reference with concrete code and tight mapping tables that assume Claude's competence. The weakest area is workflow clarity: the migration sequence lacks an explicit, concrete validation/verification checkpoint.

Suggestions

Add a concrete verification step to the Migration Approach, e.g. 'Test behaviour: run the ported plugin and confirm output matches the original WordPress plugin for representative inputs; fix and re-test until parity holds.'

Fully render the YouTube.astro example instead of leaving the iframe as a comment, so the shortcode-to-Portable-Text pattern is copy-paste ready.

Consider moving the eight Concept Mapping tables into a references/ file (e.g. CONCEPT-MAP.md) with a concise summary inline, reducing SKILL.md body length while preserving the mapping detail.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material with no padding about concepts Claude already knows (no 'what is WordPress' filler), every table row earning its place; it is efficient though the sheer volume of inline mapping tables could be trimmed or split out.	4 / 5
Actionability	Concrete, mostly executable TypeScript/JSON examples cover the common cases (options API, storage collections, querying, menus, widgets, seed.json) with specific EmDash API names, but the YouTube Astro render component is left as a commented sketch — a minor gap.	4 / 5
Workflow Clarity	A clear 5-step Migration Approach and Output Format structure exist, but the only verification step ('Test behaviour — Same result, different implementation') is implicit and non-concrete with no explicit validation checkpoint or feedback loop.	3 / 5
Progressive Disclosure	Good section structure with clear, well-signaled cross-references to the creating-plugins skill for general implementation details, keeping this skill focused on porting-specific mapping; the main gap is that the bulk mapping tables are inline with no separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

82%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 with explicit what/when structure, natural trigger synonyms, and a clear distinct niche. The only weakness is that the named actions collapse to a single porting operation rather than a comprehensive set of distinct capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain ('Port a WordPress plugin to EmDash CMS') and concrete actions ('concept mapping and implementation patterns'), but 'migrate, convert, or port' are synonyms for a single action rather than several distinct capabilities, so coverage is not comprehensive.	3 / 5
Completeness	It explicitly states both what ('Port a WordPress plugin to EmDash CMS... Provides concept mapping and implementation patterns') and when ('Use this skill when asked to migrate, convert, or port...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases are present and varied ('migrate, convert, or port a WordPress plugin, theme functionality, or custom post type'), giving good synonym coverage, though a few natural phrasings (e.g. 'rebuild for EmDash', 'WordPress to EmDash') are absent.	4 / 5
Distinctiveness Conflict Risk	The WordPress-to-EmDash porting niche is highly specific with distinct triggers, creating minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/wordpress-plugin-to-emdash/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.