CtrlK
BlogDocsLog inGet started
Tessl Logo

mise-expert

Mise development environment manager (asdf + direnv + make replacement). Capabilities: tool version management (node, python, go, ruby, rust), environment variables, task runners, project-local configs. Actions: install, manage, configure, run tools/tasks with mise. Keywords: mise, mise.toml, tool version, runtime version, node, python, go, ruby, rust, asdf, direnv, task runner, environment variables, version manager, .tool-versions, mise install, mise use, mise run, mise tasks, project config, global config. Use when: installing runtime versions, managing tool versions, setting up dev environments, creating task runners, replacing asdf/direnv/make, configuring project-local tools.

64

Quality

77%

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/mise-expert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable — dense with executable, copy-paste-ready mise.toml and CLI examples — and includes a clear design workflow with validation steps plus a symptom-based troubleshooting guide. Its main weaknesses are severe redundancy (the same task patterns repeated across four or five sections, ~1,014 lines total) and a monolithic structure with no bundle files, so migration guides, CI configs, and pattern libraries that should be on-demand references are always in context.

Suggestions

Split the migration guides (<migration_from_asdf/make/npm/direnv>), CI/CD configs, and troubleshooting guide into separate reference files (e.g. references/migrations.md, references/troubleshooting.md) and keep SKILL.md as a concise overview with one-level-deep, clearly signaled links.

Deduplicate the task-configuration examples: the dev/build/test patterns appear nearly verbatim in <tool_installation_patterns>, <common_patterns>, <example_setup>, <example_polyglot>, and <migration_from_npm> — keep one canonical set and cut the rest.

Remove sections that restate the frontmatter ("Core Capabilities" and much of "When to Use This Skill") since the description already carries that information, and replace the redundant monorepo/polyglot pair with a single example.

DimensionReasoningScore

Conciseness

At ~1,014 lines the body is noticeably verbose with several padded and redundant sections: the same dev/build/test task patterns appear nearly verbatim in <tool_installation_patterns>, <common_patterns>, <example_setup>, <example_polyglot>, and <migration_from_npm>; the "When to Use This Skill" and "Core Capabilities" sections restate the frontmatter; and monorepo and polyglot examples duplicate each other. It never explains concepts Claude wouldn't know, but the sheer duplication across sections sits squarely in the 'several unnecessary or padded sections' anchor rather than the 'some could be tightened' anchor.

2 / 5

Actionability

Guidance is fully executable throughout: complete, copy-paste-ready mise.toml configurations ([tools], [env], [tasks] with sources/outputs/depends/usage specs), concrete CLI commands ("mise use -g ripgrep@latest", "mise ls-remote node", "mise doctor"), and worked before/after migration examples for asdf, make, npm, and direnv. Specific examples cover the common cases (setup, polyglot, CI, Docker, troubleshooting).

5 / 5

Workflow Clarity

The <workflow_steps> section gives a clear 5-step sequence (Assess → Design → Implement → Optimize → Validate) with concrete validation commands in step 5 ("mise tasks ls", "mise run <task>", "mise doctor"), and the Troubleshooting Guide supplies symptom → diagnostic-command feedback loops. Not a 5 because the workflow steps themselves lack inline error-recovery branches (the fix loops live in a separate section) and some steps are advisory bullet lists rather than a concrete linear procedure.

4 / 5

Progressive Disclosure

There is no bundle (references/, scripts/, assets/ do not exist) and the entire ~1,000 lines are inlined in SKILL.md, so heavy material that clearly belongs in reference files — the four migration guides, the CI/CD configurations, the full troubleshooting guide, and the ~200-line pattern library — all load into context on every invocation. Section headers do provide reasonable in-document navigation, which keeps it above the 'minimal structure' anchor, but nothing is split out or referenced one level deep.

3 / 5

Total

14

/

20

Passed

Description

91%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 description: it explicitly states what the skill does, lists comprehensive natural trigger terms including file names and extensions, and includes an explicit 'Use when:' clause with concrete triggers, all in third-person voice. Minor weakness: some broad keywords (node, python, environment variables) create slight overlap risk with general setup skills, and the action verbs are somewhat generic.

DimensionReasoningScore

Specificity

Names the domain ("Mise development environment manager (asdf + direnv + make replacement)") and lists several concrete capabilities ("tool version management (node, python, go, ruby, rust), environment variables, task runners, project-local configs") with actions ("install, manage, configure, run tools/tasks with mise"). Not a 5 because the action verbs ("install, manage, configure") are generic compared to the fully concrete action lists in the top anchor; not a 3 because coverage spans multiple distinct capability areas rather than 1-2 actions.

4 / 5

Completeness

Explicitly answers "what" ("Capabilities: tool version management..., environment variables, task runners, project-local configs. Actions: install, manage, configure, run tools/tasks with mise") and "when" ("Use when: installing runtime versions, managing tool versions, setting up dev environments, creating task runners, replacing asdf/direnv/make, configuring project-local tools") with concrete trigger phrases. Both clauses are explicit, matching the top anchor.

5 / 5

Trigger Term Quality

The keyword list is comprehensive and includes natural synonyms, file names, and extensions users would actually say: "mise, mise.toml, tool version, runtime version, node, python, go, ruby, rust, asdf, direnv, task runner, environment variables, version manager, .tool-versions, mise install, mise use, mise run, mise tasks, project config, global config". This matches the top anchor's standard of synonyms plus file extensions (.tool-versions, mise.toml).

5 / 5

Distinctiveness Conflict Risk

The tool-specific anchors (mise, mise.toml, .tool-versions, asdf, direnv) give it a clear niche with minimal conflict risk against other skills. Not a 5 because broad generic terms in the trigger list ("node", "python", "environment variables", "version manager") could cause minor overlap with general Node/Python setup or env-management skills.

4 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (1015 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
samhvw8/dot-claude
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.