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.

A highly actionable, well-guarded CLI reference whose destructive and bulk workflows are exemplary (analyze/confirm digests, exit codes, resume paths). Its two weaknesses are a broken reference to a missing EDITING-FLOW.md and duplicated authentication coverage that wastes tokens.

Suggestions

Fix the dangling reference: either include EDITING-FLOW.md in the bundle or remove/inline the pointer in the "Editing Flow" section.

Merge the two Authentication sections ("## Authentication" and "### Authentication" under Quick Reference) into one to remove redundancy and save tokens.

Tighten the long site-import prose paragraph into a short bulleted list of exit codes, scope requirements, and safety rules for faster scanning.

DimensionReasoningScore

Conciseness

The body is dense with commented, executable command blocks and assumes Claude's competence without explaining known concepts. It falls short of 5 due to redundancy: authentication is covered twice ("## Authentication" and "### Authentication" under Quick Reference) and some prose in the site import section could be tightened.

4 / 5

Actionability

Nearly every section is copy-paste-ready `npx emdash` commands covering the common cases — list/get/create/update/delete with concrete flags, media upload with real arguments, jq piping for JSON output, and the two-phase site import with digests and follow-up commands. Only two illustrative lines use ellipsis placeholders, which is acceptable.

5 / 5

Workflow Clarity

Risky and bulk operations have explicit validation and feedback loops: "Resolve the current target with a read command before a destructive or bulk mutation", schema inspection before delete, the site import sequence of `--analyze` -> reviewed plan digest -> `--confirm`, documented exit codes (2 for blockers, 1 for failed imports), resume/cancel/abandon recovery, and `receiptDigestValid: true` as the completion checkpoint.

5 / 5

Progressive Disclosure

The body is well organized into clear sections and appropriately inlines command reference, but its single external reference — "see [EDITING-FLOW.md](./EDITING-FLOW.md)" — points to a file that is not present in the bundle, breaking navigation. That dangling reference keeps it at 3 rather than 4.

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.

A strong, specific description that clearly communicates what the skill does across a broad but concrete capability surface, held back by the complete absence of any "when to use" trigger guidance. Adding a trigger clause would also lift its usefulness for skill selection.

Suggestions

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

Vary the verbs beyond "inspect and manage" to name distinct actions (create, update, migrate, upload, export, import) for each capability area.

Include natural synonyms such as "CMS" or the ".emdash" directory to broaden trigger term coverage.

DimensionReasoningScore

Specificity

The description enumerates a comprehensive set of capability areas ("content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, generated types, and whole-site export and import"), but the only verbs are the generic pair "inspect and manage", so it lists several specific capabilities with minor gaps rather than the multiple distinct concrete actions of a 5.

4 / 5

Completeness

The "what" is clearly stated, but there is no "Use when..." clause or any equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage anchored by the distinctive product name "EmDash" plus terms like "CLI", "command line", "export", "import", "search", and "migrations". It is not a 5 because common variations such as "CMS", "headless", or file extensions like ".emdash" are absent.

4 / 5

Distinctiveness Conflict Risk

"EmDash CLI" names a distinct product with clear niche triggers; it is unlikely to fire for an unrelated skill, matching the minimal-conflict 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

templates/blog/.agents/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.