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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionprotein-interaction-network-analysisExecute the skills CLI command in your project's root directory to begin installation:
Fetches protein-interaction-network-analysis from mims-harvard/tooluniverse and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate protein-interaction-network-analysis. Access via /protein-interaction-network-analysis in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
1.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.2K
stars
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.
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.
| 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 |
STRING_map_identifiers(): validate protein names, get STRING IDsSTRING_get_network() (primary); BioGRID_get_interactions() (fallback, requires API key)STRING_functional_enrichment() for GO/KEGG/Reactome; STRING_ppi_enrichment() to test functional coherenceSASBDB_search_entries() for SAXS/SANS solution structuresSee python_implementation.py for runnable examples (example_tp53_analysis(), analyze_protein_network()).
| 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) |
| Score | Use Case |
|---|---|
| 0.4 | Exploratory analysis (default STRING threshold) |
| 0.7 | Recommended — reliable interactions |
| 0.9 | Core interactions only |
Key fields returned per interaction edge:
score — combined confidence (0–1)escore — experimental score (use for physical binding evidence)dscore — database scoretscore — text mining scoreascore — coexpression scorepreferredName_A, preferredName_B — gene namesSignaling 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 setsDruggability & Clinical Context:
DGIdb_get_drug_gene_interactions — drug interactions for hub proteins (param: genes as array)DGIdb_get_gene_druggability — druggability categoriesgnomad_get_gene_constraints — gene essentiality metrics (pLI, oe_lof)civic_search_evidence_items — clinical evidence for mutations in network proteinsUniProt_get_function_by_accession — protein function annotationinteraction_ids are in the metadata field of the response, NOT at the top level:
interaction_ids = result.get("metadata", {}).get("interaction_ids", [])
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.
protein_name AliasIntAct tools accept protein_name as an alias parameter in addition to the original identifier parameter.
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.
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:
When a symmetric multimer binds a ligand, statistical factors affect the apparent rate constants:
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).
| 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.
For "what protein does X" questions: ALWAYS search UniProt and PubMed first — do not guess from memory. Key pathways to know:
confidence_score=0.4BIOGRID_API_KEY in environment; STRING works without a key2>&1 | grep -v "Error loading tools" (see KNOWN_ISSUES.md)Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
protein-interaction-network-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
protein-interaction-network-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend protein-interaction-network-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: protein-interaction-network-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: protein-interaction-network-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend protein-interaction-network-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for protein-interaction-network-analysis matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in protein-interaction-network-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
protein-interaction-network-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
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