protein-interaction-network-analysis

mims-harvard/tooluniverse · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/mims-harvard/tooluniverse --skill protein-interaction-network-analysis
0 commentsdiscussion
summary

Comprehensive protein interaction network analysis using ToolUniverse tools. Analyzes protein networks through a 4-phase workflow: identifier mapping, network retrieval, enrichment analysis, and optional structural data.

skill.md

Protein Interaction Network Analysis

Comprehensive protein interaction network analysis using ToolUniverse tools. Analyzes protein networks through a 4-phase workflow: identifier mapping, network retrieval, enrichment analysis, and optional structural data.

Domain Reasoning: Interaction Type Clarification

When asked about protein interactions, ask: physical interaction (do they bind?) or functional interaction (do they affect the same pathway)? STRING combines both — a high combined_score does not mean physical binding. For physical binding evidence, check the experimental score (escore) specifically. A high tscore (text mining) or dscore (database) with a low escore suggests co-annotation or co-citation, not direct binding.

LOOK UP DON'T GUESS: protein interaction scores, experimental evidence types, and whether two specific proteins have known co-crystal structures. Use STRING escore and BioGRID experimental data — do not infer binding from pathway co-membership alone.

Databases Used

Database Coverage API Key Purpose
STRING 14M+ proteins, 5,000+ organisms Not required Primary interaction source
BioGRID 2.3M+ interactions, 80+ organisms Required Fallback, curated data
SASBDB 2,000+ SAXS/SANS entries Not required Solution structures

4-Phase Workflow

  1. Identifier MappingSTRING_map_identifiers(): validate protein names, get STRING IDs
  2. Network RetrievalSTRING_get_network() (primary); BioGRID_get_interactions() (fallback, requires API key)
  3. Enrichment AnalysisSTRING_functional_enrichment() for GO/KEGG/Reactome; STRING_ppi_enrichment() to test functional coherence
  4. Structural Data (optional)SASBDB_search_entries() for SAXS/SANS solution structures

See python_implementation.py for runnable examples (example_tp53_analysis(), analyze_protein_network()).

Parameters

Parameter Default Description
proteins Required Gene symbols or UniProt IDs
species 9606 NCBI taxonomy ID
confidence_score 0.7 Min interaction confidence (0–1)
include_biogrid False BioGRID fallback (requires API key)
include_structure False SASBDB structural data (slower)

Confidence Score Guidelines

Score Use Case
0.4 Exploratory analysis (default STRING threshold)
0.7 Recommended — reliable interactions
0.9 Core interactions only

Network Edge Fields (STRING)

Key fields returned per interaction edge:

  • score — combined confidence (0–1)
  • escore — experimental score (use for physical binding evidence)
  • dscore — database score
  • tscore — text mining score
  • ascore — coexpression score
  • preferredName_A, preferredName_B — gene names

Extended Analysis Tools

Signaling Pathways:

  • OmniPath_get_signaling_interactions — directed, signed PPI (stimulation/inhibition)
  • Reactome_map_uniprot_to_pathways — map proteins to Reactome pathways (param: uniprot_id)
  • ReactomeAnalysis_pathway_enrichment — pathway enrichment for gene sets

Druggability & Clinical Context:

  • DGIdb_get_drug_gene_interactions — drug interactions for hub proteins (param: genes as array)
  • DGIdb_get_gene_druggability — druggability categories
  • gnomad_get_gene_constraints — gene essentiality metrics (pLI, oe_lof)
  • civic_search_evidence_items — clinical evidence for mutations in network proteins
  • UniProt_get_function_by_accession — protein function annotation

Tool-Specific Notes

IntAct Interaction Data

interaction_ids are in the metadata field of the response, NOT at the top level:

interaction_ids = result.get("metadata", {}).get("interaction_ids", [])

BioGRID Chemical Interactions

BioGRID_get_chemical_interactions always includes a limitation note — chemical interaction coverage may be incomplete. Defaults to taxId=9606 (human) when no organism is provided.

IntAct protein_name Alias

IntAct tools accept protein_name as an alias parameter in addition to the original identifier parameter.

Domain Reasoning: Multimeric Assemblies & Binding Valency

LOOK UP DON'T GUESS: oligomeric state, subunit stoichiometry, and binding valency. Use RCSB PDB (RCSB_search_structures, RCSB_get_entry_info) or UniProt (UniProt_get_function_by_accession) to confirm whether a protein is a monomer, dimer, trimer, etc. Do not assume from gene name alone.

Calculating Multimer Valency from Binding Data

Valency = number of independent binding sites on a multimeric complex. A homodimer with one binding site per subunit has valency 2. A pentamer (e.g., IgM) with 2 Fab arms each has valency 10.

Key reasoning steps:

  1. Determine oligomeric state: Look up quaternary structure in PDB/UniProt. A "dimer" in solution may be a dimer-of-dimers (tetramer) crystallographically.
  2. Count binding sites per subunit: Each subunit contributes independently unless the binding site spans the interface (then the complex itself is the functional unit).
  3. Valency = subunits x sites_per_subunit (only if sites are independent). If binding at one site affects another, you have cooperativity, not simple valency.
  4. Avidity vs affinity: A multivalent complex binds more tightly than a single site (avidity effect). Apparent Kd_multivalent << Kd_monovalent. The enhancement depends on linker flexibility and target geometry.

Statistical Factors in Multimeric Binding

When a symmetric multimer binds a ligand, statistical factors affect the apparent rate constants:

  • First ligand binding: kon_apparent = n x kon_intrinsic (n equivalent sites available)
  • First ligand dissociation: koff_apparent = koff_intrinsic (only one ligand to dissociate)
  • General rule: For a multimer with n identical sites, binding to the i-th site has forward statistical factor (n - i + 1) and reverse statistical factor i.
  • Macroscopic vs microscopic Kd: Kd_macro(1st site) = Kd_micro / n. Kd_macro(last site) = n x Kd_micro. The ratio Kd_last / Kd_first = n^2 for non-cooperative binding.

If measured Kd values deviate from these statistical predictions, the protein shows positive cooperativity (Kd decreases more than expected) or negative cooperativity (Kd increases more than expected).

When to Use Binding Curve Analysis vs Stoichiometry

Approach Use when What it tells you
Stoichiometry (ITC, AUC, SEC-MALS) You need the number of binding partners per complex n (sites), not affinity
Binding curves (SPR, FP, ELISA) You need Kd and kinetics Affinity, but apparent Kd conflates valency and cooperativity
Hill plot (log-log binding curve) You suspect cooperativity Hill coefficient nH: nH=1 non-cooperative, nH>1 positive, nH<1 negative
Scatchard plot (bound/free vs bound) Classic approach, now less common Curved = multiple site classes or cooperativity; linear = single Kd

Obligate vs facultative multimers: An obligate dimer (e.g., many kinases) has NO monomeric activity. If your "purified protein" shows no activity, check if dimer formation is required. Use SEC or native PAGE to confirm oligomeric state. Low protein concentration, high salt, or wrong pH can dissociate obligate multimers.

Domain Reasoning: Coiled-Coil Oligomeric State Prediction

  • Heptad repeat: (abcdefg)n where positions a and d are hydrophobic core residues.
  • Oligomeric state from packing: dimer (leucine zipper, Leu at d), trimer (Ile/Val at a, Leu at d), tetramer (Leu at both a+d), pentamer (complex mixed packing, e.g., Trp or polar residues at a).
  • Heptad net diagram: map residues onto helical wheel; a+d form the hydrophobic core interface. The identity of a/d residues determines packing geometry and thus oligomeric state.
  • Polar residues at a/d (Asn, Gln) specify parallel vs antiparallel orientation and can select for specific oligomeric states.
  • LOOK UP: search PubMed for "[sequence motif] coiled coil oligomeric state" and check CC+ or SOCKET databases before predicting oligomeric state from sequence alone.

Domain Reasoning: Detergent Effects on Membrane Proteins

  • Mild detergents (DDM, LMNG, CHAPS, digitonin) preserve native oligomeric state and lipid interactions; preferred for structural studies.
  • Harsh detergents (SDS, OG at high concentration above CMC) can dissociate native complexes and strip stabilizing lipids.
  • Native MS in different detergents reveals whether specific lipids stabilize oligomeric assemblies; comparing CHAPS vs OG results distinguishes detergent-stable from lipid-dependent oligomers.

Protein Identification Questions

For "what protein does X" questions: ALWAYS search UniProt and PubMed first — do not guess from memory. Key pathways to know:

  • Amyloid clearance: collagen degradation by matrix metalloproteinases is required to expose amyloid deposits, allowing macrophage engulfment. The answer is collagen, not serum amyloid P (SAP) or other amyloid-binding proteins.
  • When a question asks "what protein", give JUST the protein name — no abbreviations, descriptions, or qualifications.

Troubleshooting

  • No interactions found: verify protein names (case-sensitive), try confidence_score=0.4
  • BioGRID not working: set BIOGRID_API_KEY in environment; STRING works without a key
  • Verbose output: filter with 2>&1 | grep -v "Error loading tools" (see KNOWN_ISSUES.md)

References

how to use protein-interaction-network-analysis

How to use protein-interaction-network-analysis on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add protein-interaction-network-analysis
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/mims-harvard/tooluniverse --skill protein-interaction-network-analysis

The skills CLI fetches protein-interaction-network-analysis from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/protein-interaction-network-analysis

Reload or restart Cursor to activate protein-interaction-network-analysis. Access the skill through slash commands (e.g., /protein-interaction-network-analysis) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.672 reviews
  • Dhruvi Jain· Dec 24, 2024

    protein-interaction-network-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Meera Iyer· Dec 20, 2024

    protein-interaction-network-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Meera Jain· Dec 4, 2024

    I recommend protein-interaction-network-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kabir Ghosh· Dec 4, 2024

    Keeps context tight: protein-interaction-network-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Tariq Bansal· Nov 23, 2024

    Keeps context tight: protein-interaction-network-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kabir Bhatia· Nov 23, 2024

    I recommend protein-interaction-network-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Oshnikdeep· Nov 15, 2024

    Registry listing for protein-interaction-network-analysis matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Diego Verma· Nov 11, 2024

    Useful defaults in protein-interaction-network-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • William Menon· Nov 7, 2024

    protein-interaction-network-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Aditi Garcia· Nov 3, 2024

    Solid pick for teams standardizing on skills: protein-interaction-network-analysis is focused, and the summary matches what you get after install.

showing 1-10 of 72

1 / 8