CtrlK
BlogDocsLog inGet started
Tessl Logo

dx-optimizer

Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.

53

Quality

60%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/dx-optimizer/SKILL.md

The canonical home for this skill is dx-optimizer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

42%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 generic, well-sectioned DX template that is lean but offers little actionable specificity, no executable examples, and a broken reference to a missing playbook file. It reads more as an outline of concerns than executable guidance.

Suggestions

Add concrete, executable examples — specific commands, sample aliases, git-hook snippets, or package.json script patterns — so the guidance can be applied directly rather than interpreted.

Create the referenced 'resources/implementation-playbook.md' (or remove the dangling reference) so progressive disclosure actually resolves to real content.

Tighten the boilerplate 'Use this skill when'/'Instructions' sections to remove tautological bullets like 'Working on dx optimizer tasks or workflows' that add no information.

DimensionReasoningScore

Conciseness

The body is mostly efficient lean bullet lists without over-explaining known concepts, but it retains tautological boilerplate (e.g. 'Working on dx optimizer tasks or workflows', generic 'Instructions') that could be tightened, fitting anchor 3 rather than the trim 4.

3 / 5

Actionability

Guidance consists of high-level goals ('Automate dependency installation', 'Configure IDE settings and extensions') with no code, commands, or specific executable steps, and the only detailed reference does not exist; this matches anchor 2 ('high-level hints but missing the specific steps to execute').

2 / 5

Workflow Clarity

A clear 5-step 'Analysis Process' sequence is present, but it lacks validation checkpoints or error-recovery feedback loops, matching anchor 3 ('sequence present but checkpoints missing or implicit').

3 / 5

Progressive Disclosure

Sections are reasonably organized, but the single referenced file 'resources/implementation-playbook.md' does not exist in the bundle and no other reference files are present, so navigation is partially broken; this fits anchor 3 ('some structure, references present but not clearly signaled').

3 / 5

Total

11

/

20

Passed

Description

78%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 is strong: it states both capabilities and explicit proactive triggers in third person, with natural phrasing users would say. Its main weakness is that the stated actions are broad categories rather than concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain ('Developer Experience specialist') and broad action areas ('Improves tooling, setup, and workflows'), but these are generic categories rather than concrete actions, matching anchor 3; it lacks the several specific actions needed for a 4.

3 / 5

Completeness

It explicitly answers both 'what' ('Developer Experience specialist. Improves tooling, setup, and workflows.') and 'when' ('Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It includes natural user phrases ('setting up new projects', 'team feedback', 'development friction') that a user would plausibly say, giving good keyword coverage, though it stops short of comprehensive synonym/extension coverage for a 5.

4 / 5

Distinctiveness Conflict Risk

'Developer Experience specialist' carves a recognizable niche with distinct triggers, with only minor overlap risk against general tooling/project-setup skills, fitting anchor 4 rather than the clearly-distinct 5 or the overlap-prone 3.

4 / 5

Total

16

/

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.