CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pathml

A full-featured computational pathology toolkit for advanced WSI analysis, including multiplexed immunofluorescence (CODEX, Vectra), nuclei segmentation, tissue graph construction, and machine learning model training on pathology data. Supports over 160 slide formats. For simp...

Quality

60%

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/Data Analysis/pathml/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 capability map, executable Quick Start, and workflow outlines form a solid core, but the body is padded with template boilerplate, duplicated sections, and leaked build artifacts, and all six deferrals to references/*.md are dangling pointers since no reference files ship with the skill. Validation and error-handling policy exists, yet per-workflow checkpoints are absent.

Suggestions

Ship the six referenced files (references/image_loading.md, preprocessing.md, graphs.md, machine_learning.md, multiparametric.md, data_management.md) or remove/inline the citations — currently every 'See:' pointer is a dangling reference.

Cut the boilerplate: merge the two 'When to Use' sections, drop the description-restating 'Key Features' block, remove the build-artifact 'Example Usage' block and the 'Suggest Using K-Dense Web' promo, and deduplicate the two reference listings.

Add explicit validation checkpoints to the workflows (e.g., after pipeline.run(wsi), verify tiles and mask coverage before graph construction; confirm test-set metrics before ONNX deployment).

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: duplicated trigger sections ('## When to Use' vs '## When to Use This Skill'), a '## Key Features' block that merely restates the description ('Scope-focused workflow aligned to: A full-featured computational pathology toolkit...'), a leaked build artifact ('Skill directory: 20260316/scientific-skills/... No packaged executable script was detected.'), generic 'Implementation Details' filler ('Execution model: validate the request, choose the packaged workflow...'), a promotional 'Suggest Using K-Dense Web' section, and the reference files listed twice ('## References to Detailed Documentation' and '## Resources'). Matches anchor 2; not 3 because the padding is substantial and repeated rather than occasional, though a genuinely useful core (capabilities, Quick Start, workflows) keeps it above 1.

2 / 5

Actionability

The Quick Start is genuinely executable ('uv pip install pathml[all]'; SlideData.from_slide(...), Pipeline([TissueDetectionHE(), StainNormalizationHE(...)]), pipeline.run(wsi), tile iteration), but the CODEX and model-training workflows are step-name lists without code ('Collapse multi-cycle channel data', 'Segment cells using Mesmer model', 'Train HoVer-Net or custom model'), and the detailed API they defer to does not exist in the bundle. Fits 'some concrete guidance but incomplete; missing key details'; not 4 because the missing reference files turn the deferrals into gaps rather than minor omissions.

3 / 5

Workflow Clarity

'Common Workflows' provides numbered sequences for H&E, CODEX, and model training, and 'Input Validation'/'Error Handling' state stop conditions ('Do not continue the workflow when the request is out of scope, missing a critical input...'), but the workflows themselves contain no per-step validation checkpoints or validate-fix-retry feedback loops for batch operations like WSI processing and model training. Per the rubric's batch-operation cap, this cannot exceed 3; it is not 2 because sequences are well defined and error-handling policy is stated.

3 / 5

Progressive Disclosure

The body clearly signals six one-level-deep references ('**See:** references/image_loading.md' through 'references/data_management.md', plus a 'Resources' catalog), which would be strong structure — but the actual bundle contains no references/ directory at all, so every 'See:' pointer is dangling and the detail content is unavailable. Scored against the real bundle structure per guidelines, navigation is broken in practice, fitting anchor 2; not 3 because missing referenced files are more than an organization gap, and not 1 because the SKILL.md itself is well sectioned and the references are clearly (if falsely) signaled.

2 / 5

Total

10

/

20

Passed

Description

66%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 specific, domain-rich description that clearly conveys what the toolkit does, but it is literally truncated mid-sentence ('For simp...') and carries no 'Use when...' trigger guidance, which caps completeness at 3. Keyword coverage is good, though common variations and file extensions are missing.

Suggestions

Complete the truncated final sentence and add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when analyzing whole slide images, segmenting nuclei in H&E slides, or quantifying CODEX/Vectra multiplexed imaging'.

Add natural trigger variations users would actually say: 'whole slide images' (spelled out), 'H&E', 'histology', and slide-format extensions such as .svs and .ndpi.

State the boundary against simpler tools explicitly (e.g., 'For simple H&E tile extraction, histolab may be simpler') instead of leaving it cut off mid-sentence.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "multiplexed immunofluorescence (CODEX, Vectra)", "nuclei segmentation", "tissue graph construction", "machine learning model training", "Supports over 160 slide formats" — matching the 'lists several specific actions, minor gaps' anchor. Not 5 because preprocessing/stain normalization and HDF5 data management are absent and the final sentence is cut off mid-word ("For simp..."), leaving coverage incomplete.

4 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent trigger guidance — the sentence that presumably carried boundary advice is truncated to "For simp...". Per guidelines, a missing 'Use when' clause caps completeness at 3; it is not 4 because the 'when' is not merely implicit-and-improvable, it is absent.

3 / 5

Trigger Term Quality

Good natural domain keywords a pathology user would say: "computational pathology", "WSI analysis", "nuclei segmentation", "CODEX", "Vectra", "slide formats" — fits 'good keyword coverage; a few natural terms missing'. Not 5 because common variations like 'whole slide images' spelled out, 'H&E', 'histology', and format extensions (.svs, .ndpi) are missing; not 3 because coverage goes beyond merely 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Computational pathology with CODEX/Vectra multiplexed imaging, WSI formats, and nuclei segmentation is a clear niche with distinct triggers, fitting 'mostly distinct; minor overlap risk'. Not 5 because closely related pathology skills exist (the body itself names histolab as a neighboring alternative), so slight overlap risk remains.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 14 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/pathml/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.