CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

distributed-training-pytorch-lightning

High-level PyTorch framework with Trainer class, automatic distributed training (DDP/FSDP/DeepSpeed), callbacks system, and minimal boilerplate. Scales from laptop to supercomputer with same code. Use when you want clean training loops with built-in best practices.

Quality

74%

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 ./cli-tool/components/skills/ai-research/distributed-training-pytorch-lightning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, code-first skill body with concrete quick-start, five executable workflows, troubleshooting, and genuinely useful one-level-deep reference files. The main costs are token padding (hardware/precision/Resources sections and duplicated LightningModule examples) and minor executability gaps (undefined variables in a few snippets).

Suggestions

Remove or compress the Hardware requirements, Precision options, and Resources sections — capability lists, GitHub stars, and Discord links add tokens without adding guidance Claude does not already have.

De-duplicate the LightningModule definitions: Workflows 1 and 2 re-show training_step/configure_optimizers already demonstrated in the quick start; show only the delta (validation_step, test_step).

Make every snippet self-contained: define train_dataset (a simple Dataset or random tensor example) and instantiate `model = LitModel()` in Workflow 2, and replace the `loss = ...` placeholder in the troubleshooting example with real code.

DimensionReasoningScore

Conciseness

The quick start and workflow code blocks are lean and payload-carrying, but several sections pad tokens with what Claude already knows: the hardware requirements matrix, the precision options list, a Resources section with GitHub star counts and "Used by: Kaggle winners", and noticeable duplication (Workflow 1 and Workflow 2 re-implement the same LightningModule already shown in the quick start). Not 4 because the duplication and marketing filler go beyond 'minor instances that could be trimmed'.

3 / 5

Actionability

Mostly executable, concrete code: a complete 3-step quick start, working Trainer configurations, ModelCheckpoint/EarlyStopping usage, and a CosineAnnealingLR optimizer dict. Not 5 due to minor gaps: `train_dataset` is never defined in the quick start, Workflow 2 calls `trainer.fit(model, ...)` with `model` never instantiated in that snippet, and the troubleshooting snippet uses the placeholder `loss = ...`.

4 / 5

Workflow Clarity

The conversion workflow is explicitly numbered (Step 1/2/3), each workflow states its result, and the Common issues section provides error→fix recovery guidance. Not 5 because there are no explicit validation checkpoints (e.g., verify a single batch trains on CPU before scaling to 8 GPUs), though the operations are non-destructive so no cap applies; not 3 because sequencing plus troubleshooting feedback clearly exceeds a bare step list.

4 / 5

Progressive Disclosure

Good structure with real, clearly signaled one-level-deep references (references/callbacks.md, references/distributed.md, references/hyperparameter-tuning.md — all present, none nesting further references). Not 5 because the ~330-line body is more than a lean overview: the inline callbacks and LR-scheduling workflows overlap with content that belongs in references/callbacks.md, so the split is good rather than exemplary.

4 / 5

Total

15

/

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.

A solid description with a clear 'what' and an explicit 'Use when' clause and strong domain keywords. Its weaknesses are the second-person 'you' phrasing (which costs specificity), and the absence of the framework's own name 'PyTorch Lightning' as a trigger term, which weakens both trigger matching and distinctiveness against neighboring PyTorch-ecosystem skills.

Suggestions

Rewrite the trigger clause in third person, e.g., 'Use when the user wants to train models with PyTorch Lightning, needs distributed training (DDP/FSDP/DeepSpeed), or mentions Lightning, Trainer, or callbacks.'

Include the framework's natural name and aliases ('PyTorch Lightning', 'Lightning') explicitly in the description so users who say the framework's name trigger the skill.

Make the 'when' clause scenario-based (single vs multi-GPU training, boilerplate-free training loops) rather than the vague desire 'clean training loops with built-in best practices'.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("Trainer class", "automatic distributed training (DDP/FSDP/DeepSpeed)", "callbacks system") which would fit anchor 4, but the 'Use when you want...' clause is second-person voice, and the judging guidelines mandate a 1-point specificity penalty for second-person phrasing. It is above anchor 2 because the actions named are specific rather than minimal or generic.

3 / 5

Completeness

Both parts are present: a clear 'what' ("High-level PyTorch framework with Trainer class, automatic distributed training...") and an explicit 'when' ("Use when you want clean training loops with built-in best practices"). Not 5 because the 'when' clause expresses a desire rather than concrete trigger scenarios a user would verbalize (e.g., 'when the user mentions Lightning or wants multi-GPU training').

4 / 5

Trigger Term Quality

Good coverage of natural terms users would say: "PyTorch", "distributed training", "DDP", "FSDP", "DeepSpeed", "callbacks", "training loops". Not 5 because the single most natural trigger phrase — "PyTorch Lightning" / "Lightning" — never appears in the description itself, so a user naming the framework would not obviously match.

4 / 5

Distinctiveness Conflict Risk

Terms like "Trainer class", "DDP/FSDP/DeepSpeed", and "callbacks system" form a distinct niche unlikely to trigger for unrelated skills. Not 5 because the description says "High-level PyTorch framework" without naming Lightning, leaving minor overlap risk with plain PyTorch or Accelerate-style 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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

davila7/claude-code-templates

Path

cli-tool/components/skills/ai-research/distributed-training-pytorch-lightning/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.