CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

process-related-diagnostic-biomarker-nomogram-research-planner

Generates complete process-related diagnostic biomarker bioinformatics research designs from a user-provided disease context, gene-family or pathway theme, and validation direction. Use when a study centers on process-related genes, DEG and WGCNA integration, machine-learning feature selection, nomogram-based diagnostic modeling, immune infiltration, regulatory-network analysis, and optional external or experimental validation. Covers five study patterns (process-DEG discovery, co-expression-module integration, machine-learning biomarker selection, diagnostic model/nomogram workflow, immune-regulatory interpretation and validation) and always outputs Lite / Standard / Advanced / Publication+ with a recommended primary plan, stepwise workflow, figure plan, validation hierarchy, minimal executable version, publication upgrade path, and strictly verified literature retrieval.

Quality

85%

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

77%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 delivers an exceptionally well-sequenced, validation-heavy planning workflow with excellent progressive disclosure into a verified, one-level-deep reference bundle. Its main weakness is token efficiency: the 23-item Hard Rules section and repeated disclaimer text duplicate mandates already stated in the execution steps and output sections, inflating the skill's size without adding instruction.

Suggestions

Consolidate the Hard Rules: rules 2–4, 12–13, 15–17, and 21–23 duplicate the Step 3/4, Step 4.5, Section D, Section G, Section I, and Section J requirements nearly verbatim — either delete the duplicates or compress them into a short cross-reference table (rule → section) to cut ~25% of the body without losing any instruction.

State the Dataset Disclaimer text once (e.g., in workflow-step-template.md, where it already exists) and reference it from the body and Hard Rule 22 rather than repeating the full verbatim block in multiple places.

Add a compact worked example (e.g., one filled 8-field workflow step and one filled Section J element from a sample disease/process-gene case) to close the actionability gap and make the required output format copy-paste concrete.

DimensionReasoningScore

Conciseness

The body is dense and mostly efficient — it never explains concepts Claude already knows (no WGCNA/limma tutorials) — but it is padded by systematic duplication: Hard Rules 2–4, 12–13, 15–17, and 21–23 restate the Step 3/4, Step 4.5, Section G, Section D, Section I, and Section J mandates almost verbatim, and the Dataset Disclaimer text appears in full both in the body and in reference files. A meaningful fraction of the Hard Rules section could be trimmed with no loss of instruction, matching the "mostly efficient but could be tightened" anchor rather than the noticeably-padded level 2, since every duplication is at least procedural rather than concept explanation.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: pattern-selection and config tables, a data-type-driven DESeq2/limma decision rule, minimum retrieval counts ("2–4 disease/process biology background references"), explicit dependency formulas, and a fully specified 6-element self-critical review. It sits at 4 rather than 5 because there is no worked example of a (even partially) filled-out plan section, which would make the required output format unambiguous rather than derivable.

4 / 5

Workflow Clarity

The 7 steps are always run in order, with an explicit pre-output validation checkpoint (Step 5: "If any dependency inconsistency is found, revise the plan before outputting"), a verbatim out-of-scope redirect script with a stop condition, an unavailable-search fallback (output a search strategy instead of fake references), and mandatory checklists (dependency checks, Section J risk review). This matches the top anchor: clear sequence, explicit validation steps, and error-recovery feedback loops.

5 / 5

Progressive Disclosure

The body is a navigable overview that points to eight well-signaled, one-level-deep references ("→ Detailed pattern logic: references/study-patterns.md" etc.) at exactly the point each is needed. Verified against the bundle: all eight referenced files exist, each is leaf content with no nested references, and there are no orphan files in references/. This matches the top anchor for structure and navigation.

5 / 5

Total

17

/

20

Passed

Description

88%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: it clearly and explicitly states both what the skill produces and when to use it, with concrete, third-person action language and domain-natural trigger terms. The only weaknesses are a few missing common trigger variations (ROC, LASSO, GEO/transcriptome) and minor overlap potential with closely related sibling planner skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions and outputs — "Generates complete process-related diagnostic biomarker bioinformatics research designs from a user-provided disease context, gene-family or pathway theme, and validation direction" plus "a recommended primary plan, stepwise workflow, figure plan, validation hierarchy, minimal executable version, publication upgrade path, and strictly verified literature retrieval" — in comprehensive, third-person form. It matches the top anchor (comprehensive coverage) rather than 4, since the action and output coverage has no meaningful gaps.

5 / 5

Completeness

It explicitly answers both questions: the "what" is concrete ("Generates complete... research designs from a user-provided disease context, gene-family or pathway theme, and validation direction") and the "when" is an explicit trigger clause ("Use when a study centers on process-related genes, DEG and WGCNA integration..."). This matches the 5 anchor exactly; it is above 4 because the when-clause is explicit rather than implied.

5 / 5

Trigger Term Quality

Good coverage of natural domain terms users would say: "DEG and WGCNA integration", "machine-learning feature selection", "nomogram-based diagnostic modeling", "immune infiltration", "regulatory-network analysis", "external or experimental validation". It falls short of the 5 anchor because several common variations are missing (e.g., ROC, LASSO/random forest, transcriptome, GEO/bulk RNA-seq) that researchers naturally use when requesting this kind of study.

4 / 5

Distinctiveness Conflict Risk

The phrase "process-related diagnostic biomarker nomogram" carves out a clear niche with distinct triggers, minimizing conflict with unrelated skills. It sits at 4 rather than 5 because generic shared terms (DEG, WGCNA, machine-learning feature selection, immune infiltration) create minor overlap risk with closely related sibling research-planner skills (e.g., prognostic or disease-generic bioinformatics planners).

4 / 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

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/process-related-diagnostic-biomarker-nomogram-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.