CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pytorch-fsdp

Fully sharded data-parallel training for large models.

39

Quality

49%

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 ./optional-skills/mlops/pytorch-fsdp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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 an auto-generated template shell: it correctly points to a large, real common-patterns reference, but contains no actual FSDP guidance, substantial boilerplate filler, and references to bundle files that do not exist. The skill's real content lives entirely in the reference files while SKILL.md adds little navigational or instructional value.

Suggestions

Remove boilerplate sections ('When to Use This Skill' tautologies, 'Resources', 'Notes', 'Updating', and 'Add helper scripts/assets here' placeholders) and keep only sections that carry real information.

Fix or remove references to non-existent files — 'getting_started', 'tutorials', 'api', and 'guides' are not in references/ — and describe other.md and index.md by their actual contents instead of 'Other documentation'.

Inline a minimal copy-paste FSDP2 wrapping example in the body so the skill is actionable on its own, and standardize the file-reading instruction to one consistent tool name instead of both 'read_file' and 'view'.

DimensionReasoningScore

Conciseness

The body is padded with sections that add no value: 'When to Use This Skill' is tautological ('Working with pytorch-fsdp'), and 'Resources', 'Notes', and 'Updating' plus placeholders like 'Add helper scripts here' are pure boilerplate. It does not reach 1 because it is short, contains no explanation of concepts Claude already knows, and the Quick Reference section does real work.

2 / 5

Actionability

The only concrete instruction is 'load it with read_file when you need wrapping, sharding-strategy, checkpoint, or mixed-precision examples' pointing at references/common-patterns.md; the rest is high-level direction like 'Use the appropriate category reference file (api, guides, etc.)' with no executable code or commands in the body. This matches 'minimal concrete guidance; high-level hints but missing the specific steps', and does not reach 3 since even the pseudocode-level guidance is mostly about navigating files rather than doing FSDP work.

2 / 5

Workflow Clarity

There is a rough sequence (trigger check → Quick Reference → reference files) but many gaps: 'Working with This Skill' branches to non-existent files (getting_started, tutorials, api, guides), and no validation or checkpoint of any kind is described. It is above anchor 1 because a rough navigational sequence is present, but below 3 because the steps are poorly defined and reference files that do not exist.

2 / 5

Progressive Disclosure

The Quick Reference section is a well-signaled, one-level-deep pointer to a real large file (references/common-patterns.md), which is good practice. However, the 'Reference Files' section lists other.md with only the vague label 'Other documentation', omits index.md, and the body directs readers to files (getting_started, tutorials, api, guides) that are not in the bundle, breaking navigation. This sits between 'minimal structure' (2) and 'good structure' (4).

3 / 5

Total

9

/

20

Passed

Description

48%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 concise and names a specific domain, giving a clear 'what', but it is missing any 'use when' trigger guidance and enumerates no concrete capabilities. It reads like a one-line category label rather than a triggering description.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user mentions FSDP, sharding, or distributed training of large PyTorch models.'

Enumerate concrete capabilities such as wrapping models with FullyShardedDataParallel, choosing sharding strategies, checkpointing, mixed precision, and CPU offloading.

Include natural trigger keywords and synonyms users actually say: 'FSDP', 'PyTorch', 'distributed training', 'model sharding'.

DimensionReasoningScore

Specificity

The description names the domain ("fully sharded data-parallel training") but states only one minimal, generic action — training large models — with no enumeration of concrete capabilities like wrapping models, choosing sharding strategies, checkpointing, or mixed precision. It matches the anchor 'Names the domain but actions are minimal or generic' and does not reach 3, which requires 1-2 distinct concrete actions.

2 / 5

Completeness

The 'what' is clearly stated ("Fully sharded data-parallel training for large models") but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It does not fall to 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

"fully sharded data-parallel training" and "large models" are relevant keywords a user working with FSDP would say, but the description omits common variations and synonyms such as "FSDP", "PyTorch", "distributed training", "sharding", or "mixed precision". This is 'some relevant keywords but missing common variations or synonyms', above anchor 2 (which expects only generic terms).

3 / 5

Distinctiveness Conflict Risk

Fully sharded data parallelism is a clear niche with distinct terminology, so it is unlikely to trigger for unrelated skills; there is minor overlap risk with closely related distributed-training skills (DDP, model parallelism). It does not reach 5 because the description lacks the acronym FSDP and explicit trigger phrases that would make the niche fully distinct.

4 / 5

Total

12

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/mlops/pytorch-fsdp/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.