CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

emdash-cli

Use the EmDash CLI to inspect and manage an EmDash instance from the command line, including content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, generated types, and whole-site export and import.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 an excellent executable CLI reference with strong validation discipline around destructive and bulk operations (read-before-write, rev tokens, plan-digest confirmation for site imports). Its main defects are a broken reference to a missing EDITING-FLOW.md and a redundant duplicate explanation of auto-publishing across two sections.

Suggestions

Add the referenced EDITING-FLOW.md to the skill bundle (or inline its essential details on Portable Text conversion, _rev tokens, and raw mode), since the link currently points to a nonexistent file.

Consolidate the auto-publish explanation: state it once, either in 'Content CRUD' or in 'Drafts and Publishing', rather than repeating it in both sections.

Consider moving the long 'Site Export and Import' prose (scope rules, exit codes, principal-mapping semantics) into a reference file to further slim the main SKILL.md once bundle files exist.

DimensionReasoningScore

Conciseness

The body is dense, comment-annotated, copy-paste command blocks with almost no explanation of concepts Claude already knows. Minor redundancy: auto-publish behavior is explained in 'Content CRUD' ('Create and update auto-publish by default so agents get read-after-write consistency') and again in a dedicated 'Drafts and Publishing' section, so it is not a 5; there is no padding or over-explanation that would drop it to 3.

4 / 5

Actionability

Every section provides fully executable commands (e.g., 'npx emdash content create posts --data ...', 'npx emdash site import site.emdash --url ... --analyze') covering the common cases for each command group, including exit codes ('exits 2 when the plan has blockers'), error codes ('INSUFFICIENT_SCOPE'), and required token scopes. This matches 'fully executable; copy-paste ready; specific examples cover the common cases'.

5 / 5

Workflow Clarity

Destructive and bulk operations have explicit validation checkpoints: 'Resolve the current target with a read command before a destructive or bulk mutation', '--rev from a prior get' for updates, and a two-step site import (analyze, review plan and digest, then '--confirm') requiring user confirmation, with failure feedback (exit codes 1/2, status/resume/cancel/abandon). Validation is present, so the destructive-operation cap of 3 does not apply.

5 / 5

Progressive Disclosure

Section structure is good and there is exactly one clearly signaled, one-level-deep reference ('see [EDITING-FLOW.md](./EDITING-FLOW.md)'), but the referenced file does not exist in the bundle, so the reference is broken and the promised detail is unreachable. This is more than the 'minor organization gaps' of a 4, but structure is solid and the reference is not buried, so it is above 2.

3 / 5

Total

17

/

20

Passed

Description

70%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 concrete and highly distinctive thanks to naming the EmDash product and enumerating its management domains, but it omits any explicit 'when to use this' trigger guidance, which caps completeness. Adding a 'Use when...' clause with natural trigger phrases would raise both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user mentions EmDash, wants to manage CMS content/schema/media from the terminal, or needs to export or import an EmDash site.'

Replace the generic verb 'manage' with a few concrete per-domain actions (e.g., 'create, update, and publish content; modify collections and fields') to sharpen specificity.

Include one or two natural user phrasings such as 'back up a site' or 'log in to EmDash' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Explicit actions include 'inspect and manage' an EmDash instance plus 'whole-site export and import', and the enumerated object list ('content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, generated types') gives concrete coverage. It falls short of 5 because the main verb 'manage' is generic and specific per-domain actions (create, update, delete) are not stated; it exceeds 3 because coverage goes well beyond 1-2 concrete actions.

4 / 5

Completeness

The 'what' is clear and concrete (inspect and manage an EmDash instance with enumerated areas), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. It is not 2 because the 'what' is explicit rather than vague.

3 / 5

Trigger Term Quality

Contains natural terms a user would say: 'EmDash CLI', 'command line', 'content', 'schema', 'media', 'search', 'export and import', 'migrations'. A few natural variations are missing (e.g., 'CMS', 'back up a site', 'login'), so it matches 'good keyword coverage; a few natural terms missing' rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'EmDash' is a specific named product with a distinct CLI, giving it a clear niche with minimal conflict risk against generic skills. It clearly matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

emdash-cms/emdash

Path

skills/emdash-cli/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.