CtrlK
BlogDocsLog inGet started
Tessl Logo

pathway-enrichment

Run pathway and gene-set enrichment analysis on gene lists or ranked gene data, then interpret the results. Use whenever the user has a set of genes (differentially expressed genes from PyDESeq2/Scanpy, CRISPR-screen hits, cluster marker genes, proteomics hits) and wants to know which biological pathways, GO terms, or gene sets are over-represented or enriched. Covers over-representation analysis (ORA / Enrichr / Fisher / hypergeometric), ranked Gene Set Enrichment Analysis (GSEA / preranked), single-sample scoring (ssGSEA/GSVA), and functional profiling via gseapy, g:Profiler, Enrichr libraries, MSigDB, GO, KEGG, Reactome, and WikiPathways — plus gene-ID mapping, choosing the right background universe, multiple-testing correction, redundancy reduction, dotplots/enrichment maps, and publication-ready tables. Use this for "pathway analysis", "enrichment analysis", "GO enrichment", "KEGG/Reactome pathways", "GSEA", "over-representation", "functional annotation", or "what pathways are my genes in".

74

Quality

93%

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

The canonical home for this skill is pathway-enrichment in K-Dense-AI/scientific-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 strong, well-architected skill body: fully executable examples with correct column names and library names, a clearly sequenced 8-step workflow with real checkpoints, and exemplary progressive disclosure into three real, accurately-described reference files plus a working helper script. The gaps are minor: method-choice guidance is repeated across three sections, the citation block is long, and error-recovery guidance lives in a pitfalls list rather than as an in-workflow feedback loop.

Suggestions

State the ORA-vs-GSEA decision rule once (e.g., in 'Choosing the Right Method') and have the Overview and Common Pitfalls reference it instead of restating it, trimming 3-5 lines of repetition.

Add an explicit recovery checkpoint in the Core Workflow (e.g., 'if nothing is significant: verify ID mapping succeeded and check the background universe' with a concrete check such as counting matched genes), turning the scattered pitfalls into a feedback loop.

Condense the 'Citing' section to the citation plus a one-line version/fetch instruction — the current 15 lines spend body budget on an ancillary concern.

DimensionReasoningScore

Conciseness

The body is dense, expert-assuming, and mostly earns its tokens — it never explains what GSEA or Fisher's test is at textbook length, and comments carry real judgment ("seed = reproducible p-values", "more stable than ranking by log2FoldChange"). It is not 5: the ORA-vs-GSEA choice is stated three times (Overview bullet, the table's closing rule "a thresholded list → ORA; a ranked table → GSEA", and Pitfall #3), and the 15-line 'Citing' section plus the Setup/library-verification snippet are trimmable. It is clearly above 3: there is no padded conceptual explanation of things Claude already knows.

4 / 5

Actionability

Both Quick Start examples are fully executable copy-paste code with real gseapy calls, real result columns ("Adjusted P-value", "FDR q-val", "Lead_genes"), and real library names; the Helper Script section gives three concrete CLI invocations, and Setup gives the exact install command plus a runnable library-name check. This matches anchor 5's 'fully executable; copy-paste ready code or commands; specific examples cover the common cases' — it even covers the fallback rank construction 'sign(log2FoldChange) * -log10(pvalue)'. Not 4: there is no missing key detail in the main paths.

5 / 5

Workflow Clarity

The 8-step Core Workflow is clearly sequenced with explicit checkpoints (Step 2 flags 'A silent ID mismatch is the #1 cause of nothing is significant', Step 6 mandates adjusted p-values plus an overlap-count sanity check, and Setup verifies library names before use), matching anchor 4's 'clear sequence with most checkpoints present; minor validation gaps'. It is not 5: there is no explicit validate→fix→retry feedback loop (e.g., what to check and re-run when results come back empty) — recovery guidance is scattered across Common Pitfalls rather than wired into the workflow — and it is not 3 because checkpoints are explicit, not merely implied.

4 / 5

Progressive Disclosure

The body is a genuine overview: decision table, quick starts, an 8-step workflow, pitfalls, and a script — with depth correctly pushed to three one-level-deep reference files, each verified to exist and each introduced with an accurate content summary in the 'Reference Files' section. This matches anchor 5's 'clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'; no reference chains into further nested references and no API-reference wall is inlined.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete third-person capability list, an explicit and well-scoped 'Use whenever' trigger clause with concrete input provenance examples, comprehensive natural-language trigger terms including a colloquial phrasing, and a distinct niche. The only minor criticism is length and slight redundancy between the 'Use whenever…' clause and the trailing 'Use this for…' clause, but every token is informative rather than padded, so no dimension drops below its top anchor.

DimensionReasoningScore

Specificity

The description lists many concrete actions — "Run pathway and gene-set enrichment analysis", "over-representation analysis (ORA / Enrichr / Fisher / hypergeometric)", "ranked Gene Set Enrichment Analysis (GSEA / preranked)", "single-sample scoring (ssGSEA/GSVA)", "gene-ID mapping", "multiple-testing correction", "redundancy reduction", "dotplots/enrichment maps", and "publication-ready tables" — which exceeds anchor 4's 'several specific actions; minor gaps' and matches anchor 5's comprehensive coverage. It does not fall below 5: there is no vague filler, and the named tools (gseapy, g:Profiler, Enrichr, MSigDB, GO, KEGG, Reactome, WikiPathways) make every claimed capability concrete.

5 / 5

Completeness

It explicitly answers both questions: the first sentence gives the "what" ("Run pathway and gene-set enrichment analysis on gene lists or ranked gene data, then interpret the results") and the second gives an explicit "when" ("Use whenever the user has a set of genes (differentially expressed genes from PyDESeq2/Scanpy, CRISPR-screen hits, cluster marker genes, proteomics hits) and wants to know which biological pathways… are over-represented or enriched"), reinforced by concrete trigger phrases — the exact shape of anchor 5. Not 4: the 'when' clause is fully explicit, not merely present-but-could-be-more-specific.

5 / 5

Trigger Term Quality

The closing clause provides comprehensive natural trigger terms including synonyms: "pathway analysis", "enrichment analysis", "GO enrichment", "KEGG/Reactome pathways", "GSEA", "over-representation", "functional annotation", and the colloquial user phrasing "what pathways are my genes in". This matches anchor 5's 'comprehensive coverage of natural terms including synonyms'; anchor 4 ('a few natural terms missing') would apply only if common variations were absent, which they are not.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (pathway/gene-set enrichment on gene lists) with distinct triggers like "GSEA", "over-representation", and "what pathways are my genes in" that no adjacent bioinformatics skill (ID lookup, DE analysis, visualization) would claim, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'. It is not 4: the triggers are specific to enrichment analysis rather than merely 'mostly distinct' — the DE/CRISPR/marker-gene provenance examples narrow it further without creating overlap.

5 / 5

Total

20

/

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
synthetic-sciences/openscience
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.