CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-proteomics-analysis

Mass-spec proteomics analysis — protein identification, quantification (LFQ, TMT, iTRAQ), differential expression (tumor vs normal, treatment vs control), PTM identification, and pathway enrichment on protein lists. Use when you have proteomics MS output, asking about protein abundance differences, or doing systems-level proteomic interpretation.

Quality

76%

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 ./plugins/tooluniverse/skills/tooluniverse-proteomics-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 carries genuinely valuable non-obvious knowledge (live-verified ProteomicsDB behaviors, quantified minimums, decision trees, evidence grading) organized in a clear gated 8-phase workflow, but it pads token budget with textbook protein-ID/PTM explanations, defers all core analysis procedures to a PHASE_DETAILS.md that is missing from the bundle, and provides no executable code for the main analysis.

Suggestions

Trim the textbook concept explanations in 'Protein Identification Reasoning' and the PTM section (PMF mechanics, what MS/MS scoring is, PTM definitions, stoichiometry basics) that Claude already knows; keep only the workflow-specific thresholds, decision trees, and evidence grading.

Fix the dangling reference: either ship PHASE_DETAILS.md in the skill bundle or inline the essential per-phase procedures in SKILL.md — currently the detailed half of the workflow ('See [PHASE_DETAILS.md](PHASE_DETAILS.md) for detailed procedures per phase') points to a nonexistent file.

Add one minimal executable example for the core DE workflow (e.g., a pandas/scipy snippet implementing the stated 2+-unique-peptide filter and Benjamini-Hochberg correction) so Phase 2-3 guidance is copy-paste ready instead of a capability list.

DimensionReasoningScore

Conciseness

Mostly efficient but padded in places: the 'Protein Identification Reasoning' section explains textbook MS concepts Claude already knows ('Peptide mass fingerprinting (PMF): Intact protein digested → measured peptide masses compared against theoretical digest', MS/MS scoring, protein inference), the PTM section opens with definitional material ('PTMs (phosphorylation, ubiquitination, acetylation, glycosylation) add biological complexity beyond protein abundance'), and the 'Comprehensive analysis of mass spectrometry-based proteomics data...' paragraph restates the header. The genuinely non-obvious material (verified-live ProteomicsDB gotchas, quantified minimums, evidence grading) does earn its tokens, but the whole could be tightened — anchor 3 fits better than 4 because the textbook explanations are more than a minor trim.

3 / 5

Actionability

There is concrete guidance — the exact CLI form `tu run read_executed_notebook '{"data_folder":"<path>","search":"<keyword>"}'`, a tool-by-tool table with field-level caveats ('expression_value (log10-normalized, cross-tissue-comparable) vs. unnormalized_intensity (NOT comparable across tissues; never rank on this field)'), and numeric thresholds ('localization probability > 0.75', 'FDR < 0.05 standard'). But the core analysis phases offer only capability lists ('Limma, DEP, MSstats for statistical testing') and defer all procedures to 'See [PHASE_DETAILS.md](PHASE_DETAILS.md) for detailed procedures per phase' — with no code or steps for import/preprocessing/DE in the body, key execution details are missing (and the referenced file is absent from the bundle). Not below 3: the guidance that is present is specific and usable, not vague hints.

3 / 5

Workflow Clarity

A clear 8-phase pipeline ('Phase 1: Data Import & QC ... Phase 8: Generate Report') gated by an explicit pre-check branch ('Only follow this skill's re-analysis recipe below if **none** of the above exist'), with quantified checkpoints acting as validation gates ('At least 3 biological replicates per condition (non-negotiable for reliable statistics)', 'Filter to proteins with 2+ unique peptides', plus differential-expression strength tiers and evidence grading). Not 5: there are no explicit error-recovery/feedback loops and per-phase validation detail is delegated to a missing file. Not 3: the sequence and most checkpoints are present and explicit.

4 / 5

Progressive Disclosure

The body is well-sectioned and its one reference is clearly signaled twice ('See [PHASE_DETAILS.md](PHASE_DETAILS.md) for detailed procedures per phase' and again under 'Reference Files'), but scored against the actual bundle: no references/, scripts/, or assets/ directories exist and PHASE_DETAILS.md is nowhere in the workspace, so the skill's single primary disclosure pointer dangles and the detailed half of the workflow cannot be loaded. The ~20-line ProteomicsDB tool reference is also inlined. Good in-file structure with a broken, load-bearing reference lands between anchors 2 and 3.

3 / 5

Total

13

/

20

Passed

Description

87%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: concrete, comprehensive capability enumeration with an explicit 'Use when...' trigger clause and a clearly delineated proteomics niche. Its only deductions are a second-person trigger phrasing and a few missing natural synonyms (tool-output names, 'phosphoproteomics').

Suggestions

Rewrite the trigger clause in third person/gerund form, e.g. 'Use when working with proteomics MS output or when the user asks about protein abundance differences', to satisfy the third-person-voice guideline.

Add natural synonyms users actually say — 'differential protein expression', 'phosphoproteomics', and tool-output names (MaxQuant, Spectronaut, DIA-NN) — to round out trigger-term coverage.

DimensionReasoningScore

Specificity

The capability list is comprehensive and concrete — 'protein identification, quantification (LFQ, TMT, iTRAQ), differential expression (tumor vs normal, treatment vs control), PTM identification, and pathway enrichment on protein lists' — matching the anchor-5 example style, but the trigger clause uses second person ('Use when you have proteomics MS output, asking about protein abundance differences'), so the third-person-voice guideline costs it one point.

4 / 5

Completeness

Explicitly answers both what ('protein identification, quantification (LFQ, TMT, iTRAQ), differential expression..., PTM identification, and pathway enrichment on protein lists') and when ('Use when you have proteomics MS output, asking about protein abundance differences, or doing systems-level proteomic interpretation') with concrete trigger phrases — the same structure as the anchor-5 reference example.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'proteomics', 'mass-spec', 'MS output', 'protein abundance differences', 'tumor vs normal, treatment vs control', 'systems-level proteomic interpretation', plus method acronyms LFQ/TMT/iTRAQ. A few natural terms users would actually say are missing — 'differential protein expression', 'phosphoproteomics', and tool-output names (MaxQuant, Spectronaut, DIA-NN) — matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (mass-spec proteomics) with triggers consistently anchored to proteins and MS output ('proteomics MS output', 'protein abundance differences'), and even generic terms are qualified to stay in-niche ('pathway enrichment on protein lists'). 'Differential expression (tumor vs normal...)' is vocabulary shared with transcriptomics skills, but the surrounding qualifiers leave only minimal conflict risk — anchor 5, not 4.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugins/tooluniverse/skills/tooluniverse-proteomics-analysis/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.