CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

devx-ux

Activate when designing or modifying CLI command surfaces, command help text, install/init/run flows, error wording, or first-run experience in the APM CLI -- even when the user does not say "UX" explicitly.

60

Quality

75%

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 ./.agents/skills/devx-ux/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 an exemplary lean rule set: crisp activation triggers, directive and checkable UX rules, and an explicit boundary against a sibling skill. Its only gaps are the absence of a worked example and one broken external persona link.

DimensionReasoningScore

Conciseness

Every line is a directive with no padding and no explanation of concepts Claude already knows; assertions like 'npm / pip / cargo / gh mental models' and '--verbose is for agents' are stated without over-explanation, matching the lean anchor 5.

5 / 5

Actionability

The rules are concrete and checkable ('Every error names the failure, the cause, and one next action') and name specific mental models and surfaces (help= strings, docstrings), but there is no worked example such as a before/after error message, so it fits anchor 4 rather than 5.

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines whose single action is unambiguous: exhaustive activation criteria plus directive rules, with an explicit scope boundary deferring logging decisions to another skill. The rubric's simple-skill exemption applies and no destructive/batch validation cap is triggered.

5 / 5

Progressive Disclosure

With no bundle files and a short, well-organized body ('When to activate' / 'Key rules') the simple-skill exemption would merit 5, but the persona link points outside the skill bundle to a nonexistent path (../../../.apm/agents/devx-ux-expert.agent.md), a minor navigation gap matching anchor 4.

4 / 5

Total

18

/

20

Passed

Description

52%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 has strong, specific trigger coverage for a niche codebase but omits any statement of what the skill does, leaving it purely as an activation rule. This caps completeness badly and leaves the skill's actual capabilities implicit.

Suggestions

Lead with a 'what' clause before the activation rule, e.g. 'Applies developer-tooling UX conventions (familiar command grammar, human-readable errors) to APM CLI command surfaces...' so the description answers both what and when.

Add natural trigger synonyms such as 'usage message', 'flag or argument naming', or 'command-line output' to widen the terms users would actually say.

Add one boundary phrase in the description (e.g. 'Logging internals are handled by the CLI Logging UX skill') to reduce overlap risk on error-output changes.

DimensionReasoningScore

Specificity

The description names concrete artifacts ('command help text', 'error wording', 'install/init/run flows', 'first-run experience') but the actions ('designing or modifying') are generic and it never makes the skill's actual operation concrete, matching anchor 3 rather than 4.

3 / 5

Completeness

The description is entirely a 'when' clause ('Activate when...') and never states what the skill does (apply UX conventions? review? rewrite help text?), exactly matching anchor 2 ('only when is present without what').

2 / 5

Trigger Term Quality

'command help text', 'error wording', 'install/init/run flows', and 'first-run experience' are natural developer phrasings plus specific command names, but common synonyms like 'usage message', 'flags/arguments', or 'command-line output' are missing, matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'in the APM CLI' gives a clear niche with concrete trigger surfaces, but error wording and output formatting overlap the sibling 'CLI Logging UX skill' and the description draws no boundary, matching anchor 4.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/apm

Path

.agents/skills/devx-ux/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.