name: kdense-pathway-enrichment description: "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\"." metadata: version: "1.0.1"

<!-- Generated by scripts/generate_wrappers.py; do not edit. -->

Kdense Pathway Enrichment

Use this Codex adapter for the pinned upstream scientific skill.

Catalog status

• Status: inactive
• Source: kdense
• Audit reasons: executable-content
• Upstream license: MIT
• Inventory: ../../inventory.json
• Upstream instructions: ../../../vendor/scientific-agent-skills/skills/pathway-enrichment/SKILL.md

Procedure

1. Resolve the plugin root as three directories above this skill directory.
2. Run "<plugin-root>/scripts/python_runtime.sh" "<plugin-root>/scripts/search_skills.py" --name kdense-pathway-enrichment and verify the record's status, reasons, and source path and the source's pinned commit (empty for first-party cx skills) from its output instead of reading inventory.json.
3. Do not read the upstream instructions until the user has seen every audit reason and given explicit acknowledgement. Acknowledgement permits instruction inspection only.
4. Treat upstream frontmatter as source metadata, not as Codex configuration. Follow the instruction body only where it is compatible with available Codex tools and the current user-approved plan.
5. Treat tools named for another agent runtime as capability requests. Map them to an available Codex tool only when the behavior is equivalent; otherwise report the unavailable capability.
6. Ask before credentials, package installation, new network hosts, remote compute, writes, paid services, destructive actions, or imported executable code.
7. Use $science-provenance for produced scientific outputs and $science-review before presenting scientific claims.

Boundaries

• This wrapper does not grant credentials, network access, package installation, or script execution.
• Do not change an inactive record to active from inside a research task.
• Preserve failures, uncertainty, source identifiers, and licensing constraints.