CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

93%

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

93%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 routing skill body: lean, executable, and well-structured with a validated dispatch gate and one-level-deep references. The only minor gap is the absence of an in-body error-recovery feedback loop.

DimensionReasoningScore

Conciseness

A lean ~30-line dispatcher that assumes Claude's competence and avoids explaining known concepts; every line is actionable instruction with no padding.

5 / 5

Actionability

Provides a copy-paste-ready command ('node <skill-dir>/scripts/cli.mjs init --status') and concrete routing conditions with explicit per-action reference files.

5 / 5

Workflow Clarity

A clear numbered sequence with an explicit init-gate validation checkpoint and stop conditions, though the body itself routes rather than embedding a fix-retry feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is a clean overview that dispatches to nine one-level-deep action reference files plus help/commands docs, with clearly signaled navigation and no nested doc-chasing.

5 / 5

Total

19

/

20

Passed

Description

92%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, well-scoped description that clearly states capabilities and gives explicit, low-conflict trigger guidance. The only gap is trigger-term synonym diversity, which is narrow relative to the proper-noun anchor.

DimensionReasoningScore

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' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what (the workflow stages) and when ('Use only when the user explicitly asks for ESDD...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good trigger coverage via 'asks for ESDD, references an ESDD command or artifact, or wants to continue an existing ESDD change', but the terms are all anchored to the proper noun 'ESDD' with limited synonym diversity.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to a named system with an explicit 'Use only when' boundary anchored to ESDD commands and artifacts, giving a clear niche with minimal conflict risk.

5 / 5

Total

19

/

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.

Validation15 / 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
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.