CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

73%

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/distributed-training/accelerate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 highly actionable with executable examples and excellent progressive disclosure, but workflow clarity is capped by the absence of explicit validation/verification checkpoints for distributed and batch training operations.

Suggestions

Add validation checkpoints to workflows, e.g. after launch verify "all N processes are running and loss is decreasing on rank 0", and a validate→fix→retry loop for common failure modes (OOM, NCCL errors, rank hangs).

Trim redundant asides and the repeated "4 lines added" annotations across workflows to tighten conciseness.

Consolidate the repeated prepare()/backward() pattern shown in multiple workflows into one canonical example with per-workflow only showing the differing config.

DimensionReasoningScore

Conciseness

Code-heavy and direct, but includes repeated "4 lines added" patterns and asides like "No .to('cuda') needed - automatic!" and "Everything else is automatic!" that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready code and launch commands covering single-GPU, multi-GPU, multi-node, mixed precision, DeepSpeed, FSDP, and gradient accumulation — the common cases are all concretely addressed.

5 / 5

Workflow Clarity

Workflows are clearly sequenced, but distributed/batch training has no explicit validation checkpoints (e.g. verify processes launched, confirm loss decreasing, handle OOM); the Common issues section compensates only partially, so validation gaps cap this at 3.

3 / 5

Progressive Disclosure

Clear overview in SKILL.md with well-signaled one-level-deep references to real files (megatron-integration.md, custom-plugins.md, performance.md) for advanced topics; navigation is easy and appropriately split.

5 / 5

Total

17

/

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 is specific and rich in natural trigger terms but lacks an explicit "Use when..." clause, so it answers "what" well while only weakly implying "when". Adding a trigger-guidance sentence would lift completeness and distinctiveness.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when adding distributed/multi-GPU training to a PyTorch script or when the user mentions multi-GPU, multi-node, DeepSpeed, FSDP, or mixed precision."

Reframe feature list items as verb-led actions (e.g. "Adds distributed support in 4 lines", "Places devices and applies mixed precision automatically") to strengthen the specificity anchor.

Include natural variations users say ("multi-GPU", "multi-node", "scale training") alongside the framework names.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ("4 lines to add distributed support", "Automatic device placement, mixed precision (FP16/BF16/FP8)", "Interactive config, single launch command") but presents them as a feature list rather than verb-led actions, so it sits just below the fully comprehensive anchor.

4 / 5

Completeness

Has a clear "what" but no explicit "Use when..." clause — trigger guidance is only weakly implied by the feature list, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Strong natural terms ("distributed training", "PyTorch", "DeepSpeed/FSDP/Megatron/DDP", "mixed precision", "HuggingFace") that users would actually say, with minor gaps like "multi-GPU"/"multi-node".

4 / 5

Distinctiveness Conflict Risk

Clearly niched to distributed training via Accelerate with named frameworks; mostly distinct with minor overlap risk against raw DeepSpeed/FSDP or Lightning skills.

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

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
OpenLAIR/dr-claw
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.