CtrlK
BlogDocsLog inGet started
Tessl Logo

devrel-dx-craft

Design first-success DX and pick sample app vs recipe vs pattern. Use when auditing onboarding or choosing content types for developers. It does not write launch stories (that's `devrel-story-craft`).

67

Quality

80%

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/dev-gtm/skills/devrel-dx-craft/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 mature, instruction-only skill body: clear area/mode tables, enforced phase gates with validation loops, and clean progressive disclosure into verified reference files. The main weakness is redundancy — the REFACTOR Hardening and citation-reminder lines duplicate guidance already stated elsewhere.

Suggestions

Collapse the REFACTOR Hardening section into the existing area sections or a single concise pressure-counters block; the rules are already covered by the area guidance and Quality Checklist.

Reduce the repeated "cite the Rationalization Counter Table" instructions to one canonical reference plus a single reminder, since the directive recurs four times.

Trim the Quality Checklist items that re-state body content (e.g. frontmatter shape, load blockquotes) to focus the checklist on verification-only outcomes.

DimensionReasoningScore

Conciseness

The body is well-structured and avoids explaining concepts Claude already knows, but the REFACTOR Hardening section and repeated "cite the Rationalization Counter Table" reminders restate rules already present in the area sections and Quality Checklist, so it could be tightened.

3 / 5

Actionability

Concrete decision rules ("End-to-End Demos = Sample Applications; Feature Examples = Code Snippets/Recipes; Comparative Scripts = Solution Patterns"), explicit anti-patterns, and a "Mandatory before declaring first success" checklist give executable guidance, with the bulk of detail correctly pushed to references.

4 / 5

Workflow Clarity

The DX Journey → Content Taxonomy → Content Jobs → Done sequence is governed by explicit phase gates that act as validation checkpoints with feedback loops ("if only features defined, return to DX Journey"), backed by checklists.

5 / 5

Progressive Disclosure

Heavy content is externalized to four real, one-level-deep references (dx-journey.md, content-taxonomy.md, content-jobs.md, attribution.md), each clearly signaled with a "> Load ... for ..." blockquote pointing to exactly what it contains.

5 / 5

Total

17

/

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 tight, third-person description that clearly pairs a 'what' with an explicit 'Use when' trigger clause and a conflict-reducing boundary note. Specificity is the only mild gap — the action verbs are concrete but limited to two.

DimensionReasoningScore

Specificity

"Design first-success DX and pick sample app vs recipe vs pattern" names the domain plus two concrete actions (design the first-success path, choose among three content types), but the action set is not comprehensive.

3 / 5

Completeness

It explicitly states what it does ("Design first-success DX and pick sample app vs recipe vs pattern") and when to use it ("Use when auditing onboarding or choosing content types for developers"), with concrete trigger phrases for both.

5 / 5

Trigger Term Quality

"auditing onboarding", "choosing content types", "sample app vs recipe vs pattern" are natural phrases a developer would say; common synonyms like "getting started" or "developer experience/DX" are missing, so it stops just short of full coverage.

4 / 5

Distinctiveness Conflict Risk

The niche (first-success DX + content taxonomy choice) is narrow, and the explicit boundary "It does not write launch stories (that's `devrel-story-craft`)" disambiguates it from the nearest sibling skill.

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.