CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pytorch-patterns

PyTorch deep learning patterns and best practices for building robust, efficient, and reproducible training pipelines, model architectures, and data loading. Use when writing or reviewing PyTorch training loops, model architectures, or data loading, or when a run will not reproduce.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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, code-complete pattern reference with good organization and lean prose. Its main weakness is structure: everything is inlined in one large SKILL.md with no reference files, and the AMP content is duplicated across sections.

Suggestions

Move the pattern catalog (e.g., architecture patterns, data pipeline patterns, performance optimization) into references/ files (architectures.md, data-pipelines.md, performance.md) and keep SKILL.md as a concise overview linking to them one level deep.

Deduplicate the mixed-precision content: keep the GradScaler/autocast pattern in one place and reference it from the training-loop example instead of repeating it in Performance Optimization.

Trim the Quick Reference table to idioms not already demonstrated in code, or fold its entries into the relevant sections to reduce token overhead.

DimensionReasoningScore

Conciseness

The body is lean and code-first with terse framing, but the AMP/GradScaler pattern is duplicated (Training Loop Patterns and Performance Optimization) and the Quick Reference table restates what the code comments already say — minor trimming opportunities, not padding.

4 / 5

Actionability

Every section provides complete, executable, copy-paste-ready Python with explicit good/bad contrasts (e.g., the full train_one_epoch with autocast, scaler, clipping; checkpoint save/load with weights_only=True), covering the common PyTorch cases.

5 / 5

Workflow Clarity

Sections are clearly organized with an explicit 'When to Activate' guide and unambiguous single-purpose patterns, but it is a reference catalog with no multi-step sequence or validation checkpoints — good structure with minor gaps rather than an explicit sequenced workflow.

4 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, or assets/), and roughly 390 lines of pattern-catalog material that would naturally live in separate reference files are fully inlined — some structure via clear section headers, but content that should be separate is inline and nothing is split out.

3 / 5

Total

16

/

20

Passed

Description

87%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 strong description: third-person voice, concrete domain and capability areas, and an explicit 'Use when' clause with natural trigger phrases including the subtle reproducibility trigger. Minor gaps in keyword breadth (GPU memory, debugging, speed terms) keep trigger coverage just short of comprehensive.

DimensionReasoningScore

Specificity

Names the domain plus three concrete capability areas — 'training pipelines, model architectures, and data loading' — but 'robust, efficient, and reproducible' are quality adjectives rather than concrete actions, so coverage is several-specific-actions with minor gaps rather than comprehensive.

4 / 5

Completeness

It clearly and explicitly answers both 'what' (PyTorch patterns for building training pipelines, model architectures, and data loading) and 'when' ('Use when writing or reviewing PyTorch training loops... or when a run will not reproduce') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

'writing or reviewing PyTorch training loops, model architectures, or data loading, or when a run will not reproduce' covers the natural phrases users say, but misses common variations like 'GPU memory', 'training speed', 'debugging training', 'dataloader', or file extensions, so it sits between good and comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The PyTorch-specific scope and distinct triggers ('PyTorch training loops', 'run will not reproduce') give it a clear niche with minimal overlap risk against neighboring ML or Python skills.

5 / 5

Total

18

/

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_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/pytorch-patterns/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.