General
tooluniverse-protein-modification-analysis - Claude MCP Skill
Post-translational modification (PTM) analysis — phosphorylation, ubiquitination, acetylation, glycosylation, methylation. Uses iPTMnet (sites + enzymes), ProtVar (functional consequences), UniProt (baseline), STRING, ELM (linear motifs), MassIVE/ProteomeXchange (experimental). Use for PTM site annotation, kinase-substrate identification, and PTM-disease associations.
SEO Guide: Enhance your AI agent with the tooluniverse-protein-modification-analysis tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to post-translational modification (ptm) analysis — phosphorylation, ubiquitination, acetylation, glyco... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# Protein Post-Translational Modification Analysis Comprehensive PTM analysis using iPTMnet (primary), ProtVar (functional context), UniProt (baseline), STRING (interactions), ELM (linear motifs), and MassIVE/ProteomeXchange (experimental data). ## LOOK UP DON'T GUESS - PTM sites/enzymes: `iPTMnet_get_ptm_sites` - Functional consequence: `ProtVar_get_function` + `iPTMnet_get_ptm_ppi` - Proteoforms: `iPTMnet_get_proteoforms` - Linear motifs: `ELM_get_instances` ## COMPUTE, DON'T DESCRIBE When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it. ## Domain Reasoning PTMs are context-dependent: same phosphorylation site can activate or inhibit depending on kinase and effectors. Always check: which enzyme, what functional consequence, in what cell context. --- ## KEY PRINCIPLES 1. **Disambiguation first** -- resolve to UniProt accession before iPTMnet calls 2. **iPTMnet is SOAP-style** -- every call requires `operation` parameter 3. **Evidence-graded** -- distinguish experimental (T1) from predicted (T4) 4. **English-first queries** --- ## Workflow ``` Phase 0: Protein Disambiguation → UniProt accession Phase 1: PTM Site Inventory → iPTMnet_get_ptm_sites Phase 2: Proteoform Analysis → iPTMnet_get_proteoforms Phase 3: PTM-Dependent Interactions → iPTMnet_get_ptm_ppi Phase 4: Functional Context → ProtVar_get_function at key sites Phase 4b: Linear Motif Context → ELM_get_instances for SLiM overlap Phase 4c: Experimental Data → MassIVE/ProteomeXchange Phase 5: Synthesis & Report ``` --- ## Phase 0: Disambiguation - `iPTMnet_search(operation="search", search_term="TP53", role="Substrate")` -- find UniProt IDs - If user provides UniProt accession directly, use it - Select human entry if multiple hits ## Phase 1: PTM Sites `iPTMnet_get_ptm_sites(operation="get_ptm_sites", uniprot_id="P04637")` -- returns position, residue, modification type, enzyme, evidence. Group by modification type. Fallback: `UniProt_get_entry_by_accession` PTM annotations. ## Phase 2: Proteoforms `iPTMnet_get_proteoforms(operation="get_proteoforms", uniprot_id=...)` -- distinct PTM combinations. Focus on those with functional/disease annotations if >20. ## Phase 3: PTM-Dependent Interactions `iPTMnet_get_ptm_ppi(operation="get_ptm_ppi", uniprot_id=...)` -- interacting protein, PTM site, effect (enables/disrupts). Supplement with `STRING_get_interaction_partners(identifiers=gene, species=9606, required_score=700)`. ## Phase 4: Functional Context `ProtVar_get_function(accession=..., position=N, variant_aa=AA)` -- domain, active site, binding site, conservation. Grade: active-site PTM > domain-core > disordered region. ## Phase 4b: Linear Motifs (ELM) `ELM_get_instances(operation="get_instances", uniprot_id=..., motif_type="MOD")` -- MOD = modification sites, DEG = degradation signals. Cross-reference with Phase 1 PTM positions. `ELM_list_classes(operation="list_classes")` for motif details. ## Phase 4c: Experimental Data `MassIVE_search_datasets(species="9606")`, `MassIVE_get_dataset(accession="MSV...")` for public MS datasets. --- ## Evidence Grading | Tier | Criteria | |------|----------| | T1 | PTM at validated active/binding site with functional data | | T2 | PTM in structured domain with ProtVar annotation | | T3 | Correlation data only (mass spec detection) | | T4 | Predicted, no experimental validation | --- ## Tool Parameter Reference | Tool | Key Params | |------|-----------| | `iPTMnet_search` | `operation="search"`, `search_term`, `role` | | `iPTMnet_get_ptm_sites` | `operation="get_ptm_sites"`, `uniprot_id` | | `iPTMnet_get_proteoforms` | `operation="get_proteoforms"`, `uniprot_id` | | `iPTMnet_get_ptm_ppi` | `operation="get_ptm_ppi"`, `uniprot_id` | | `ELM_get_instances` | `operation="get_instances"`, `uniprot_id`, `motif_type` | | `ELM_list_classes` | `operation="list_classes"` | | `MassIVE_search_datasets` | `page_size`, `species` | **Critical**: All iPTMnet and ELM tools require `operation` as first parameter (SOAP-style). --- ## Fallbacks | Situation | Fallback | |-----------|----------| | Not in iPTMnet | UniProt PTM/processing annotations | | No PTM-PPI data | STRING general PPI | | No ProtVar data | UniProt domain annotations | | No ELM data | Proceed with iPTMnet/UniProt only | ## Limitations - iPTMnet biased toward well-studied proteins - Proteoform data covers observed combinations only - PTM-PPI: only PTM-specific evidence; more PPIs exist in STRING
Signals
Information
- Repository
- mims-harvard/ToolUniverse
- Author
- mims-harvard
- Last Sync
- 9/5/2026
- Repo Updated
- 9/5/2026
- Created
- 3/25/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
cursorrules
CrewAI Development Rules
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
firecrawl-build
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
Related Guides
Python Django Best Practices: A Comprehensive Guide to the Claude Skill
Learn how to use the python django best practices Claude skill. Complete guide with installation instructions and examples.
Mastering Python and TypeScript Development with the Claude Skill Guide
Learn how to use the python typescript guide Claude skill. Complete guide with installation instructions and examples.
Mastering Data Science with Claude: A Complete Guide to the Pandas Scikit-Learn Skill
Learn how to use the pandas scikit learn guide Claude skill. Complete guide with installation instructions and examples.