CtrlK
BlogDocsLog inGet started
Tessl Logo

axolotl

Expert guidance for fine-tuning LLMs with Axolotl - YAML configs, 100+ models, LoRA/QLoRA, DPO/KTO/ORPO/GRPO, multimodal support

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/ml-training/axolotl/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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 well-structured with genuine one-level-deep references, but suffers from generic boilerplate, several non-executable pattern blocks, and a lack of any sequenced workflow with validation checkpoints.

Suggestions

Replace bare-identifier code blocks (Pattern 3, 4, 6) with complete, copy-pasteable YAML or commands, or move them into the reference files.

Remove empty placeholder sections ('Add helper scripts here', 'Add templates, boilerplate, or example projects here') and fix dangling references to non-existent files (getting_started, tutorials, guides).

For common multi-step operations (e.g. configuring FSDP or context parallelism), add a short sequenced workflow with an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

Mostly efficient, but includes generic boilerplate ('Add helper scripts here', 'Add templates, boilerplate, or example projects here') and low-value patterns (Pattern 3/4/6 are bare identifiers) that could be trimmed.

3 / 5

Actionability

Some concrete executable guidance (FSDP yaml, NCCL command, save_compressed) but several patterns are just bare identifiers (`context_parallel_size`, `integrations`) and the Python examples lack context on when to call them.

3 / 5

Workflow Clarity

No real multi-step workflow with validation checkpoints is presented; the 'When to Use' list and 'Updating' section are loosely defined sequences with no checkpoints, fitting the 'rough sequence, poorly defined' anchor.

2 / 5

Progressive Disclosure

Good one-level-deep structure with real reference files (api.md, dataset-formats.md, other.md all exist) clearly listed; minor gaps include dangling references to non-existent 'getting_started/tutorials/guides' files and inlined quick-reference patterns.

4 / 5

Total

12

/

20

Passed

Description

70%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 is specific and distinct, with good trigger-term coverage anchored on the named tool Axolotl. Its main weakness is the absence of an explicit 'Use when...' clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when fine-tuning or training LLMs with Axolotl, writing axolotl YAML configs, or setting up LoRA/QLoRA, DPO/KTO/ORPO/GRPO, or multimodal training.'

Include common synonyms a user might say such as 'SFT', 'training', and 'PEFT' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete capabilities ('YAML configs, 100+ models, LoRA/QLoRA, DPO/KTO/ORPO/GRPO, multimodal support'), though the action verb is the generic 'fine-tuning' rather than distinct discrete actions.

4 / 5

Completeness

Has a clear 'what' (expert guidance for fine-tuning LLMs with Axolotl) but no 'when'/'Use when...' trigger clause, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Strong natural keyword coverage users would say ('fine-tuning LLMs', 'LoRA/QLoRA', 'DPO/KTO/ORPO/GRPO', 'Axolotl'), with a few common synonyms missing (e.g. 'SFT', 'training', 'PEFT').

4 / 5

Distinctiveness Conflict Risk

Names the specific tool 'Axolotl' with method-specific triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
synthetic-sciences/openscience
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.