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

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.

The body is a high-quality, actionable CLI reference with strong command coverage and appropriate safety guidance for destructive operations. Its main gaps are minor Authentication-section redundancy and a referenced EDITING-FLOW.md that is not present in the bundle.

Suggestions

Consolidate the two 'Authentication' sections (the overview with the resolution-order list and the Quick Reference command block) into one to remove redundancy.

Ensure EDITING-FLOW.md ships alongside SKILL.md, or inline the essential editing-flow details (Portable Text conversion, _rev tokens, raw mode) so the reference is not broken.

Add a brief validate-and-retry note for schema/content mutations that can fail (e.g. re-run `schema get` to confirm a field was added/removed) to strengthen workflow feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly executable commands with terse inline comments, assuming Claude's competence; the only drag is minor redundancy (an 'Authentication' overview section and an 'Authentication' quick-reference block both cover login/whoami/logout).	4 / 5
Actionability	Nearly every section is copy-paste-ready `npx emdash` commands with real flags covering the common cases (list/get/create/update/delete, schema add-field, media upload, search, types), with realistic placeholder IDs and URLs.	5 / 5
Workflow Clarity	Destructive and bulk operations carry explicit validation guidance ('Resolve the current target with a read command before a destructive or bulk mutation' and 'Delete a collection after inspecting it and confirming the target' with a `schema get` before `schema delete`), and auth resolution is a clear numbered sequence; however there are no explicit error-recovery feedback loops.	4 / 5
Progressive Disclosure	Content is organized into clear sections and offloads editing-flow detail to a well-signaled one-level-deep reference (EDITING-FLOW.md), matching the good pattern; the score is held at 4 because the referenced file is not present in the bundle, leaving the link unverifiable.	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.

The description is specific, well-scoped, and highly distinctive, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness. Adding a trigger clause would lift it into the top tier.

Suggestions

Append an explicit trigger clause, e.g. 'Use when managing an EmDash CMS instance from the command line, or when the user mentions EmDash, content/schema/migrations, or generating CMS types.'

Replace the generic verbs 'inspect and manage' with more concrete actions (e.g. 'create, update, publish, and delete content; manage schema and taxonomies; run migrations; generate types') to strengthen specificity.

Add the synonym 'CMS' so the description matches users who refer to EmDash by category rather than product name.

Dimension	Reasoning	Score
Specificity	Names the domain ('EmDash CLI', 'command line') and enumerates a comprehensive set of capability areas (content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, generated types), though the action verbs themselves ('inspect and manage') are generic rather than each being a distinct concrete action.	4 / 5
Completeness	The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Good coverage of domain terms a user managing EmDash would naturally say (content, schema, media, taxonomies, migrations, types), but it lacks broader synonyms such as 'CMS' and has no explicit 'Use when...' trigger phrasing.	4 / 5
Distinctiveness Conflict Risk	'EmDash CLI' is a unique proper-noun niche with distinct triggers and minimal conflict risk against other skills; no other skill would plausibly match this description.	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: 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.