CtrlK
BlogDocsLog inGet started
Tessl Logo

journey-sidebar-labels

Audit sidebar labels and order as a developer journey. Use when nav is alphabetical, labels are nouns, or groups need sentence case. It does not write page copy (that's `docs-writing-style`).

69

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A well-organized, actionable diagnostic skill that splits detailed reference material into a one-level-deep bundle file and provides concrete rules, worked examples, and a defined procedure. The only relative gaps are minor conciseness trim opportunities and the absence of an explicit retry feedback loop.

DimensionReasoningScore

Conciseness

The body is efficient and domain-specific with no padding of concepts Claude already knows, but sections like example prompts and the "Did this help?" meta block could be trimmed, keeping it just below fully lean.

4 / 5

Actionability

Concrete, specific guidance throughout: an 8-row label-rules table with worked examples ("Test users" → "Run end-to-end tests", slug rename example), a defined 6-step diagnostic procedure, and a structured output table, covering common cases for an instruction-only skill.

5 / 5

Workflow Clarity

The "Diagnostic process" is a clear 6-step numbered sequence with checkpoints (preview test in step 5, leaf-vs-title drift check in step 6), but it lacks an explicit fix-and-revalidate feedback loop, leaving a minor validation gap.

4 / 5

Progressive Disclosure

A clear overview with a well-signaled, one-level-deep reference (`references/fsa-sidebar-journey.json`, cited as both a structured reference and a checklist); the detailed journey structure is appropriately split into that file rather than inlined.

5 / 5

Total

18

/

20

Passed

Description

82%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.

A strong, well-scoped description that answers both what and when with concrete triggers and an explicit boundary against a sibling skill. Specificity is the only relative weakness, as it surfaces one main action rather than a list of several.

DimensionReasoningScore

Specificity

It names the domain clearly ("Audit sidebar labels and order as a developer journey") with one concrete action (audit), but does not enumerate several specific actions, matching the anchor that names the domain with 1-2 actions rather than comprehensive coverage.

3 / 5

Completeness

It explicitly states both what ("Audit sidebar labels and order as a developer journey") and when ("Use when nav is alphabetical, labels are nouns, or groups need sentence case") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases a docs maintainer would say are present ("nav is alphabetical", "labels are nouns", "groups need sentence case", "sidebar labels"), with only minor synonym gaps such as "navigation menu" or "TOC".

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (sidebar label/order auditing) with distinct triggers and explicitly disambiguates from a sibling skill ("It does not write page copy (that's `docs-writing-style`)"), minimizing conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
saif-shines/devex-kit
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.