Agent skill

Kegg Pathway Analysis

by jaechang-hits in jaechang-hits/SciAgent-Skills

Guide to KEGG pathway enrichment for DEG results. An agent skill from jaechang-hits/SciAgent-Skills.

CC-BY-4.0Auto-check passedResearch & Science

Install Kegg Pathway Analysis

skills CLI
$ npx skills add jaechang-hits/SciAgent-Skills --skill kegg-pathway-analysis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jaechang-hits/SciAgent-Skills kegg-pathway-analysis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jaechang-hits/SciAgent-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/systems-biology-multiomics/kegg-pathway-analysis .claude/skills/kegg-pathway-analysis && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
kegg-pathway-analysis
GitHub stars
374
Used in
1 other repo
Token cost
~4.8k tokens
SKILL.md length
1,663 words
Files
1
Skills in repo
169
Repo updated
First seen
Licence
CC-BY-4.0

At a glance

Guide to KEGG pathway enrichment for DEG results. An agent skill from jaechang-hits/SciAgent-Skills.

  • Works in 7 steps: Always split ORA by gene direction. Run… → Specify the background universe… → Pre-fetch and cache KEGG data before… → …
  • Research & Science work in your project
  • SKILL.md covers Overview, Key Concepts, Pre-flight Interview and Decision Framework, plus 5 more sections
  • Reaches rest.kegg.jp

What it does

Kegg Pathway Analysis is an agent skill from jaechang-hits/SciAgent-Skills. Guide to KEGG pathway enrichment for DEG results. Covers ORA vs GSEA, mandatory directionality splitting, KEGG organism codes, API failure handling with offline fallbacks, cross-condition comparisons, and answer-first reporting. Consult when running enrichment with clusterProfiler or gseapy.

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science. The repository describes itself as: 197 bioinformatics & life science skills for Claude Code and AI agents — BixBench 92.0% accuracy. RNA-seq, single-cell, drug discovery, proteomics, and more. Powers OmicsHorizon. The licence is CC-BY-4.0.

When your agent uses it

  • Research & Science work in your project

Example prompts

  • “/kegg-pathway-analysis”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Always split ORA by gene direction. Run enrichKEGG() or gp.enrichr() separately for up-regulated and down-regulated genes. Combining them…
  2. Specify the background universe explicitly. Set the universe to all tested genes (the full set from your differential expression…
  3. Pre-fetch and cache KEGG data before running enrichment. Download pathway-gene mappings at the start of the analysis and save them…
  4. Report the numeric answer before resolving pathway names. Once you have computed the count or list of significant pathway IDs, emit that…
  5. Apply multiple testing correction consistently. Use adjusted p-values (p.adjust < 0.05, typically BH method) rather than raw p-values…
  6. Verify gene ID format matches the organism. Eukaryotic KEGG pathways expect Entrez gene IDs; bacterial species expect locus tags. A…
  7. Use gseapy as a fallback when clusterProfiler fails. When enrichKEGG() fails due to KEGG API issues, gseapy's enrichr() function with…

What it can do on your machine

Read from SKILL.md and the folder at commit 82c862c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are r, python and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • rest.kegg.jp

    Also links to:

    • kegg.jp
    • doi.org
    • gseapy.readthedocs.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kegg Pathway Analysis loads about 4.8k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 1,663 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jaechang-hits/SciAgent-Skills at commit 82c862c, republished under its CC-BY-4.0 licence (© jaechang-hits). 1,663 words, ~4,842 tokens.

Download SKILL.mdSave it as .claude/skills/kegg-pathway-analysis/SKILL.md (or your agent's skills folder).
name
kegg-pathway-analysis
description
Guide to KEGG pathway enrichment for DEG results. Covers ORA vs GSEA, mandatory directionality splitting, KEGG organism codes, API failure handling with offline fallbacks, cross-condition comparisons, and answer-first reporting. Consult when running enrichment with clusterProfiler or gseapy.
license
CC-BY-4.0

KEGG Pathway Enrichment Analysis Guide

Overview

KEGG (Kyoto Encyclopedia of Genes and Genomes) pathway enrichment analysis identifies biological pathways that are statistically over-represented among differentially expressed genes. This guide covers the two main enrichment approaches (ORA and GSEA), critical workflow decisions such as splitting genes by directionality, tool selection between R clusterProfiler and Python gseapy, and strategies for handling the notoriously unreliable KEGG REST API. It addresses recurring failure modes that produce incorrect pathway counts or stalled analyses.

The three most common errors in KEGG pathway analysis are: (1) combining up-regulated and down-regulated genes into a single enrichment run, which masks true pathway signals; (2) analysis failures caused by KEGG REST API timeouts with no fallback strategy; and (3) delaying result reporting while attempting cosmetic pathway name lookups that may never complete. This guide provides concrete solutions for each.

Key Concepts

ORA vs GSEA

Over-Representation Analysis (ORA) and Gene Set Enrichment Analysis (GSEA) are the two primary methods for pathway enrichment, and they differ in both input and statistical approach.

ORA takes a pre-filtered gene list (e.g., genes with padj < 0.05 and |log2FC| > 1.5) and tests whether KEGG pathway members are over-represented in that list relative to a background universe. ORA uses a hypergeometric test (Fisher's exact test). It is straightforward but discards magnitude information and depends heavily on the significance cutoff chosen.

GSEA takes a ranked list of all genes (typically ranked by log2 fold change or a signed significance statistic) without any cutoff. It computes a running enrichment score by walking down the ranked list and identifies pathways whose members cluster toward the top or bottom of the ranking. GSEA captures subtle coordinated changes that ORA may miss.

In practice, ORA via enrichKEGG() (clusterProfiler) or gp.enrichr() (gseapy) is the more common starting point. GSEA via gseKEGG() or gp.prerank() is preferred when you want to avoid arbitrary cutoffs or when effect sizes are small.

Directionality in Enrichment

When performing ORA, gene directionality -- whether a gene is up-regulated or down-regulated -- is critical. A single pathway can contain genes regulated in opposite directions. If up-regulated and down-regulated genes are combined into one list, their opposing signals cancel out, diluting the enrichment signal and masking genuinely enriched pathways. Running enrichment separately for up-regulated and down-regulated gene sets produces more accurate and interpretable results. This splitting is mandatory for ORA. GSEA inherently handles directionality through the signed ranking, though interpreting leading-edge genes by direction is still important.

KEGG Organism Codes

KEGG uses three-letter (or four-letter) organism codes to identify species-specific pathway databases. Using the wrong code silently returns empty results. Common codes:

OrganismCode
Humanhsa
Mousemmu
Ratrno
Zebrafishdre
Drosophiladme
C. eleganscel
E. coli K-12eco
P. aeruginosa PA14pau
P. aeruginosa PAO1pae
S. cerevisiaesce
A. thalianaath

Gene ID format also varies by organism: eukaryotic species typically require Entrez gene IDs, while bacterial species use locus tags. Mismatched ID types are a silent failure mode.

KEGG API Reliability

The KEGG REST API (rest.kegg.jp) is rate-limited, frequently slow, and prone to timeouts. Both clusterProfiler::enrichKEGG() and direct HTTP requests to KEGG can fail unpredictably. Planning for API failures is not optional -- it is a necessary part of any KEGG-based workflow. Strategies include pre-fetching and caching pathway data, using offline gene set databases bundled with gseapy, and implementing retry logic with timeouts.

Pre-flight Interview

Settle these with the user before writing any analysis code.

yaml
decisions:
  - id: D1
    param: organismCode
    kind: required
    source: upstream
    ask: "Which species should pathways be looked up for?"
    default: "carried from the dataset"

  - id: D2
    param: identifierMapping
    kind: required
    source: data
    depends_on: [D1]
    ask: "Which identifier type do the genes carry, and how should unmapped ones be handled?"
    default: null

  - id: D3
    param: testingApproach
    kind: required
    source: upstream
    ask: "Test a significant-gene list against pathways (over-representation), or the whole ranked list without a cut (enrichment)?"
    default: "over-representation when the input is a gene list"

  - id: D4
    param: backgroundSet
    kind: required
    source: upstream
    depends_on: [D3]
    ask: "Which genes form the background - everything measured in this experiment, or the whole annotated genome?"
    default: "the genes tested in this experiment"
    skip_if: "ranked-list enrichment, which uses the ranking rather than a background"

  - id: D5
    param: pathwayScope
    kind: optional
    source: user
    ask: "Should all pathway categories be tested, or only metabolism, signalling, or disease maps?"
    default: "all categories"

  - id: D6
    param: significanceThreshold
    kind: required
    source: user
    ask: "How strong must a pathway's evidence be, after correcting for the number of pathways tested?"
    default: "adjusted p-value 0.05"

D4 is the decision most often skipped and the one that most changes the answer. Using the whole genome as background when the experiment only measured expressed genes makes every tissue-specific pathway look enriched - the enrichment is against genes that were never measurable, not against the experiment.

Decision Framework

Question: What enrichment analysis do you need?
|
+-- Have a pre-filtered DEG list (with cutoffs applied)?
|   +-- Yes --> ORA
|   |   +-- Using R? --> clusterProfiler::enrichKEGG()
|   |   +-- Using Python? --> gseapy.enrichr()
|   |   +-- KEGG API failing? --> gseapy with offline gene sets
|   +-- No, want cutoff-free analysis --> GSEA
|       +-- Using R? --> clusterProfiler::gseKEGG()
|       +-- Using Python? --> gseapy.prerank()
|
+-- Need to split by direction?
|   +-- ORA --> YES, always split up/down (mandatory)
|   +-- GSEA --> No split needed (direction encoded in ranking)
|
+-- KEGG API unreliable?
    +-- Try cached/pre-fetched data first
    +-- Fall back to gseapy offline databases
    +-- Use retry logic with short timeouts
ScenarioRecommended ApproachRationale
Standard ORA with RclusterProfiler::enrichKEGG(), split by directionMost widely used, integrates with Bioconductor ecosystem
Standard ORA with Pythongseapy.enrichr() with KEGG_2021_HumanOffline gene sets avoid API dependency
Cutoff-free enrichmentGSEA via gseKEGG() or gp.prerank()Captures subtle coordinated changes, no arbitrary threshold
KEGG API is downSwitch to gseapy offline databasesgseapy bundles KEGG gene sets locally
Comparing conditionsRun separate up/down enrichment per conditionEnables direction-aware set operations across conditions
Non-model organismVerify organism code, use KEGGREST to check availabilityWrong code silently returns empty results

Best Practices

  1. Always split ORA by gene direction. Run enrichKEGG() or gp.enrichr() separately for up-regulated and down-regulated genes. Combining them inflates the gene list, dilutes enrichment signal, and produces incorrect pathway counts. Report the union of significant pathways from both directions.

  2. Specify the background universe explicitly. Set the universe to all tested genes (the full set from your differential expression analysis), not just the significant ones. Omitting the universe defaults to all genes in the KEGG database, which inflates significance for well-studied pathways.

  3. Pre-fetch and cache KEGG data before running enrichment. Download pathway-gene mappings at the start of the analysis and save them locally. This avoids mid-analysis failures when the KEGG API becomes unresponsive and makes the analysis reproducible.

  4. Report the numeric answer before resolving pathway names. Once you have computed the count or list of significant pathway IDs, emit that result immediately. Resolving IDs to human-readable names via additional KEGG API calls is cosmetic and can timeout, losing the primary result.

  5. Apply multiple testing correction consistently. Use adjusted p-values (p.adjust < 0.05, typically BH method) rather than raw p-values. Both clusterProfiler and gseapy apply correction by default, but always verify the cutoff is on the adjusted value.

  6. Verify gene ID format matches the organism. Eukaryotic KEGG pathways expect Entrez gene IDs; bacterial species expect locus tags. A mismatch silently returns zero enriched pathways. Use bitr() in clusterProfiler or equivalent ID conversion if your input uses gene symbols.

  7. Use gseapy as a fallback when clusterProfiler fails. When enrichKEGG() fails due to KEGG API issues, gseapy's enrichr() function with bundled offline gene sets (e.g., KEGG_2021_Human) provides equivalent ORA results without any network dependency.

Show full SKILL.md (995 more words)Show less

Common Pitfalls

  1. Combining up-regulated and down-regulated genes into a single enrichment run. Pathways with genes regulated in opposite directions cancel out, producing fewer significant pathways than the true count. Results from combined lists are unreliable. Example of the anti-pattern:

    r
    # WRONG: combining up and down genes into one list
    all_sig_genes <- rownames(subset(res, padj < 0.05 & abs(log2FoldChange) > 1.5))
    ekegg <- enrichKEGG(gene = all_sig_genes, ...)  # Will miss pathways
    • How to avoid: Always split DEGs by direction before ORA. Run enrichment twice (once for up, once for down) and take the union of significant pathways.
  2. Using the wrong KEGG organism code. KEGG silently returns empty results for invalid or mismatched organism codes. This is especially common for bacterial species with multiple strain-specific codes (e.g., pae for PAO1 vs pau for PA14).

    • How to avoid: Confirm the organism code from the KEGG organism list before running enrichment. For bacteria, verify the specific strain code.
  3. Gene ID type mismatch. Providing gene symbols when KEGG expects Entrez IDs (or locus tags for bacteria) silently yields zero enriched pathways with no error message.

    • How to avoid: Check the expected ID type for your organism. Use clusterProfiler::bitr() or equivalent to convert gene symbols to Entrez IDs before enrichment.
  4. Not handling KEGG API timeouts. The KEGG REST API frequently times out, causing enrichKEGG() to fail mid-analysis. Without error handling, the entire analysis is lost.

    • How to avoid: Wrap KEGG API calls in retry logic with short timeouts (30 seconds). Pre-fetch pathway data at the start. Have gseapy as a fallback.
  5. Delaying the answer to resolve pathway names. Calling keggGet() to convert pathway IDs to human-readable names after computing results can timeout, losing the numeric answer entirely. Example of the anti-pattern:

    r
    # BAD: answer delayed by name lookup that may hang
    result_ids <- setdiff(pathways_condA, pathways_condB)
    names <- keggGet(result_ids)  # Can timeout -- answer never emitted
    count <- length(result_ids)
    • How to avoid: Report pathway IDs and counts immediately. Resolve names only after the primary result is secured, inside a tryCatch() or try/except block.
  6. Omitting the background universe. Not specifying the universe parameter defaults to the entire KEGG gene database for that organism, inflating statistical significance for pathways containing well-annotated housekeeping genes.

    • How to avoid: Always pass universe = rownames(res) (all tested genes from the DE analysis) to enrichKEGG().
  7. Using raw p-values instead of adjusted p-values for filtering. Reporting pathways with p < 0.05 without multiple testing correction dramatically increases false positives.

    • How to avoid: Always filter on p.adjust < 0.05. Verify that the column you are filtering is the adjusted value, not the raw p-value.

Workflow

  1. Step 1: Prepare gene lists

    • Filter significant DEGs from differential expression results (e.g., padj < 0.05, |log2FC| > 1.5)
    • Split into up-regulated and down-regulated gene sets
    • Convert gene IDs to the format expected by KEGG (Entrez IDs or locus tags)
    r
    library(clusterProfiler)
    
    # Filter significant DEGs
    sig_genes <- subset(res, padj < 0.05 & abs(log2FoldChange) > 1.5)
    
    # MANDATORY: Split by direction BEFORE running enrichment
    up_genes <- rownames(subset(sig_genes, log2FoldChange > 0))
    dn_genes <- rownames(subset(sig_genes, log2FoldChange < 0))
    
    cat("Up-regulated genes:", length(up_genes), "\n")
    cat("Down-regulated genes:", length(dn_genes), "\n")
  2. Step 2: Pre-fetch KEGG data (recommended)

    • Cache pathway-gene mappings locally before running enrichment
    • Decision point: If KEGG API is accessible, proceed with live queries. If not, switch to offline gene sets (Step 2b).

    R (KEGGREST package):

    r
    library(KEGGREST)
    pathway_list <- tryCatch(
      keggList("pathway", organism_code),
      error = function(e) NULL
    )

    Python (requests with caching):

    python
    import requests
    import json
    import os
    
    cache_file = f"kegg_{organism_code}_pathways.json"
    if os.path.exists(cache_file):
        with open(cache_file) as f:
            pathway_map = json.load(f)
    else:
        resp = requests.get(
            f"https://rest.kegg.jp/list/pathway/{organism_code}", timeout=30
        )
        if resp.ok:
            pathway_map = dict(
                line.split("\t") for line in resp.text.strip().split("\n")
            )
            with open(cache_file, 'w') as f:
                json.dump(pathway_map, f)
  3. Step 3: Run enrichment separately for each direction

    • Run ORA twice: once for up-regulated genes, once for down-regulated genes
    • Always specify the universe (all tested genes)

    R (clusterProfiler):

    r
    ekegg_up <- enrichKEGG(gene = up_genes, organism = organism_code,
                           universe = rownames(res), pvalueCutoff = 0.05)
    ekegg_dn <- enrichKEGG(gene = dn_genes, organism = organism_code,
                           universe = rownames(res), pvalueCutoff = 0.05)
    
    up_pathways <- subset(as.data.frame(ekegg_up), p.adjust < 0.05)$ID
    dn_pathways <- subset(as.data.frame(ekegg_dn), p.adjust < 0.05)$ID
    
    all_sig_pathways <- union(up_pathways, dn_pathways)
    cat("Significant pathways (up):", length(up_pathways), "\n")
    cat("Significant pathways (down):", length(dn_pathways), "\n")
    cat("Total unique significant pathways:", length(all_sig_pathways), "\n")

    Python (gseapy):

    python
    import gseapy as gp
    
    up_genes = sig_genes[sig_genes['log2FoldChange'] > 0].index.tolist()
    dn_genes = sig_genes[sig_genes['log2FoldChange'] < 0].index.tolist()
    
    enr_up = gp.enrichr(gene_list=up_genes, gene_sets='KEGG_2021_Human',
                         organism='human', outdir=None)
    enr_dn = gp.enrichr(gene_list=dn_genes, gene_sets='KEGG_2021_Human',
                         organism='human', outdir=None)
  4. Step 4: Report results immediately

    • Emit pathway IDs and counts before attempting name resolution
    • Optionally resolve pathway names in a non-blocking manner
    r
    result_ids <- setdiff(pathways_condA, pathways_condB)
    count <- length(result_ids)
    cat("Answer:", count, "pathways unique to condition A\n")
    cat("Pathway IDs:", paste(result_ids, collapse = ", "), "\n")
    
    # Optional: resolve names (non-blocking)
    names <- tryCatch(keggGet(result_ids), error = function(e) NULL)
  5. Step 5: Cross-condition comparison (if applicable)

    • Run separate up/down enrichment for each condition (4 enrichKEGG calls total)
    • Compare pathway sets within the same direction
    • Report the union of direction-specific unique pathways
    r
    # Condition A
    up_pathways_A <- subset(as.data.frame(ekegg_up_A), p.adjust < 0.05)$ID
    dn_pathways_A <- subset(as.data.frame(ekegg_dn_A), p.adjust < 0.05)$ID
    
    # Condition B
    up_pathways_B <- subset(as.data.frame(ekegg_up_B), p.adjust < 0.05)$ID
    dn_pathways_B <- subset(as.data.frame(ekegg_dn_B), p.adjust < 0.05)$ID
    
    # Find pathways unique to condition A in each direction
    unique_up <- setdiff(up_pathways_A, up_pathways_B)
    unique_dn <- setdiff(dn_pathways_A, dn_pathways_B)
    
    # Union
    unique_to_A <- union(unique_up, unique_dn)
    cat("Pathways in A but not B:", length(unique_to_A), "\n")
    cat("  From up-regulated:", length(unique_up), "-",
        paste(unique_up, collapse = ", "), "\n")
    cat("  From down-regulated:", length(unique_dn), "-",
        paste(unique_dn, collapse = ", "), "\n")
  6. Step 6: Handle API failures with retry logic

    • If KEGG API calls fail, retry with timeout before falling back to offline data
    r
    fetch_kegg_with_retry <- function(organism_code, max_retries = 3,
                                       timeout_sec = 30) {
      for (i in seq_len(max_retries)) {
        result <- tryCatch({
          R.utils::withTimeout(
            keggList("pathway", organism_code),
            timeout = timeout_sec
          )
        }, error = function(e) NULL)
        if (!is.null(result)) return(result)
        Sys.sleep(2)
      }
      warning("KEGG API unreachable after retries. Proceeding without pathway names.")
      return(NULL)
    }

Further Reading

  • gseapy-gene-enrichment -- Python-based gene set enrichment analysis; use as a fallback when clusterProfiler KEGG API calls fail, or as the primary tool for Python-based workflows
  • deseq2-differential-expression / pydeseq2-differential-expression -- Upstream differential expression analysis that produces the DEG lists used as input to KEGG pathway enrichment

© jaechang-hits, CC-BY-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/systems-biology-multiomics/kegg-pathway-analysis of jaechang-hits/SciAgent-Skills.

Open the folder on GitHubat commit 82c862c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jaechang-hits/SciAgent-Skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Kegg Pathway Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Kegg Pathway Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kegg Pathway Analysis this skilljaechang-hits/SciAgent-Skills3741 repos~4.8kAutomated safety check: PassCC-BY-4.0
Hypothesis Generationspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Content Research Writerweapp-tailwindcss/weapp-tailwindcss1.9k25 repos~3.5kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Hypothesis Generation

    spacering-net/codeg

    Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Research & ScienceAuto-check: notes
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed
  • Content Research Writer

    weapp-tailwindcss/weapp-tailwindcss

    Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.

    1.9k GitHub starsUsed in 25 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes
  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

More from jaechang-hits/SciAgent-Skills

All 169 skills in this repo
  • Neb Irc Activation Energy

    jaechang-hits/SciAgent-Skills

    NEB-IRC activation energy pipeline for reaction barriers using GFN2-xTB and pysisyphus.

    374 GitHub stars~4k tokensUpdated 12 days ago
    Auto-check passed
  • Molecular Visualization 3dmol

    jaechang-hits/SciAgent-Skills

    3Dmol.js WebGL molecular visualization emitted as self-contained HTML.

    374 GitHub stars~3.2k tokensUpdated 12 days ago
    Auto-check passed
  • Cobrapy Metabolic Modeling

    jaechang-hits/SciAgent-Skills

    Constraint-based (COBRA) analysis of genome-scale metabolic models: FBA, FVA, knockouts, flux sampling, production envelopes, gapfilling, media optimization.

    374 GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Rdkit Chemdraw Cdxml

    jaechang-hits/SciAgent-Skills

    Read, write, and edit ChemDraw CDX/CDXML files with RDKit's rdkit.Chem.rdChemDraw plus direct XML editing, always paired with a rendered PNG.

    374 GitHub stars~6.9k tokensUpdated 12 days ago
    Auto-check passed
  • Pubmed Database

    jaechang-hits/SciAgent-Skills

    Programmatic PubMed access via NCBI E-utilities REST API. An agent skill from jaechang-hits/SciAgent-Skills.

    374 GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed
  • Sciagent Skill Creator

    jaechang-hits/SciAgent-Skills

    Scaffold a new SciAgent-Skills entry. An agent skill from jaechang-hits/SciAgent-Skills.

    374 GitHub stars~2.3k tokensUpdated 12 days ago
    Auto-check passed

Questions about Kegg Pathway Analysis

What does Kegg Pathway Analysis do?

Guide to KEGG pathway enrichment for DEG results. An agent skill from jaechang-hits/SciAgent-Skills. Kegg Pathway Analysis is an agent skill from jaechang-hits/SciAgent-Skills. Guide to KEGG pathway enrichment for DEG results.

When should I use Kegg Pathway Analysis?

Kegg Pathway Analysis fits situations like: research & Science work in your project.

How do I install Kegg Pathway Analysis in Claude Code?

Run `npx skills add jaechang-hits/SciAgent-Skills --skill kegg-pathway-analysis -a claude-code`. Or copy the skill folder (skills/systems-biology-multiomics/kegg-pathway-analysis in jaechang-hits/SciAgent-Skills) into .claude/skills/kegg-pathway-analysis in your project. Claude Code loads it when a task matches its description.

How do I install Kegg Pathway Analysis in Codex?

Run `npx skills add jaechang-hits/SciAgent-Skills --skill kegg-pathway-analysis -a codex`. Or copy the skill folder (skills/systems-biology-multiomics/kegg-pathway-analysis in jaechang-hits/SciAgent-Skills) into .agents/skills/kegg-pathway-analysis in your project. Codex loads it when a task matches its description.

Can I use Kegg Pathway Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jaechang-hits/SciAgent-Skills --skill kegg-pathway-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kegg-pathway-analysis, .gemini/skills/kegg-pathway-analysis, .github/skills/kegg-pathway-analysis and .opencode/skills/kegg-pathway-analysis in your project.

What does Kegg Pathway Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: Kegg Pathway Analysis is instructions for the agent only. Our summary lists: Python 3.

Does Kegg Pathway Analysis access the network?

SKILL.md names 4 domains. In commands or code: rest.kegg.jp; the agent is likely to contact it when it follows the instructions. As links in the text: kegg.jp, doi.org and gseapy.readthedocs.io. This is read from the text; nothing was executed.

Is Kegg Pathway Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Kegg Pathway Analysis use?

Kegg Pathway Analysis is published under the CC-BY-4.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Kegg Pathway Analysis use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Kegg Pathway Analysis?

Skills that share tags, products or a category with Kegg Pathway Analysis: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kegg Pathway Analysis?

jaechang-hits (a GitHub user) maintains it in jaechang-hits/SciAgent-Skills, which has 374 GitHub stars. The repository holds 169 skills in this directory. The repository was last updated on September 29, 2026.

Source: jaechang-hits/SciAgent-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.