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

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/emdash-cli/SKILL.md

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 strong, highly actionable CLI reference with exemplary validation-gated workflows for destructive and bulk operations (rev tokens, import plan digests, exit codes, resume/cancel paths). The weaknesses are minor redundancy around auto-publish and a progressive-disclosure shortfall: the command reference is monolithic and its sole external reference is a missing file.

Suggestions

Ship the referenced EDITING-FLOW.md in the bundle (or remove the link) — the body's only external reference currently points to a nonexistent file.

Move the per-command quick reference (schema, media, taxonomy, menus) into a one-level-deep reference file, keeping SKILL.md as an overview with authentication, workflows, and pointers.

Deduplicate the auto-publish behavior between the Content CRUD comments and the "Drafts and Publishing" section, and break the dense site-import paragraph into a short checklist.

Dimension	Reasoning	Score
Conciseness	The body is dense, comment-annotated, copy-paste command blocks with no padding about concepts Claude already knows. Minor over-explanation remains: auto-publish behavior is explained twice (inline in Content CRUD and again in the "Drafts and Publishing" section) and the site import paragraph is long, so it falls short of the lean anchor.	4 / 5
Actionability	Every section provides fully executable, copy-paste-ready `npx emdash ...` commands with realistic flags, IDs, and outputs (e.g. `--rev MToyMDI2...`, `--map-principal editor@example.com=editor@example.com`), covering the common cases for each command group.	5 / 5
Workflow Clarity	Multi-step processes are explicitly sequenced with validation checkpoints: the import flow runs analyze → show the user the plan and digest → `--confirm` → status/resume/receipt, with documented exit codes; destructive operations are guarded by read-before-mutate guidance, `--rev` tokens from a prior get, and schema inspection before delete, so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	Section headers and a quick-reference layout give reasonable structure, but the ~260-line full command reference is inlined in SKILL.md rather than split out, and the body's only external reference — [EDITING-FLOW.md](./EDITING-FLOW.md) — does not exist in the bundle (no references/ directory is present), leaving a broken pointer.	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 clear, well-scoped description that enumerates the CLI's capability surface comprehensively and is highly distinct thanks to the product name. Its main weakness is the absence of any explicit "Use when..." trigger guidance, which both caps completeness and slightly weakens trigger-term quality.

Suggestions

Add a trigger clause, e.g. "Use when the user mentions EmDash, an EmDash CMS instance, or asks to manage content, schema, or site export/import from the command line."

Include natural synonyms users would say — "CMS", ".emdash", "site package" — alongside the existing domain terms.

Replace the generic verbs "inspect and manage" with a few concrete action phrases (e.g. "list and edit content", "add schema fields", "upload media") to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete capability areas ("content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, generated types, and whole-site export and import"), but the verbs remain generic ("inspect and manage") rather than naming distinct concrete actions, which keeps it below the comprehensive anchor.	4 / 5
Completeness	The "what" is clear and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Good coverage of natural domain terms a user would say ("EmDash CLI", "content", "schema", "search", "export and import", "migrations"), but a few natural terms and synonyms are missing ("CMS", ".emdash", "site package"), so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The named product ("EmDash CLI... EmDash instance") carves out a clear niche with distinct triggers and minimal risk of firing for the wrong skill.	5 / 5
	Total	16 / 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: emdash-cms/emdash
Path: skills/emdash-cli/SKILL.md
Commit: 0e8977c

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