CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

microbiome-diversity-reporter

Interpret Alpha and Beta diversity metrics from 16S rRNA sequencing results.

Quality

63%

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/Academic Writing/microbiome-diversity-reporter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill body contains genuinely useful, executable reference material — a real CLI with documented parameters, input formats, and example output — wrapped in a large amount of generated template boilerplate. The main quality problems are padding, broken self-references, and generic checklist sections that bloat the context window and should be moved to reference files or removed.

Suggestions

Cut the template filler sections ('Key Features', 'Evaluation Criteria', 'Lifecycle Status', 'Output Requirements', 'Response Template', and the duplicate 'Quick Check'/'Audit-Ready Commands' blocks) or move them to references/audit-reference.md, keeping SKILL.md focused on Usage, Input Format, Output, and Error Handling.

Fix the broken cross-references — 'See `## Usage` above' and 'See `## Workflow` above' point to sections defined later — and remove the non-portable 'cd "20260318/scientific-skills/..."' example in favor of a relative path from the skill root.

Ship a real requirements.txt (the Prerequisites section runs 'pip install -r requirements.txt' but no such file exists) and make the Workflow steps concrete by tying each step to the actual commands (e.g. py_compile check, then the --input/--beta/--full invocations) instead of generic directives.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with padded template sections: 'Key Features' ('Packaged executable path(s)', 'Structured execution path'), an empty 'Evaluation Criteria' checklist, 'Lifecycle Status' filler ('Planned Improvements: Performance optimization'), 'Quick Check' duplicating 'Audit-Ready Commands', two separate 'References' sections, and broken self-references ('See `## Usage` above' and 'See `## Workflow` above' both point to sections that appear later in the file). It does not hit score 1 because it avoids long explanations of concepts Claude already knows.

2 / 5

Actionability

The Usage section provides fully executable commands ('python scripts/main.py --input otu_table.tsv --metric shannon --output alpha_report.html'), a concrete parameter table, exact input file formats, and a realistic example output JSON — copy-paste ready for the common cases. Minor gaps keep it below 5: 'Prerequisites' tells the user to run 'pip install -r requirements.txt' but no requirements.txt exists in the bundle, and the Example Usage section contains a non-portable 'cd "20260318/scientific-skills/..."' path plus self-referential filler ('See `## Usage` above for related details.') instead of instructions.

4 / 5

Workflow Clarity

A 5-step Workflow is listed in order with an explicit fallback step, and 'Quick Check' gives one validation command (py_compile), but the steps are generic directives ('Confirm the user objective...', 'Use the packaged script path or the documented reasoning path...') rather than concrete sequenced actions with checkpoints — matching 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The bundle structure is sound — the referenced file references/audit-reference.md exists, is one level deep, and is clearly linked, and scripts/main.py exists as claimed — but the ~300-line SKILL.md body inlines large generic blocks (Risk Assessment, Security Checklist, Evaluation Criteria, Output Requirements, Response Template, audit commands) that clearly belong in the references directory, fitting 'some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

12

/

20

Passed

Description

61%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 concise, domain-specific, and correctly scoped to 16S rRNA microbiome diversity analysis, but it is a single-clause 'what' statement. It names only one action and omits any 'Use when...' trigger guidance, limiting both completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when analyzing microbiome 16S rRNA / OTU / ASV data, computing diversity indices (Shannon, Simpson, Chao1), or comparing sample composition.'

List the concrete actions the skill performs beyond 'interpret' — computing alpha diversity indices, beta diversity distances/PCoA, group significance testing (PERMANOVA), and generating HTML/JSON/Markdown reports.

Include common synonyms users would say, such as 'microbiome', 'OTU table', 'species richness', and 'Beta diversity' alternatives like 'UniFrac' or 'PCoA'.

DimensionReasoningScore

Specificity

The phrase 'Interpret Alpha and Beta diversity metrics from 16S rRNA sequencing results' names the domain and exactly one action ('Interpret ... metrics'); it never mentions computing indices, generating reports, statistical tests, or visualizations, so it matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than the several-specific-actions anchors.

3 / 5

Completeness

The 'what' is clear (interpreting alpha/beta diversity metrics from 16S results), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3 ('clear what, when missing or only weakly implied').

3 / 5

Trigger Term Quality

'Alpha diversity', 'Beta diversity', '16S rRNA', and 'sequencing' are natural phrases a microbiome researcher would say, giving good keyword coverage, but common variations such as 'microbiome', 'OTU', 'ASV', 'Shannon', or 'species richness' are missing, which fits the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

'16S rRNA sequencing' pins a clear bioinformatics niche with distinct triggers, but the generic verb 'Interpret' leaves minor overlap risk with closely related sequencing-analysis or general data-interpretation skills, fitting 'mostly distinct; minor overlap risk'.

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/Academic Writing/microbiome-diversity-reporter/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.