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/blank/.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 well-organized, highly actionable CLI reference with appropriate validation guidance for destructive operations and a clean progressive-disclosure pointer, held back only by minor redundancy, lack of explicit feedback loops, and a missing referenced file.

Suggestions

Consolidate the two Authentication sections (the standalone one and the Quick Reference one) to remove redundancy and tighten conciseness.

Add an explicit validate→fix→retry feedback loop for at least one destructive or batch workflow (e.g., schema delete: get → confirm target → delete → re-list to verify) to reach 5 on workflow clarity.

Either provide the referenced ./EDITING-FLOW.md in the bundle or remove the dangling link so progressive disclosure is fully sound.

Dimension	Reasoning	Score
Conciseness	The body is a lean, mostly executable command reference with relevant, non-padded prose (auth precedence, auto-publish behavior); minor redundancy such as two Authentication sections keeps it just below the 5 anchor.	4 / 5
Actionability	Copy-paste-ready `npx emdash …` commands with concrete flags cover the common cases across content CRUD, schema, media, search, taxonomy, menus, types, and auth, matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	Validation guidance is present for destructive/batch ops ('Resolve the current target with a read command before a destructive or bulk mutation', inspect-before-delete, --rev requirement), avoiding the 3 cap, but there are no explicit validate→fix→retry feedback loops, so it stays at 4.	4 / 5
Progressive Disclosure	Clear sectioned structure with a well-signaled one-level-deep reference (EDITING-FLOW.md) for editing-flow detail; the referenced file is not present in the bundle, a minor organization gap that holds it below 5.	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, product-scoped description with strong distinctiveness and broad capability coverage, weakened by the absence of an explicit 'when to use' trigger clause and only generic action verbs.

Suggestions

Append a 'Use when…' clause naming concrete trigger phrases (e.g., 'Use when managing an EmDash CMS instance, running migrations, generating types, or working with EmDash content/schema from the command line') to lift completeness above 3.

Replace the generic verbs 'inspect and manage' with a few discrete actions (e.g., 'list, create, update, and publish content; manage schema and taxonomies; run migrations and generate types') to reach the 5 anchor for specificity.

Add natural synonyms a user might say (e.g., 'EmDash CMS', 'em CLI') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Enumerates comprehensive capability areas (content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, generated types), but the verbs 'inspect and manage' are generic rather than discrete concrete actions, so it sits below the 5 anchor.	4 / 5
Completeness	It clearly answers 'what' (inspect and manage an EmDash instance across the listed domains) but provides no 'Use when…' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Good product-specific keyword coverage (EmDash, CLI, command line, content, schema, migrations, types) that a user of this CMS would naturally say, though it lacks synonym breadth and there are no relevant file extensions to cover.	4 / 5
Distinctiveness Conflict Risk	The EmDash product name carves out a clear, niche trigger set with minimal overlap risk against 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/blank/.agents/skills/emdash-cli/SKILL.md
Commit: 9ca2de5

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