emdash-cli

Use the EmDash CLI to manage content, schema, media, and more. Use this skill when you need to interact with a running EmDash instance from the command line — creating content, managing collections, uploading media, generating types, or scripting CMS operations.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

65%Weight 40%Scale 1-3

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-organized CLI reference with executable commands throughout. It loses points for duplicated auth/drafts content, missing verification steps on destructive operations, and a broken reference to a non-existent EDITING-FLOW.md file.

Suggestions

Create the referenced ./EDITING-FLOW.md (or remove the link) so the one progressive-disclosure pointer resolves to a real file.

De-duplicate the Authentication material — keep the resolution-order explanation in one place and reference it from the Quick Reference instead of restating the commands.

Add a brief verification step for destructive/batch operations (e.g. `content get` to confirm before `content delete`, or note that `delete` is reversible via `restore`).

Dimension	Reasoning	Score
Conciseness	The body is mostly an efficient, code-heavy command reference with no basic-concept padding, but "Authentication" is duplicated as both a top-level section and a Quick Reference subsection, and the auto-publish behavior is restated in inline comments and again in the "Drafts and Publishing" section, so it could be tightened — matching anchor 2 rather than 3.	2 / 3
Actionability	The body is dominated by fully executable `npx emdash ...` commands with flags, inline comments, and concrete examples (e.g. `content create posts --data '{...}'`, `media upload ./photo.jpg --alt "A sunset"`), all copy-paste ready.	3 / 3
Workflow Clarity	Some sequences are enumerated (auth resolution order 1–4, cloudflared flow 1–3), but destructive operations (`content delete`, `schema delete --force`) have no verification step and the core editing workflow is deferred to a reference file, capping the score at 2 per the rubric's destructive-operations rule.	2 / 3
Progressive Disclosure	Sections are well organized, but the sole external reference — "see EDITING-FLOW.md" — points to a file that does not exist in the bundle, and the ~245-line inline command reference could itself be split into a separate reference file; this matches anchor 2 rather than a clean one-level-deep structure.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 that clearly states capabilities and provides an explicit trigger clause tied to a specific product niche. The only issue is second-person voice ("you need") in the trigger clause, which the rubric penalizes on specificity.

Suggestions

Rephrase the trigger clause in third person to avoid the voice penalty, e.g. "Use this skill to interact with a running EmDash instance from the command line — creating content, managing collections, uploading media, generating types, or scripting CMS operations."

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("creating content, managing collections, uploading media, generating types, or scripting CMS operations"), which matches the anchor-3 example, but the second-person phrasing "when you need to interact" triggers the rubric's voice penalty, reducing the score by one to 2.	2 / 3
Completeness	Explicitly answers both "what" ("manage content, schema, media, and more") and "when" with a clear trigger clause ("Use this skill when you need to interact with a running EmDash instance"), satisfying the anchor-3 requirement.	3 / 3
Trigger Term Quality	Covers natural terms a user would say when managing a CMS — "create content", "upload media", "generate types", "manage collections", "scripting CMS operations", "command line" — matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Tied to a specific named product ("running EmDash instance") with distinct CMS-operation triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: 53dbf22

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