CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

image-processing

Batch-convert and compress local images with Pillow; use when you need an offline, scriptable pipeline for directory-based processing.

Quality

62%

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 ./scientific-skills/Other/image-processing/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 operational core of this skill is genuinely good — a real script, correct documented flags, honest I/O boundaries, and clear format-specific save rules. It is dragged down by ~50 lines of generic policy boilerplate appended to the body (much of it describing a result .md file the script never produces) and by hedging where the bundled script already contains the exact answers. Cutting the boilerplate and stating the actual PNG mapping and CLI behavior would move both conciseness and actionability up a full point.

Suggestions

Delete or drastically compress the generic sections (When Not to Use, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling) that describe a result .md deliverable and fabrication concerns irrelevant to image conversion — this is pure padding.

Replace hedged statements with the actual behavior from the bundled script: state the PNG mapping (compress_level = round((100 - quality)/10), clamped 0–9), confirm --recursive/--overwrite exist instead of "flags may vary by implementation", and list the supported input formats (.jpg/.jpeg/.png/.tif/.tiff/.bmp/.gif/.webp).

Fix the Quick Validation section: `--help` prints argparse usage, so replace the fabricated "Result file: image_processing_result.md" expected-output block with the real JSON summary the script emits, and add a concrete post-run check (e.g. verify the printed `errors` count is 0 and spot-check an output file) to satisfy the batch-validation checkpoint.

DimensionReasoningScore

Conciseness

The core sections (When to Use through Implementation Details) are efficient, but roughly half the body — "When Not to Use", "Required Inputs", "Recommended Workflow", "Output Contract", "Validation and Safety Rules", and "Quick Validation" — is generic template boilerplate (e.g. "Do not use this skill when the user asks for fabricated results") irrelevant to image conversion. This matches "noticeably verbose; several unnecessary explanations or padded sections"; it is not a 1 because it never explains concepts Claude already knows and the operational core is tight.

2 / 5

Actionability

The main command is concrete and executable (flags verified against the bundled script), but the variant examples are hedged ("flags may vary by implementation") and the PNG compression note says "depending on the mapping used by the script" when the deterministic mapping exists in the bundle. The "Expected output format" block for `--help` is fabricated — argparse prints usage help, not "Result file: image_processing_result.md". This lands on "some concrete guidance but incomplete; missing key details" rather than the mostly-executable level of 4.

3 / 5

Workflow Clarity

A sequence is present (install dependencies → run conversion → optional variants) and the script itself has overwrite protection and error collection, but this is a batch operation and validation checkpoints are vague: "Run a final validation pass" is abstract and the Quick Validation step only exercises `--help` rather than verifying converted outputs. Per the batch-operation cap, workflow clarity cannot exceed 3 without concrete output validation.

3 / 5

Progressive Disclosure

The body has clear section structure, and its one reference ("For additional examples, see `references/examples.md`") is real, one level deep, and clearly signaled; the executable lives in `scripts/` alongside `requirements.txt`. Not a 5 because the body exceeds the simple-skill threshold, examples.md largely duplicates the main example, and format-specific details that could be referenced are instead hedged inline.

4 / 5

Total

12

/

20

Passed

Description

62%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, honest description with a clear what and an explicit use-when clause. Its main weaknesses are limited action coverage and a trigger clause phrased in implementation terms ("offline, scriptable pipeline") rather than natural user language, which weakens trigger-term quality and distinctiveness.

Suggestions

Add concrete natural trigger phrases, e.g. "Use when the user wants to batch-convert images to WebP/JPG/PNG, shrink image file sizes, or prepare image assets for a website or app."

Mention the supported formats and file extensions (WebP, JPG, PNG, .webp, .jpg, .png) so the description covers the most common user phrasings and reduces overlap with generic image skills.

State one or two more concrete capabilities inline (e.g., "preserves folder structure" and "skips existing outputs unless overwrite is enabled") to lift specificity from 2 actions to several.

DimensionReasoningScore

Specificity

"Batch-convert and compress local images with Pillow" names the domain plus two concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because it omits several specifics (output formats, structure preservation, overwrite policy), and the second-person phrasing "use when you need" would be penalized against a 4.

3 / 5

Completeness

It answers both what ("Batch-convert and compress local images with Pillow") and when ("use when you need an offline, scriptable pipeline for directory-based processing"). Not a 5 because the when-clause is narrow and abstract rather than listing concrete trigger phrases a user would naturally say, e.g. "when the user mentions WebP or wants to shrink image file sizes."

4 / 5

Trigger Term Quality

Terms like "batch-convert", "compress", "images", "offline", and "directory-based processing" are relevant, but common natural variations users would say ("optimize images", "WebP", "resize", file extensions like .png/.jpg) are missing. It sits at "some relevant keywords but missing common variations or synonyms," not the good-coverage level of 4.

3 / 5

Distinctiveness Conflict Risk

The framing (offline, Pillow-based, directory-based batch pipeline) carves a fairly distinct niche with minor overlap risk against general image-editing or format-conversion skills. Not a 5 because it does not name its distinct triggers (e.g., WebP conversion, asset preparation for the web), leaving some ambiguity against image-utility skills.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/image-processing/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.