CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dx-review

Review developer experience and API ergonomics

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/dx-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, actionable review procedure with a concrete, copy-paste-ready output template and a clear multi-step workflow. Its main weaknesses are redundancy between the criteria lists and the review-process steps, generic guidelines padding, and the absence of any verification checkpoint despite the skill itself asking reviewers to check that code examples work.

Suggestions

Merge the 'DX Evaluation Criteria' question lists with the overlapping 'Review Process' steps to remove duplicated guidance (friction/ergonomics, types, workflows appear twice).

Add an explicit verification step to the process, e.g. "Step 5: Verify claims — actually run the code examples you cite as broken or fixed before reporting them."

Fix the stray ``` fence at the end of the output-format template (line 157) so the nested markdown block renders correctly instead of leaking literal fence characters.

DimensionReasoningScore

Conciseness

The body mostly assumes Claude's competence (no concept explanations), but the 7 evaluation-criteria question lists and the 4-step "Review Process" cover substantially the same ground (e.g., "Step 4: Look for Friction" repeats the Ergonomics criteria, and "Step 2: Read the Types" repeats the Type Experience criteria), and the Guidelines section states practices Claude already follows ("Be specific - Vague feedback isn't actionable"). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not score 2 because nothing explains concepts Claude doesn't know, and not score 4 because the criteria/process duplication and generic guidelines are more than minor.

3 / 5

Actionability

The output format is a fully specified, copy-paste-ready markdown template with exact section names, severity/category taxonomies, and code-block placeholders, and the workflow names concrete tasks ("Opening a PDF and reading metadata", "Modifying form fields", "Saving changes"). For an instruction-only skill this is mostly executable guidance; the minor gap is that steps like "Use the API" and "Read the Types" give no concrete method (no example command or snippet for exercising the library), keeping it below fully copy-paste-ready score 5.

4 / 5

Workflow Clarity

There is a clear, coherent sequence: identify scope, analyze, evaluate against 7 criteria, walk the 4 review-process steps, then write the report to a named path with a fixed structure. This is a read-only review skill so destructive-operation validation caps do not apply, but there is no explicit verification checkpoint (e.g., confirming JSDoc examples actually run, per its own "Do examples in comments actually work?" criterion), which leaves minor validation gaps characteristic of score 4 rather than 5.

4 / 5

Progressive Disclosure

The body is well organized into clearly signaled sections (Task, Criteria, Process, Output Format, Guidelines, Begin) and there are no bundle files, so everything is appropriately in one file — the output template and criteria are the core working material and rightly inline. It sits at 'good structure; most content appropriately placed'; it is not score 5 because at ~157 lines the criteria section could plausibly be split into a reference file, and the nested code-fence in the output template (stray ``` lines around the template's end) slightly obscures navigation of that block.

4 / 5

Total

15

/

20

Passed

Description

53%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 names a specific and distinctive domain but is skeletal: one generic verb, no concrete capabilities, no synonyms like "DX" or "API design", and critically no 'Use when...' trigger guidance. It is serviceable but well below the quality of the reference good examples.

Suggestions

Add an explicit trigger clause, e.g.: "Use when the user asks to review DX, API ergonomics, API design, or developer usability of a library."

Enumerate concrete actions instead of a single generic verb, e.g.: "Reviews a library's discoverability, naming consistency, error messages, and type ergonomics; writes a prioritized DX findings report."

Include natural synonyms users would actually say — "DX", "API design", "usability", "developer experience" — to improve trigger matching.

DimensionReasoningScore

Specificity

"Review developer experience and API ergonomics" names the domain (developer experience, API ergonomics) and one action (Review), but does not enumerate any concrete sub-activities (e.g., evaluating naming, errors, types, or documentation). It matches the anchor for naming a domain with 1-2 actions that are not comprehensive; it is above 'names the domain but actions are minimal' because two distinct review targets are stated, but below 'several specific actions' since only one generic verb carries the description.

3 / 5

Completeness

The 'what' is present (review DX and API ergonomics) but there is no 'Use when...' clause or any trigger guidance whatsoever — 'when' is entirely missing, which caps completeness at 3 per the judging guidelines. It is not score 4 because a 'when' element is absent rather than just under-specified, and not score 2 because the 'what' is clear rather than vague.

3 / 5

Trigger Term Quality

The phrases "developer experience" and "API ergonomics" are relevant domain keywords, but the description omits the most common natural variations users would say: "DX" (the abbreviation used in the skill's own name and body), "API design", and "usability". This matches 'some relevant keywords but missing common variations or synonyms'; it is not score 4 because multiple frequently-used synonyms are absent.

3 / 5

Distinctiveness Conflict Risk

"Developer experience" and "API ergonomics" carve out a clear niche that is mostly distinct from general code-review or security-review skills, with only minor overlap risk if a user says something like "review the API". It is not score 5 because the absence of explicit trigger phrases leaves room for confusion with adjacent review skills, and not score 3 because the domain language is specific rather than broadly overlapping.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

LibPDF-js/core

Path

.opencode/skills/dx-review/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.