CtrlK
BlogDocsLog inGet started
Tessl Logo

model-pruning

Reduce LLM size and accelerate inference using pruning techniques like Wanda and SparseGPT. Use when compressing models without retraining, achieving 50% sparsity with minimal accuracy loss, or enabling faster inference on hardware accelerators. Covers unstructured pruning, structured pruning, N:M sparsity, magnitude pruning, and one-shot methods.

56

Quality

65%

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 ./backend/cli/skills/ml-training/model-pruning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 content delivers substantial, domain-specific material with a nearly executable Wanda quick start, but roughly half the code relies on undefined helpers or pseudocode, the workflow lacks a post-pruning validation/feedback loop, and the provided references/wanda.md bundle file is never referenced from SKILL.md while its content is duplicated inline. The skill reads as a monolithic dump rather than a progressive-disclosure overview.

Suggestions

Replace pseudocode and undefined helpers (train_step, prune_layer, fine_tune, prune_model, finetune_dataset, load_calibration_data) with self-contained executable code, or move the Strategies section to a reference file with complete implementations.

Add an explicit validation checkpoint after pruning: evaluate perplexity or a benchmark (the lm_eval snippet is a start), and add a feedback loop such as 'if accuracy degradation > 1%, reduce sparsity by 0.1 and re-prune' before saving the model.

Link the existing references/wanda.md from SKILL.md (e.g., '**Wanda deep-dive**: See [references/wanda.md](references/wanda.md)') and trim the duplicated inline Wanda explanation, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly code-driven and efficient in the Quick Start, but 'Core Concepts' re-explains magnitude-pruning basics, 'Sparsity Patterns' illustrates [1,0,1,0]-style patterns Claude can infer, and ~485 lines inline material that duplicates the provided references/wanda.md. This is 'mostly efficient but includes some unnecessary explanation' (anchor 3), not the minor trimming of anchor 4, since padding recurs across several sections.

3 / 5

Actionability

The Wanda quick start is near-executable, but the Strategies and Production sections depend on undefined functions (train_step, prune_layer, fine_tune, prune_model, finetune_dataset, load_calibration_data), and 'importance = weight^2 / diag(Hessian)' and the 'if no_retraining_budget:' block are pseudocode. This matches anchor 3 ('pseudocode instead of executable code; missing key details'); it is not anchor 4 because roughly half the code blocks cannot run as written.

3 / 5

Workflow Clarity

The production pipeline lists a numbered sequence (load -> calibrate -> prune -> optionally fine-tune -> save) and an Evaluation section exists, but there is no integrated validation checkpoint or feedback loop (e.g., 'if accuracy degradation exceeds X, lower sparsity and re-prune'). Since pruning plus fine-tuning is a batch operation on a large model, the missing-validation cap of 3 applies.

3 / 5

Progressive Disclosure

The bundle provides references/wanda.md (a Wanda deep-dive), yet the body never links to it — no reference to 'references/', 'wanda.md', or any bundle path appears anywhere in SKILL.md. The reference file is orphaned while its subject matter is inlined monolithically, matching anchor 2 ('content that clearly belongs in separate files is inlined; references buried/absent'); it is not anchor 3 because not a single reference is signaled, despite the bundle existing.

2 / 5

Total

11

/

20

Passed

Description

83%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, explicit 'Use when...' triggers, distinctive technique names, and quantitative specifics. The main gaps are a few missing colloquial trigger phrases and slight overlap risk with adjacent model-compression skills via the generic term 'compressing models'.

DimensionReasoningScore

Specificity

Concrete actions ('Reduce LLM size', 'accelerate inference') are backed by named techniques (Wanda, SparseGPT), quantitative targets (50% sparsity), and a coverage list of pruning variants. It falls short of anchor 5 because the action verbs themselves are few, with breadth carried by the technique enumeration rather than a comprehensive set of specific actions.

4 / 5

Completeness

Clearly answers 'what' ('Reduce LLM size and accelerate inference using pruning techniques like Wanda and SparseGPT') and 'when' with an explicit 'Use when compressing models without retraining, achieving 50% sparsity with minimal accuracy loss, or enabling faster inference on hardware accelerators' clause containing concrete trigger phrases. Matches anchor 5 exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'pruning', 'compressing models', 'sparsity', 'faster inference', 'Wanda', 'SparseGPT'. A few natural user phrasings are missing ('make the model smaller', 'shrink the model', 'speed up inference'), matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (LLM pruning) with distinctive named techniques (Wanda, SparseGPT, N:M sparsity) gives minimal conflict risk, but the broad phrase 'compressing models' could overlap with sibling compression skills (quantization, distillation). Mostly distinct with minor overlap risk — anchor 4.

4 / 5

Total

17

/

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

skill_md_line_count

SKILL.md is long (505 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
synthetic-sciences/openscience
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.