CtrlK
BlogDocsLog inGet started
Tessl Logo

core-fix-skill-docs

Internal maintenance support for checking and fixing generated Rust skill documentation references. Use only when explicitly invoked by /fix-skill-docs.

54

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/core-fix-skill-docs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 actionable with concrete commands and examples, but loses conciseness to duplicated Agent/Inline mode sections and loses workflow clarity to missing validation checkpoints around destructive and batch operations. Progressive disclosure is adequate but unoptimized.

Suggestions

Collapse the Agent Mode and Inline Mode sections into a shared step sequence, branching only on the fetch mechanism, to remove the duplicated steps and improve conciseness.

Add explicit validation checkpoints before destructive/batch actions (e.g., confirm missing-file list with the user, verify fetched content is non-empty before writing, and dry-run --remove-invalid) to lift workflow clarity above 3.

Move the tool-priority detail and error-handling table into a reference file and link to it from SKILL.md, or remove the time-sensitive version line, to improve progressive disclosure and conciseness.

DimensionReasoningScore

Conciseness

Agent Mode and Inline Mode repeat near-identical step sequences, and a time-sensitive version/date line adds noise; content is mostly efficient but could be tightened by de-duplicating the modes.

3 / 5

Actionability

Provides concrete bash, Task(), WebFetch, and Edit snippets with sample outputs; template placeholders like {crate_name} keep it just short of fully copy-paste ready.

4 / 5

Workflow Clarity

Steps are clearly numbered and sequenced, but batch/destructive operations (scanning all skills, --remove-invalid edits, overwriting reference files) lack explicit validation checkpoints before acting, capping this at 3 per the rubric.

3 / 5

Progressive Disclosure

All content is inline in a ~240-line file with reasonable section headers, but the duplicated mode workflows could be reorganized or split, and no bundle files are used to offload detail.

3 / 5

Total

13

/

20

Passed

Description

66%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 clearly conveys a narrow purpose and an explicit invocation trigger, giving it strong distinctiveness and solid completeness. Specificity and trigger-term coverage are adequate but could be richer with more concrete actions and natural synonyms.

DimensionReasoningScore

Specificity

Names the domain ('generated Rust skill documentation references') and two concrete actions ('checking and fixing'), but does not enumerate specific actions comprehensively enough for a 4.

3 / 5

Completeness

Explicitly answers both 'what' (checking and fixing documentation references) and 'when' ('Use only when explicitly invoked by /fix-skill-docs'); the 'what' could be more concrete to reach 5.

4 / 5

Trigger Term Quality

Includes relevant terms ('skill documentation references', '/fix-skill-docs') but lacks the natural synonyms or phrasings a user would actually say, missing common variations.

3 / 5

Distinctiveness Conflict Risk

A narrow niche (generated Rust skill documentation references) gated by a single explicit invocation trigger yields minimal conflict risk with other skills.

5 / 5

Total

15

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
actionbook/rust-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.