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.

Quality

35%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dx-optimizer/SKILL.md

Quality

Content

28%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a high-level manifesto or role description for DX optimization rather than an actionable skill file. It lacks concrete commands, executable code examples, and specific tooling instructions that would make it useful. The content is padded with concepts Claude already understands (what good DX looks like, what documentation should be) while missing the specific 'how' that would make it actionable.

Suggestions

Replace abstract bullet points with concrete, executable examples — e.g., provide actual git hook scripts, specific Makefile targets, or package.json script configurations that Claude can copy and adapt.

Add validation checkpoints to the Analysis Process — e.g., 'Run `time npm install && npm start` to baseline setup time, then re-measure after each improvement.'

Remove sections that explain concepts Claude already knows (what DX is, what success metrics mean) and replace with specific tool configurations, command templates, or decision trees.

Create the referenced `resources/implementation-playbook.md` bundle file with detailed examples, or inline the most critical examples directly in the skill.

Dimension	Reasoning	Score
Conciseness	The skill is noticeably verbose with many sections that explain concepts Claude already knows (what DX is, what good documentation looks like, what success metrics are). The 'Use this skill when' and 'Do not use this skill when' sections are generic filler. The motivational closing line adds no value.	2 / 5
Actionability	The content is almost entirely high-level guidance with no concrete code, commands, or executable examples. Bullet points like 'Simplify onboarding to < 5 minutes' and 'Optimize build and test times' are aspirational goals, not actionable instructions. No specific commands, scripts, or copy-paste ready content is provided.	2 / 5
Workflow Clarity	The 'Analysis Process' provides a rough 5-step sequence but steps are vaguely defined ('Profile current developer workflows', 'Research best practices') with no validation checkpoints, no concrete tools or commands, and no feedback loops for error recovery.	2 / 5
Progressive Disclosure	There is a reference to `resources/implementation-playbook.md` for detailed examples, which is a reasonable disclosure pattern. However, no bundle files exist to support this reference, and the bulk of the content is inlined as lists that could benefit from better organization into separate files for each optimization area.	3 / 5
	Total	9 / 20 Passed

Description

42%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 benefits from having an explicit 'Use when...' clause with concrete trigger scenarios, which is a strength. However, the 'what' portion is too vague — 'improves tooling, setup, and workflows' could describe dozens of different skills. The lack of specific actions and natural trigger terms makes it difficult to distinguish from other development-related skills.

Suggestions

Replace 'improves tooling, setup, and workflows' with specific concrete actions, e.g., 'Configures build systems, sets up linting/formatting, creates developer onboarding guides, optimizes CI/CD pipelines'.

Add natural trigger terms and synonyms users would actually say, such as 'dev environment', 'DX', 'developer productivity', 'build tools', 'local setup', 'developer onboarding'.

Narrow the scope to reduce conflict risk — clarify what distinguishes this from general project setup, CI/CD, or code quality skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Developer Experience') and mentions broad areas like 'tooling, setup, and workflows' but these are generic categories rather than concrete actions. No specific actions like 'configures CI pipelines' or 'creates onboarding scripts' are listed.	2 / 5
Completeness	Has both 'what' (improves tooling, setup, and workflows) and 'when' (setting up new projects, after team feedback, when development friction is noticed). The 'when' clause is explicit with concrete trigger scenarios, though the 'what' remains vague.	4 / 5
Trigger Term Quality	Terms like 'tooling', 'setup', and 'workflows' are somewhat relevant but very generic. Missing natural user phrases like 'dev environment', 'build system', 'CI/CD', 'onboarding', 'developer productivity', 'DX', or specific tool names that users would actually mention.	2 / 5
Distinctiveness Conflict Risk	'Tooling, setup, and workflows' is extremely broad and could overlap with nearly any development-related skill — project scaffolding, CI/CD configuration, code review, testing setup, etc. The term 'Developer Experience specialist' is a broad umbrella that doesn't carve out a clear niche.	2 / 5
	Total	10 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/dx-optimizer/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.