CtrlK
BlogDocsLog inGet started
Tessl Logo

wgcna-analysis

Use when building a weighted gene co-expression network from a bulk expression matrix and a sample group file, filtering variable genes by MAD, identifying co-expression modules with WGCNA, correlating modules with traits, and exporting module-level plots and gene tables. NOT for single-cell RNA-seq, differential expression testing, methylation analysis, or datasets that are too small for WGCNA after quality control.

72

Quality

91%

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

88%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 skill body with excellent executable detail, a validated workflow, and a clean reference routing table. The main defects are broken bundle references (a missing diagnosis-report.md and an entire missing tests/ directory the smoke test depends on) and a small amount of author-facing padding (implementation checklist, duplicated command, version stamp).

Suggestions

Ship the referenced test artifacts (tests/data/expression.csv, tests/data/group.csv, tests/validate_outputs.R) or remove the Testing section's smoke-test command, since the documented validation workflow cannot be executed as bundled.

Delete the "Need conversion audit details" row pointing to references/diagnosis-report.md (file does not exist) — it is author-facing conversion-audit material, not agent guidance.

Trim the Implementation Checklist section and the redundant full-flag smoke-test command (or shorten it to a one-line reference to the Usage block) to recover tokens without losing guidance.

DimensionReasoningScore

Conciseness

The body is dominated by dense, functional tables (arguments, outputs, errors) with no library tutorials or explanations of concepts Claude already knows. Minor trimmable material remains: the author-facing "Implementation Checklist", a smoke-test command that largely duplicates the Usage command, and a version/date stamp line — inefficiencies that could be cut but do not amount to the unnecessary explanation of the score-3 anchor.

4 / 5

Actionability

Fully executable guidance throughout: a complete Rscript invocation with every CLI flag, an argument table with types and defaults, concrete CSV snippets for both required inputs, an exact output-file manifest, and runnable smoke-test/validation commands. Copy-paste ready and covering the common case, matching the score-5 anchor.

5 / 5

Workflow Clarity

Five clearly sequenced workflow steps with validation at both ends (sample-ID consistency checks in Step 1; validate_outputs.R, expected-output checks, and a reproducibility note at the end) and an explicit error-recovery feedback loop: an error-code table with causes and solutions, plus "IF error persists, READ: references/troubleshooting.md". This matches the explicit-validation-and-feedback-loop anchor.

5 / 5

Progressive Disclosure

Good structure: a situation-based "When to Read External Files" routing table, one-level-deep references (verified: no nested references inside the reference files), and appropriate placement of algorithm/CLI detail in references/. However, two of the six routed paths are dead in the actual bundle — references/diagnosis-report.md does not exist, and the Testing section depends on tests/data/ and tests/validate_outputs.R which are absent — so the organization gaps go slightly beyond minor, keeping this below score 5 while remaining clearly above the midpoint.

4 / 5

Total

18

/

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 strong description that explicitly states both capability and trigger conditions with an unusually useful NOT-for boundary list. The only gap is a handful of missing natural synonyms (e.g., RNA-seq, transcriptomics) that users might use when requesting this analysis.

DimensionReasoningScore

Specificity

The description lists five concrete, comprehensive actions in third-person gerund form: "building a weighted gene co-expression network", "filtering variable genes by MAD", "identifying co-expression modules with WGCNA", "correlating modules with traits", and "exporting module-level plots and gene tables". Coverage spans the full workflow with no generic filler, matching the comprehensive multiple-specific-actions anchor rather than the score-4 anchor's 'minor gaps in coverage'.

5 / 5

Completeness

Both what and when are explicitly answered: the "what" is the five concrete actions, and the "when" is an explicit "Use when building a weighted gene co-expression network from a bulk expression matrix and a sample group file" clause, reinforced by a concrete NOT-for list (single-cell RNA-seq, differential expression, methylation, too-small datasets). This matches the score-5 anchor with concrete trigger phrases, clearly above score 4's 'when could be more explicit'.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "WGCNA", "weighted gene co-expression network", "bulk expression matrix", "co-expression modules", and "module" correlations are phrases users would actually say. A few natural terms are missing (e.g., "RNA-seq" as a positive trigger, "transcriptomics", "eigengene"), which matches the good-coverage-with-gaps anchor rather than the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

WGCNA is a clear niche with distinct triggers, and the explicit exclusions ("NOT for single-cell RNA-seq, differential expression testing, methylation analysis") actively prevent wrong-skill triggering against neighboring bioinformatics skills. Minimal conflict risk, matching the clear-niche anchor.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
aipoch/medical-research-skills
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.