CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-mise

Diagnose, fix, and validate mise runtime failures. Use when commands fail from mise config, missing runtimes, stale pins, trust prompts, or shell activation drift.

65

Quality

79%

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

Quality

Content

71%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 body with strong validation feedback loops and dry-run guards on risky operations. The main weakness is progressive disclosure: the referenced deferred-context path does not align with the bundle files actually present in the skill directory.

Suggestions

Point the Progressive Disclosure section at the real bundle files (references/contract.yaml, references/evals.yaml, references/task-profile.json) instead of an archived path that is not present in this skill bundle.

Tighten the Philosophy and Constraints bullets by dropping restated principles that the workflow and validation sections already demonstrate, to lift conciseness toward a 5.

Add a brief inline mapping of which deferred reference to load for which task (e.g. 'evals.yaml for eval-mode expectations') so one-level-deep navigation is unambiguous.

DimensionReasoningScore

Conciseness

Lean bullet-style sections that mostly assume competence and avoid teaching what mise is; minor padded phrasings in the Philosophy and Constraints sections keep it just below a 5.

4 / 5

Actionability

Provides concrete, runnable commands (e.g. 'mise trust <path>', 'brew upgrade mise', 'mise self-update --yes', 'mise cache prune --dry-run') with mostly executable guidance and only minor gaps.

4 / 5

Workflow Clarity

A clear five-step workflow with explicit validation checkpoints and feedback loops ('Rerun the relevant validation after fixes', 'rerun mise doctor and the original failing command'), plus dry-run guards on destructive/batch cache actions; minor gaps prevent a 5.

4 / 5

Progressive Disclosure

Content is well-sectioned and signals one-level-deep deferred context, but the cited archived path 'Infrastructure/references/deferred-skill-context/agent-ops-fix-mise/' does not match the actual bundle structure present (references/contract.yaml, evals.yaml, task-profile.json), leaving navigation to real files unclear.

3 / 5

Total

15

/

20

Passed

Description

87%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, third-person description that cleanly pairs a concrete capability statement with explicit trigger conditions and is tightly scoped to mise. It could reach a perfect profile by adding a few synonyms and broader action coverage.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions ('Diagnose, fix, and validate mise runtime failures') but the action count is modest rather than comprehensive, sitting between anchors 3 and 5.

4 / 5

Completeness

Explicitly answers both what ('Diagnose, fix, and validate mise runtime failures') and when ('Use when commands fail from mise config, missing runtimes, stale pins, trust prompts, or shell activation drift') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers ('missing runtimes, stale pins, trust prompts, or shell activation drift') but lacks common synonyms or the 'mise' file extension phrasings that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

Carves a clear mise-specific niche with distinct triggers (trust prompts, stale pins, shell activation drift) and minimal overlap risk with other skills.

5 / 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.