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.

52

Quality

58%

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 ./skills/dx-optimizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 clean, organized instruction-only skill, but its guidance is mostly abstract and lacks concrete commands, executable examples, or explicit validation checkpoints in its workflow.

Suggestions

Add concrete, copy-paste-ready examples or commands for the most common tasks (e.g., a sample `.claude/commands/` slash command, a `package.json` script snippet, a husky/git hook config) to lift actionability.

Insert explicit validation/feedback checkpoints into the Analysis Process (e.g., after implementing, verify build+test pass and measure the target metric before iterating) to raise workflow clarity.

Trim generic filler bullets in 'Instructions' and 'Optimization Areas' that restate what Claude already knows.

DimensionReasoningScore

Conciseness

Mostly efficient and well-organized with no major padding, but several bullets are generic boilerplate ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') that could be tightened or removed.

3 / 5

Actionability

Guidance is largely abstract high-level hints ('Create intelligent defaults', 'Optimize build and test times') with no concrete commands, executable examples, or specific tools, though a few deliverable targets (`.claude/commands/`, `package.json` scripts, git hooks) are named.

2 / 5

Workflow Clarity

The 'Analysis Process' gives a clear numbered sequence (Profile → Identify → Research → Implement → Measure), but there are no explicit validation checkpoints or feedback loops for an iterative/batch implementation process, capping it at 3.

3 / 5

Progressive Disclosure

A single well-organized file with clear section headers and no broken or nested references; no bundle files exist so there is nothing to mis-signal. Slightly over the simple-skill line, so it stays just below a 5.

4 / 5

Total

12

/

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: third person, with a clear what and an explicit, multi-trigger when clause. It is solid but not exemplary because the stated actions are generic rather than concretely enumerated.

Suggestions

Replace the generic 'Improves tooling, setup, and workflows' with a few concrete capabilities (e.g., 'Profiles build/test times, configures IDE settings and git hooks, generates onboarding scripts and CLI commands').

Add natural synonyms or tool references users might say (e.g., 'onboarding', 'build times', 'developer friction', '.claude/commands') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Developer Experience specialist') and 1-2 action areas ('Improves tooling, setup, and workflows'), but the actions are nominal and generic rather than a comprehensive concrete list.

3 / 5

Completeness

Explicitly answers both what (DX specialist improving tooling/setup/workflows) and when (a 'Use PROACTIVELY when...' clause with concrete triggers); the 'what' could be more specifically enumerated, keeping it just below a 5.

4 / 5

Trigger Term Quality

Good natural trigger coverage ('setting up new projects', 'after team feedback', 'when development friction is noticed', 'PROACTIVELY'), but missing common synonyms and file/tool extensions.

4 / 5

Distinctiveness Conflict Risk

'Developer Experience' is a distinct niche with clear triggers and minimal overlap risk, though it could brush against generic project-setup or tooling 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-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.