CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dual-disease-shared-transcriptome-biomarker-research-planner

Generates complete dual-disease shared-transcriptome biomarker and hub-gene research designs from a user-provided disease pair and shared-biology direction. Always use this skill whenever a user wants to design, plan, or build a non-oncology two-disease transcriptome study centered on per-disease differential expression, shared-signal intersection or concordance, PPI-based hub-gene prioritization, diagnostic evaluation across both diseases, immune infiltration context, pathway interpretation, and optional orthogonal validation. Covers five study patterns (shared-DEG-first workflow, hub-gene-first shared-biomarker workflow, hybrid shared-biomarker compression workflow, immune-context shared-biomarker workflow, orthogonal validation workflow) and always outputs four workload configs (Lite / Standard / Advanced / Publication+) with recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path...

Quality

88%

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

81%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.

A well-structured, highly actionable instruction skill with an explicit 7-step sequenced workflow, mandatory validation checkpoints, a dependency-consistency feedback loop, and clean one-level-deep progressive disclosure into real reference files. Remaining gaps: duplicated rules across Steps, output sections, and Hard Rules; no worked example of the final deliverable; and two orphaned reference files that the body never links. These keep it just below the top anchors on conciseness, actionability, and progressive disclosure.

Suggestions

Link references/figure-deliverable-plan.md from Section E and references/validation-evidence-hierarchy.md from Section F so all eight bundle files are reachable and their sections have declared supporting material.

Deduplicate the repeated rules — state the never-fabricate-references policy once in Step 4.5, the minimal-executable-subset rule once in Section G, and the self-critical-review requirement once in Section J, then drop the redundant Hard Rules 13/15/16 or reduce them to one-line pointers.

Add a short skeletal example of the final output (one disease pair, a filled-in A–J skeleton or a single example step with all 8 fields) so the mandatory structure is unambiguous without opening every reference file.

DimensionReasoningScore

Conciseness

The body is directive and dense — tables for pattern/config selection, no explanations of concepts Claude already knows — but carries notable redundancy: the never-fabricate-references rule appears in Step 4.5, Section I, and Hard Rule 15; Hard Rules 13 and 16 restate Section G and Section J; and the Step 3 config table overlaps the workload-configurations reference. This falls between the 3 anchor (some unnecessary explanation) and the 5 anchor (every token earns its place), so it scores 4.

4 / 5

Actionability

For an instruction-only skill the guidance is unusually concrete: exact output sections A–J, exact endpoint formulas ('same-direction DEG overlap ∩ PPI hubs ∩ dual-disease ROC support'), explicit method routing ('Count data → DESeq2 (recommended)' / 'Non-count data → limma'), and a ready-to-use out-of-scope redirect script. It is not 5 because there is no worked example (even skeletal) of a final plan, and steps like 'include all 8 fields' defer entirely to reference files without any inline enumeration.

4 / 5

Workflow Clarity

'Execution — 7 Steps (always run in order)' provides a clear sequence with an explicit validation checkpoint and feedback loop — Step 5 'Dependency Consistency Check (mandatory before output)' with 'If any dependency inconsistency is found, revise the plan before outputting' — plus a 16-item Hard Rules checklist and explicit failure handling for literature retrieval ('If browsing/search is unavailable, say so explicitly and output a search strategy + target evidence map instead of fake references'). This matches the 5 anchor: clear sequence, explicit validation, error-recovery loops, and a final checklist.

5 / 5

Progressive Disclosure

Six one-level-deep reference files are clearly signaled with descriptive link lines ('→ Detailed pattern logic: [references/study-patterns.md]') and spot-checks confirm they contain substantive content, giving a good overview-to-detail split. It is not 5 because two bundle files — references/figure-deliverable-plan.md and references/validation-evidence-hierarchy.md — are never referenced from the body, leaving Section E (Figure and Deliverable Plan) and Section F (Validation and Robustness) without their supporting material and leaving those files undiscoverable.

4 / 5

Total

17

/

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.

A highly specific, complete description with an explicit third-person 'what' and a well-formed 'Always use this skill whenever...' trigger clause and strong niche boundary marking. Its only weakness is trigger-term synonym coverage: the abbreviations and dataset names real users say (DEGs, GEO, comorbidity) appear in the body's Sample Triggers but not in the description itself. The leading space before the description value is a minor formatting blemish.

Suggestions

Add the natural user phrasings from the Sample Triggers section — e.g. 'DEGs', 'GEO datasets', 'comorbidity biomarker paper' — to the description so its trigger terms cover the synonyms users actually type.

Remove the stray leading space in the frontmatter description value ('description: Generates ...').

DimensionReasoningScore

Specificity

The description enumerates many concrete actions and outputs: 'per-disease differential expression, shared-signal intersection or concordance, PPI-based hub-gene prioritization, diagnostic evaluation across both diseases, immune infiltration context' plus 'four workload configs (Lite / Standard / Advanced / Publication+) with recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path'. Coverage of what the skill does is essentially complete, matching the 5 anchor rather than the 4 anchor.

5 / 5

Completeness

Both parts are explicit: the 'what' ('Generates complete dual-disease shared-transcriptome biomarker and hub-gene research designs ... always outputs four workload configs ...') and a fully explicit 'when' clause ('Always use this skill whenever a user wants to design, plan, or build a non-oncology two-disease transcriptome study ...'). This matches the 5 anchor exactly; the when-clause is not merely present but concrete.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('design, plan, or build a ... transcriptome study', 'disease pair', 'shared biomarker', 'hub-gene', 'immune infiltration', 'validation'), but common variations the skill's own Sample Triggers show users actually use — 'DEGs/DEG analysis', 'GEO', 'comorbidity paper' — are absent from the description. This sits between the 3 anchor (missing common variations) and the 5 anchor (comprehensive synonyms), so it scores 4.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche with explicit boundary markers ('non-oncology', 'two-disease', 'transcriptome', 'shared-biomarker'), so it is clearly distinguishable from generic bioinformatics or single-disease skills and unlikely to trigger for the wrong skill, matching the 5 anchor.

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/dual-disease-shared-transcriptome-biomarker-research-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.