CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

huggingface-accelerate

Simplest distributed training API. 4 lines to add distributed support to any PyTorch script. Unified API for DeepSpeed/FSDP/Megatron/DDP. Automatic device placement, mixed precision (FP16/BF16/FP8). Interactive config, single launch command. HuggingFace ecosystem standard. Also covers DeepSpeed and PyTorch Lightning (guides in references/).

Quality

71%

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/distributed-training/accelerate/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 highly actionable, well-sequenced skill body with excellent copy-paste examples covering all advertised workflows. Its weaknesses are moderate redundancy and time-sensitive version detail in the main body, and a merged-in DeepSpeed sub-bundle whose second-level references are deeply nested and poorly labeled, undermining navigation despite the clean top-level structure.

Suggestions

Drop the duplicated conversion example — keep either the Quick start diff or Workflow 1's original-vs-converted scripts, not both — and remove filler lines (the `accelerate config` question list, "Used by: ...") to tighten the body.

Move version-specific details ("Version: 1.11.0+", "FSDP: PyTorch 1.12+") into a clearly labeled version-compatibility note so they don't go stale in the main flow.

Fix the second-level navigation in references/deepspeed/overview.md: replace placeholder descriptions ("08.md - 08 documentation") with real topic summaries, split the 454KB tutorials.md into focused files, or surface key DeepSpeed content directly in the overview so nothing important is buried two levels deep.

DimensionReasoningScore

Conciseness

The body is mostly lean code-and-commands, but it includes unnecessary material: the 4-line conversion example is shown in full twice (the diff in Quick start, then again as Workflow 1's original-vs-converted scripts, ~40 duplicated lines), and filler like the "Questions" list from `accelerate config` and Resources lines such as "Tutorial: 'Accelerate your scripts'" and "Used by: ..." add tokens without instruction value. Time-sensitive version numbers ("Version: 1.11.0+", "FSDP: PyTorch 1.12+") are also present outside any deprecated/version-note section, which the guidelines penalize.

3 / 5

Actionability

Nearly every section is copy-paste-ready: the numbered 4-line conversion, per-setup launch commands (single/multi-GPU/multi-node with exact flags), mixed-precision constructor args, a complete deepspeed_config.json, the FSDP plugin setup, `accelerator.accumulate`, `save_state`/`load_state` guarded by `is_main_process`, and `set_seed`. The only placeholder is `dataset`, which is inherent to training examples; the examples cover all the common cases the description advertises.

5 / 5

Workflow Clarity

Workflows are clearly sequenced — the conversion steps are literally numbered (+1..+4), each workflow follows an enable → prepare → launch pattern, and the "Common issues" section gives error-recovery fixes (wrong device placement, accumulation not working, FSDP seed divergence). Not anchor 5 because there are no explicit validation checkpoints (e.g., verifying the setup runs on one GPU before scaling to multi-node, or `accelerate test`), leaving checkpoints implicit rather than built into the workflows.

4 / 5

Progressive Disclosure

The SKILL.md body itself is a well-signaled overview with one-level references (megatron-integration.md, custom-plugins.md, performance.md, and the merged-tool guides all exist and are linked with descriptive tables). However, scoring against the actual bundle structure: the merged DeepSpeed guide nests a second reference level (references/deepspeed/overview.md → references/deepspeed/references/*.md, including a 454KB tutorials.md monolith), and its "Reference Files" index signals them with useless placeholders like "08.md - 08 documentation" and "other.md - Other documentation", so the deep material is effectively buried two levels down.

3 / 5

Total

15

/

20

Passed

Description

62%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 dense, capability-rich description that clearly communicates what the skill does, with excellent technical keyword coverage. Its main weaknesses are the complete absence of an explicit "Use when..." trigger clause and a closing claim that broadens scope into DeepSpeed and PyTorch Lightning, raising conflict risk with adjacent skills.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user wants distributed or multi-GPU/multi-node training for PyTorch scripts, or mentions Accelerate, DeepSpeed, FSDP, DDP, or mixed precision training."

Soften or scope the "Also covers DeepSpeed and PyTorch Lightning" claim (e.g., "Includes reference guides for DeepSpeed and PyTorch Lightning") so the description does not fire for general questions about those tools when they have their own skills.

Include one or two common natural phrasings such as "multi-GPU", "multi-node", or "train across GPUs" to round out trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "4 lines to add distributed support to any PyTorch script", "Automatic device placement, mixed precision (FP16/BF16/FP8)", "Interactive config, single launch command" — with named backends (DeepSpeed/FSDP/Megatron/DDP). It falls short of anchor 5 because the items are feature labels rather than concrete actions, and coverage has minor gaps (e.g., gradient accumulation, checkpointing, multi-node scaling are not mentioned).

4 / 5

Completeness

The "what" is clearly and specifically answered (add distributed support to PyTorch scripts with a unified API, automatic device placement, mixed precision), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3; the only implied timing is "to add distributed support to any PyTorch script".

3 / 5

Trigger Term Quality

Strong keyword coverage of terms users would naturally say: "distributed training", "PyTorch script", "DeepSpeed", "FSDP", "DDP", "mixed precision", "FP16/BF16/FP8", "PyTorch Lightning". Not anchor 5 because common natural phrasings like "multi-GPU", "multi-node", "sharding", or "train across GPUs" are missing, which leaves a few likely user utterances uncovered.

4 / 5

Distinctiveness Conflict Risk

The core niche (HuggingFace Accelerate as the "Simplest distributed training API" / "HuggingFace ecosystem standard") is identifiable, but the closing claim "Also covers DeepSpeed and PyTorch Lightning (guides in references/)" deliberately broadens the skill to two adjacent ecosystems, creating real overlap risk if dedicated DeepSpeed or Lightning skills exist. This is more than the "minor overlap risk with closely related skills" of anchor 4, but the skill is not generic, so it sits above anchor 2.

3 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 4 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

OpenLAIR/dr-claw

Path

skills/distributed-training/accelerate/SKILL.md

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.