esdd

Express Spec-Driven Development for setting up project-aware change workflows, documenting domains, planning and applying changes in stages, verifying outcomes, and archiving completed work. Use only when the user explicitly asks for ESDD, references an ESDD command or artifact, or wants to continue an existing ESDD change.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured dispatcher skill: terse, actionable, with a clear sequenced workflow and an explicit init-gate validation checkpoint. References are real, one level deep, and clearly signaled, giving strong progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and dispatch-focused — short numbered rules, a one-line script listing, and terse conditional gate logic — with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Provides an executable command ('node <skill-dir>/scripts/cli.mjs init --status') plus concrete conditional instructions ('read [help]... and stop', 'suggest running /esdd init and stop') that are copy-paste ready and unambiguous.	3 / 3
Workflow Clarity	The dispatch is clearly sequenced (parse $ACTION → init gate → dispatch or help) and the Init Gate acts as an explicit validation checkpoint with conditional branching and stop conditions for both initialized states.	3 / 3
Progressive Disclosure	A clean overview points to one-level-deep, well-signaled references (help, docs.commands, and per-action files), all of which exist in references/, with content appropriately split across files and easy to navigate.	3 / 3
	Total	12 / 12 Passed

Description

100%

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, concise description that states concrete capabilities and pairs them with explicit, restrictive use-when triggers tied to a named skill name. It avoids verbosity and over-claims while clearly demarcating when it should activate.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'setting up project-aware change workflows, documenting domains, planning and applying changes in stages, verifying outcomes, and archiving completed work' — matching the anchor for naming several specific actions rather than vague language.	3 / 3
Completeness	Clearly answers both what (the staged workflow verbs) and when via an explicit 'Use only when the user explicitly asks for ESDD...' clause, satisfying the top anchor for both what AND when.	3 / 3
Trigger Term Quality	Explicit, natural triggers users would actually say: 'the user explicitly asks for ESDD, references an ESDD command or artifact, or wants to continue an existing ESDD change' — good coverage of natural terms for this domain.	3 / 3
Distinctiveness Conflict Risk	The narrow 'Use only when... explicitly asks for ESDD' trigger carves out a distinct niche tied to a named command/artifact, making conflict with other skills unlikely.	3 / 3
	Total	12 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: shillem/cc-marketplace
Commit: 56f705f

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