CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

microscopy-scale-bar-adder

Add accurate, publication-ready scale bars to microscopy images given pixel-to-unit calibration data.

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/microscopy-scale-bar-adder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 well-organized and mostly efficient, but its central promise fails on execution: every documented CLI example is incompatible with the bundled script's actual argument names, defaults, and position values, so the skill's copy-paste commands error out. Generic workflow/response boilerplate and a review-process banner add padding, and the advertised batch-processing use case lacks a validation loop.

Suggestions

Reconcile the documentation with scripts/main.py: use the real flags (--input, --scale-length, --scale-unit, --pixels-per-unit), hyphenated positions (bottom-right etc.), actual defaults (bar-thickness 8, output default output_with_scalebar.png), and the script's exact error strings — or update the script to match the doc.

Remove the 'POLISHED CANDIDATE — Requires Fresh Evaluation' banner and the generic Workflow/Response/Fallback template boilerplate, which add ~30 lines of non-task content.

Add an output-verification checkpoint for the batch-processing use case (e.g., re-measure the rendered bar length in pixels against the expected calibration) so batch workflows include a validate-fix-retry loop.

DimensionReasoningScore

Conciseness

Core sections (Usage, Parameters, Implementation Notes, Error Handling) are tight and earn their tokens, but the body carries padding: the 'POLISHED CANDIDATE — Requires Fresh Evaluation' banner (meta-commentary irrelevant to skill execution), a generic 5-step Workflow ('Confirm the user objective... Return a structured result') with no scale-bar-specific content, and boilerplate Response/Fallback templates. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened'. Not a 2: the majority of the document is efficient; not a 4: the boilerplate sections are more than minor.

3 / 5

Actionability

Commands and parameter tables look copy-paste ready, but they document a CLI that does not match the bundled scripts/main.py: the doc says '--image/--scale/--unit' and positions 'bottomright', while the script implements '--input/--scale-length/--scale-unit' and 'bottom-right', with different defaults (bar-thickness 3 vs 8, output '<input>_scalebar.<ext>' vs 'output_with_scalebar.png') and different error strings. Every documented usage example would fail with an argparse error. Fits 'some concrete guidance but incomplete... missing key details'. Not a 4: the guidance is not executable against the actual bundle; not a 2: the structure and specificity of the guidance is genuinely high, only the interface mapping is wrong.

3 / 5

Workflow Clarity

A concrete operational sequence exists in Implementation Notes (path validation → open → compute pixel length → draw bar → draw label → save) with explicit error checkpoints and exit codes, but the headline 'Workflow' section is generic agent boilerplate with no validation checkpoints. The skill explicitly lists 'Batch-processing image sets' as a use case, yet no output verification loop exists (e.g., checking rendered bar length against calibration), and the guidelines cap workflow clarity at 3 for batch operations without validation. Not a 4: the batch use case lacks a validate-fix-retry loop and the main Workflow section has no real checkpoints.

3 / 5

Progressive Disclosure

The bundle is a single script (scripts/main.py) which the body references by a real, correct path; sections are well-organized with clear headers (When to Use, Usage, Parameters, Features, Error Handling), no nested references, and content appropriately kept in one level. Fits 'good structure; most content is appropriately placed; references mostly clear; minor organization gaps'. Not a 5: the doc is ~130 lines with generic templates inlined that could be trimmed or split, and there is no signaling of where deeper material lives beyond the script path.

4 / 5

Total

13

/

20

Passed

Description

53%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 concrete and correctly scoped to a distinct niche, with appropriate third-person voice and no fluff. Its main weakness is the missing 'Use when...' trigger clause and thin natural-keyword coverage, which the guidelines cap and penalize respectively.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions scale bars, calibrating microscopy images, µm/nm scale, or preparing microscopy figures for publication.'

Include natural synonyms and file extensions in the description (TIFF, .tif, µm/micron calibration) to improve trigger-term coverage.

Optionally mention 1-2 more concrete capabilities (batch styling consistency, configurable bar position/units) to lift specificity from one action to several.

DimensionReasoningScore

Specificity

The description names its domain ('microscopy images') and exactly one concrete action ('Add accurate, publication-ready scale bars') with an input qualifier ('given pixel-to-unit calibration data'). It matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive' — no mention of batch processing, configurable styling/position, or output formats. Not a 4: it does not list several specific actions; not a 2: the action and domain are concrete, not generic.

3 / 5

Completeness

The 'what' is clear (add calibrated scale bars to microscopy images), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the guidelines explicitly cap completeness at 3 for this. Matches the anchor 'has a clear what but when is missing or only weakly implied'. Not a 2: the what is specific, not vague; not a 4: the when is entirely absent, not merely under-specified.

3 / 5

Trigger Term Quality

Relevant keywords are present ('scale bars', 'microscopy images', 'calibration', 'publication') but common variations and synonyms users would naturally say are missing — no 'Use when' phrasing, no file extensions (.tif, TIFF, PNG), no units (µm, nm). Fits the anchor 'some relevant keywords but missing common variations or synonyms'. Not a 4: coverage of natural trigger terms is thin, limited to the domain nouns.

3 / 5

Distinctiveness Conflict Risk

'Scale bars to microscopy images' carves out a clear niche with little overlap against general image-annotation or figure-preparation skills. Fits 'mostly distinct; minor overlap risk with closely related skills' — a generic 'annotate images' or 'prepare publication figures' skill could plausibly co-trigger. Not a 5: the absence of explicit trigger phrases means boundary cases aren't crisply separated.

4 / 5

Total

13

/

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/microscopy-scale-bar-adder/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.