CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/mise-complete

Configure and operate Mise for deterministic developer environments. Use when installing runtime/tool versions, defining reusable tasks, managing layered environment variables, migrating from asdf/nvm/pyenv, or debugging mise.toml behavior in CI and local shells. Keywords: mise, mise.toml, tool versions, tasks, env, asdf migration, setup automation, dev environment.

71

Quality

89%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and workflow-clear with executable commands and a validation/retry loop, but it is mildly padded by a self-evaluation command and its external references are listed rather than woven into navigation. Tightening the off-topic block and linking references inline would lift the two mid dimensions.

Suggestions

Remove or relocate the "Evaluate this skill quality" Quick Command block — it is meta to the skill's purpose and consumes tokens without aiding Mise operation.

Weave the references into their relevant sections (e.g., link references/tasks-definition.md next to the task discussion, references/env-hierarchies.md next to env config) instead of a bare end-of-file list.

Dedupe the validation guidance between Deterministic Workflow steps 5–6 and the Quick Commands doctor entry to avoid restating the same mise install/doctor flow twice.

DimensionReasoningScore

Conciseness

Mostly lean and it assumes Claude's competence, but the off-purpose "Evaluate this skill quality" command block and overlap between the Deterministic Workflow steps and the Quick Commands section add tokens that don't earn their place.

2 / 3

Actionability

Concrete executable commands (mise install, mise doctor, mise ls, mise use node@22, mise run test, mise env) each with expected results, plus a complete copy-paste mise.toml example.

3 / 3

Workflow Clarity

A six-step Deterministic Workflow sequences detection through validation ("mise install && mise doctor") with an explicit failure→diagnose→retry feedback loop in step 6.

3 / 3

Progressive Disclosure

Sections are well-organized and the ten references are one level deep, but they appear as a bare flat list rather than being signaled inline within the relevant sections (e.g., no "See references/tasks-definition.md" link near the task content).

2 / 3

Total

10

/

12

Passed

Description

100%

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, third-person description that pairs concrete capabilities with explicit "Use when" triggers and a natural keyword list. It clearly states both what the skill does and when to invoke it with minimal risk of skill conflicts.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "installing runtime/tool versions, defining reusable tasks, managing layered environment variables, migrating from asdf/nvm/pyenv, or debugging mise.toml behavior" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers what ("Configure and operate Mise for deterministic developer environments") and when ("Use when installing runtime/tool versions...") with an explicit trigger clause, satisfying both halves.

3 / 3

Trigger Term Quality

An explicit "Keywords: mise, mise.toml, tool versions, tasks, env, asdf migration, setup automation, dev environment" gives good coverage of natural terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The Mise-specific niche and migration triggers (asdf/nvm/pyenv) make it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents