CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

esdd

Express Spec-Driven Development for project setup, domain documentation, planning, implementation, revision, verification and archiving. Use only when the user asks for ESDD, references an ESDD command or artifact, or follows up on an existing ESDD change.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

An exemplary router-style body: lean, fully executable commands verified against the bundled CLI, explicit sequencing with validation gates, stop conditions, and feedback loops. The only weakness is navigation depth — action references chain one level deeper via shared-*.md files, and the four docs.*.md bundle files are orphaned with no entry point pointing to them.

DimensionReasoningScore

Conciseness

The 49-line body is pure procedural instruction ("Treat the first word as `$ACTION`, remainder as `$REST`", "Run the init gate, except for `explore`") with zero explanation of concepts Claude already knows. The densest passages ("rewrite each affected section as it would read if the current target had been known from the start") are skill-specific policy, not padding, so there is nothing to trim — matching the anchor 'lean and efficient; assumes Claude's competence' rather than anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Every command is copy-paste ready and verified against the bundle: `node <skill-dir>/scripts/cli.mjs init --status`, `status "<name>" --apply`, and `list` all exist in scripts/cli.mjs and its actions, and the dispatch logic is fully concrete ("If uninitialized and `$ACTION` is not `init`, suggest `/esdd init` and stop"). This matches 'fully executable; copy-paste ready commands; specific examples cover the common cases' — the no-input, invalid-input, valid-action, and follow-up cases are all handled.

5 / 5

Workflow Clarity

Steps 1–6 give a clear sequence with an explicit validation checkpoint (the Init Gate's if/then/stop conditions) and genuine feedback loops: "Check tasks only when implementation and relevant verification satisfy their outcomes; uncheck unmet ones. Run relevant tests and build/type checks after code corrections", plus stop-on-blocked revision. It fits anchor 5 ('explicit validation steps; feedback loops for error recovery') rather than anchor 4 because checkpoints are present at every decision point, not just 'most'.

5 / 5

Progressive Disclosure

The body is a lean overview dispatching to ten action references, all of which are real files, plus shared-revision.md and the CLI script — good structure matching anchor 4. It falls short of anchor 5 ('well-signaled one-level-deep references') because action files chain to a second markdown level (e.g. continue.md → shared-revision.md, shared-plan-loop.md) and four bundle files (docs.commands.md, docs.workflows.md, docs.artifacts.md, docs.configuration.md, ~23KB total) are referenced from nowhere — not SKILL.md, any reference file, or the scripts — leaving that content unreachable via navigation.

4 / 5

Total

19

/

20

Passed

Description

87%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 strong description that explicitly answers both what and when, with distinctive named triggers and correct third-person voice throughout. The action list covers the full lifecycle but at a generic-verb level rather than concrete operations, and trigger coverage omits the natural expansion 'spec-driven development' that appears in the capability clause.

DimensionReasoningScore

Specificity

It lists several specific functions — "project setup, domain documentation, planning, implementation, revision, verification and archiving" — with only minor coverage gaps, matching anchor 4. It is not anchor 5 because the actions are generic lifecycle verbs rather than concrete operations (compare "fill forms, merge documents"), and "Express Spec-Driven Development" leans on domain jargon; it is above anchor 3 since coverage spans seven functions, not just 1–2.

4 / 5

Completeness

Both questions are answered explicitly: the what ("project setup, domain documentation, planning, implementation, revision, verification and archiving") and the when ("Use only when the user asks for ESDD, references an ESDD command or artifact, or follows up on an existing ESDD change") with three enumerated concrete trigger conditions. This matches anchor 5; it is not anchor 4 because the when-clause is fully explicit rather than merely present or 'could be more specific'.

5 / 5

Trigger Term Quality

Good keyword coverage of what a user of this named workflow would naturally say: "asks for ESDD, references an ESDD command or artifact, or follows up on an existing ESDD change". It misses a few natural terms — the expansion "spec-driven development" (used in the what-clause) and likely "SDD" are not trigger phrases — so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage, while clearly exceeding anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

Triggering is gated on the named workflow itself ("Use only when the user asks for ESDD..."), giving it a clear niche with distinct triggers and minimal conflict risk with any other skill — anchor 5. It is not anchor 4 because there is no plausible overlap even with closely related planning/spec skills: the ESDD name is required.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

shillem/cc-marketplace

Path

plugins/esdd/skills/esdd/SKILL.md

Reviewed

Table of Contents

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.