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.

51

Quality

56%

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/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 organized into sensible sections but the guidance is largely abstract goals and generic process steps rather than executable instruction, and its single progressive-disclosure reference is broken. It reads as templated boilerplate over a tailored playbook.

Suggestions

Replace the tautological 'Use/Do not use this skill when' boilerplate with DX-specific trigger conditions and concrete exclusions.

Add concrete, executable guidance (example CLI commands, sample .claude/commands snippets, a working Makefile/task-runner snippet) instead of goal-level bullets.

Either create resources/implementation-playbook.md with the promised detailed examples and link to it correctly, or remove the broken reference.

DimensionReasoningScore

Conciseness

Mostly efficient list-based content, but the tautological 'Use this skill when working on dx optimizer tasks' / 'Do not use... unrelated to dx optimizer' boilerplate adds padding Claude does not need.

3 / 5

Actionability

Guidance is high-level goals and hints ('Identify repetitive tasks for automation', 'Simplify onboarding to < 5 minutes') with no concrete commands or examples, and the only detailed-example reference (resources/implementation-playbook.md) does not exist.

2 / 5

Workflow Clarity

The Analysis Process gives a clear 5-step sequence (Profile, Identify, Research, Implement, Measure) but lacks explicit validation checkpoints or error-recovery feedback loops.

3 / 5

Progressive Disclosure

Section headers provide reasonable structure and one reference is clearly signaled, but it points to a missing file (resources/implementation-playbook.md) and most detail is inlined rather than split out.

3 / 5

Total

11

/

20

Passed

Description

70%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 well-formed with explicit what/when structure and natural trigger phrases, but the stated capabilities remain area-level rather than concrete actions. It is distinct and unlikely to misfire, just not maximally specific.

DimensionReasoningScore

Specificity

Names the DX domain and three areas (tooling, setup, workflows) but these are areas rather than concrete actions like the anchor-3 example, and coverage is not comprehensive.

3 / 5

Completeness

Clearly answers both what ('Improves tooling, setup, and workflows') and when (three explicit triggers), though the 'what' is somewhat generic rather than fully concrete.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ('setting up new projects', 'team feedback', 'development friction'); a few common synonyms/variations are missing, fitting the anchor-4 example.

4 / 5

Distinctiveness Conflict Risk

Developer Experience is a recognizable niche with specific triggers; mostly distinct with only minor overlap risk against general project-setup skills.

4 / 5

Total

15

/

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.