Name: emdash-cli
Rating: 64 (1 reviews)
Author: emdash-cms

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, and generated types.

Quality

76%

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 ./templates/blog-cloudflare/.agents/skills/emdash-cli/SKILL.md

The canonical home for this skill is emdash-cli in emdash-cms/emdash

Quality

Content

82%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 CLI reference with executable commands throughout, clear sequencing, and sensible progressive disclosure. The main gaps are a missing EDITING-FLOW.md bundle file (dangling reference) and the lack of explicit validate-retry feedback loops for destructive operations.

Suggestions

Add the missing ./EDITING-FLOW.md file referenced at the end of the body, or remove/inline the reference so navigation does not dead-end.

For destructive and batch operations (content delete, schema delete, schema remove-field), add an explicit validate-then-act or inspect-confirm-retry checkpoint pattern.

Resolve the duplicated 'Authentication' heading (a ## section and a ### under Quick Reference) to tighten structure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples with brief framing; it assumes Claude's competence and avoids explaining basic concepts, though the duplicated 'Authentication' heading and a few explanatory asides could be trimmed slightly.	4 / 5
Actionability	Dense copy-paste-ready executable commands across content, schema, media, search, taxonomy, menu, auth, and types, with flag-level specifics and pipe/jq examples covering the common cases.	5 / 5
Workflow Clarity	Sequencing is clear (e.g. the numbered auth-resolution priority) and destructive operations carry an explicit checkpoint ('Resolve the current target with a read command before a destructive or bulk mutation' and 'Delete a collection after inspecting it'), though explicit validate-fix-retry feedback loops are not spelled out.	4 / 5
Progressive Disclosure	Good section structure with a Quick Reference that correctly offloads deep editing-flow detail to a one-level-deep, clearly signaled reference (EDITING-FLOW.md); however that referenced file does not exist in the bundle, a minor navigation gap.	4 / 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 specific, well-scoped description that names a distinct tool and a broad capability surface in third-person voice. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs to inspect or manage an EmDash CMS instance from the command line, or mentions emdash/em CLI commands.'

Add a couple of natural synonyms users might say (e.g. 'CMS', 'content management') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('inspect and manage an EmDash instance') and enumerates a broad set of concrete capability areas ('content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, and generated types'), giving several specific actions with only minor gaps in granularity.	4 / 5
Completeness	It clearly answers 'what' (inspect and manage an EmDash instance from the CLI across the listed areas) but provides no explicit 'Use when...' trigger clause, capping completeness at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Includes natural domain terms a user managing EmDash would say ('content, schema, media, search, menus, migrations') plus 'CLI' / 'command line'; a few common synonyms or phrasings are missing, so it stops short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The named 'EmDash CLI' tool and its enumerated CMS command surface give it a clear niche with distinct triggers and minimal overlap risk with other skills.	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: templates/blog-cloudflare/.agents/skills/emdash-cli/SKILL.md
Commit: 9ca2de5

Reviewed: 3 hours 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.