CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-craft

Start a session to write or improve a kit skill. A user-started orchestrator.

59

Quality

69%

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/tooling/skills/skill-craft/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured lifecycle orchestrator: lean, imperative, with explicit phase gates, a validation feedback loop, and disciplined progressive disclosure to a single real reference file. The only weak spot is slight redundancy in the cross-reference and closing summary.

DimensionReasoningScore

Conciseness

At 167 lines (under the 200 budget) the body is imperative and assumes competence, with only minor repetition (the plugin-craft cross-reference and the closing summary could be trimmed) keeping it off a 5.

4 / 5

Actionability

Provides concrete, copy-paste-ready commands (`dora review ... --format json`, `npx @hacksmith/doraval`), an exact frontmatter template, and specific paths; minor gaps in full runnable examples for the optimize loop keep it at 4.

4 / 5

Workflow Clarity

A phase table, explicit phase gates between every transition, and a dora validate→fix→re-run-until-exit-0 feedback loop plus a boxed quality checklist give clear sequencing with validation and error recovery.

5 / 5

Progressive Disclosure

The body stays a lean overview and consistently delegates heavy material to the one-level-deep, existing `references/skill-craft-methodology.md` via the canonical `> For ... load references/...` blockquote, making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

53%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 states what the skill does concisely in third person, but omits any 'when to use it' trigger guidance and relies on a single phrase pair rather than a spread of natural trigger terms. It is distinguishable but would benefit from explicit trigger phrasing.

Suggestions

Add a 'Use when the user asks to write, draft, or improve a kit skill (e.g. "turn this into a skill", "make a skill for X")' clause to answer the 'when' and lift completeness above 3.

Broaden trigger terms to include natural variations like 'author a skill', 'skill from scratch', or 'refactor a skill' to improve trigger-term coverage.

Explicitly distinguish from the sibling skill-creator (e.g. 'Use for kit-form skills; use /skill-creator for the full eval harness') to reduce overlap risk.

DimensionReasoningScore

Specificity

Names the domain ('kit skill') and two concrete actions ('write or improve'), but coverage is not comprehensive — it stops at the headline actions without listing the lifecycle activities the body actually covers.

3 / 5

Completeness

The 'what' is clear but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

'write or improve a kit skill' are natural phrases a user might say, but there are no synonyms, variations, or file extensions; 'user-started orchestrator' is meta rather than a user-facing trigger.

3 / 5

Distinctiveness Conflict Risk

The 'kit skill' scope is a clear niche with only minor overlap risk against the sibling skill-creator; the description does not explicitly disambiguate from it, keeping it just below a 5.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

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.