CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

multi-omics-clinical-integration-planner

Designs complete research plans that integrate clinical variables with multi-omics data from a user-provided biomedical direction. Always use this skill whenever a user wants to design, scope, or structure a study that combines clinical variables with transcriptomics, proteomics, metabolomics, epigenomics, or related omics layers for mechanism interpretation, biomarker development, risk stratification, treatment-response analysis, or translational use. It should define the clinical use case, alignment across data layers, feature-reduction and fusion logic, modeling route, mechanism-interpretation layer, validation ladder, and four workload configurations (Lite / Standard / Advanced / Publication+). Never fabricate datasets, accession numbers, sample counts, metadata completeness, platform coverage, literature references, PMIDs, DOIs, or validation status. Always include the mandatory Dataset Disclaimer immediately before any workflow section that mentions datasets or public resources.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 structurally excellent — a fixed execution sequence with a mandatory dependency check, a fully specified output template, and an exemplary one-level-deep reference mapping — but it is heavily padded: the same rules (fabrication ban, disclaimer placement, risk review, should-nots, DESeq2/limma) are each restated three to four times across sections. Consolidating the duplicated blocks would cut the file by roughly a third with no loss of operational content.

Suggestions

Consolidate the three copies of the self-critical risk-review checklist (Step 7, Section L, and Hard Rule 13) into a single definition, referenced by the other two.

State each hard rule once: fold the DESeq2/limma rule, the Dataset Disclaimer placement rule, and the fabrication ban into the Hard Rules section alone, removing their duplicates in Formatting Expectations, Step 6, Section H, Step 4.5, and Core Function.

Merge 'Sample Triggers' into the Input Validation examples and fold 'What This Skill Should Not Do' into the Core Function 'should not' list, removing two near-duplicate sections.

Include the actual Dataset Disclaimer template inline (or a one-line pointer to where it is defined in references/dataset-recommendation-and-disclaimer.md), since the body mandates it repeatedly without ever showing it.

DimensionReasoningScore

Conciseness

The body is noticeably padded through wholesale repetition rather than concept over-explanation: the risk-review checklist appears three times (Step 7, Section L, Hard Rule 13); the fabrication ban appears in the frontmatter, Step 4.5, Core Function, and Hard Rule 1; the Dataset Disclaimer placement rule is stated in Step 6, Section H, and Hard Rule 2; the DESeq2/limma rule is stated twice (Formatting Expectations and Hard Rule 7); 'Sample Triggers' largely duplicates the Input Validation examples; and 'What This Skill Should Not Do' duplicates 'Core Function should not'. This matches 'several unnecessary explanations or padded sections'; it is not 3 because the redundancy is systemic (~40% of the body could be cut) rather than occasional tightening, and not 1 because nothing explains concepts Claude already knows and all content is operational.

2 / 5

Actionability

For an instruction-only skill the guidance is mostly executable: a fixed 7-step execution order, a mandatory A-L output structure with per-section content specs (including exact table columns for Sections C and F), a copy-paste redirect template, and concrete method defaults ('count data → DESeq2 (recommended default)', 'non-count normalized data → limma'). It is not 5 because some key artifacts are named but never shown inline — the 'mandatory Dataset Disclaimer' text itself is never provided in SKILL.md, and no example output section or filled-in configuration table is given; it is not 3 because the guidance is specific and complete enough to execute without guessing at structure.

4 / 5

Workflow Clarity

The 7 steps run in explicit order ('always run in order') and include a genuine pre-output checkpoint: 'Step 5 — Dependency Consistency Check (mandatory before output)' with a five-point checklist, plus a closing risk review in Step 7. This matches 'clear sequence with most checkpoints present'; it is not 5 because Step 5 specifies no remediation loop (what to do when the consistency check fails, or re-checking after fixes) and the dependency check is stated once without a verify-fix-revalidate cycle, and it is not 3 because the checkpoints are explicit and detailed rather than implicit.

4 / 5

Progressive Disclosure

The 'Reference Module Integration' section maps each of the nine reference files to the exact output section where it must be used ('references/study-patterns.md → use when selecting the dominant clinical–multi-omics study pattern in Section B', etc.), all nine referenced paths exist in the references/ directory, references are one level deep, and details (method library, dataset disclaimer text, validation hierarchy, figure plan) are appropriately split out of the overview. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation.

5 / 5

Total

15

/

20

Passed

Description

92%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 strong: it states concrete deliverables, gives an explicit and detailed 'use when' clause with natural trigger terms, and defines a distinctive niche. The only weakness is mild padding (the fabrication-prohibition and disclaimer sentences describe internal rules rather than triggers) and a few missing natural synonyms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions and deliverables: 'define the clinical use case, alignment across data layers, feature-reduction and fusion logic, modeling route, mechanism-interpretation layer, validation ladder, and four workload configurations (Lite / Standard / Advanced / Publication+)'. This matches the anchor for comprehensive coverage of specific concrete actions; it is not score 4 because there are no meaningful gaps in the action inventory for its domain, and it stays in third person ('Designs complete research plans').

5 / 5

Completeness

It explicitly answers both questions: what it does ('Designs complete research plans that integrate clinical variables with multi-omics data...') and when to use it ('Always use this skill whenever a user wants to design, scope, or structure a study that combines clinical variables with transcriptomics, proteomics, metabolomics, epigenomics, or related omics layers for...'). This matches the anchor with clear 'what' AND explicit 'when' with concrete trigger phrases; score 4 would require the 'when' clause to be only partially explicit, which it is not.

5 / 5

Trigger Term Quality

Good natural-term coverage: users would say 'design, scope, or structure a study', 'multi-omics', the named layers 'transcriptomics, proteomics, metabolomics, epigenomics', and use cases like 'biomarker development, risk stratification, treatment-response analysis'. It is not 5 because a few natural phrasings users would plausibly say are missing (e.g., 'genomics', 'study design', 'clinical data integration', 'multi-omics study'); it is not 3 because coverage clearly exceeds 'some relevant keywords' with several synonyms and use-case variants.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — planning studies that combine clinical variables with multi-omics layers — with triggers specific to that combination (omics layer names plus clinical-variable integration plus design/scoping intent), so conflict risk with adjacent skills (single-omics analysis, literature review, manuscript writing) is minimal and those boundaries are even named. Not 4: no significant overlap with closely related skills is evident from the trigger language.

5 / 5

Total

19

/

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

awesome-med-research-skills/Protocol Design/multi-omics-clinical-integration-planner/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.