Pymol

Google DeepMindOfficialPublished by Google DeepMind

Skill
Tool integration
Science and research
Apache-2.0
No issues found

From the author

Visualize, analyze, and render protein and molecular structures using PyMOL. Use when the user wants to create images of protein structures, perform structural alignments or superposition, measure distances or contacts, highlight binding sites or active site residues, color by B-factor/pLDDT, or analyze protein-ligand interactions. Do not use for docking, molecular dynamics, or sequence-only analysis.

— the description by Google DeepMind

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

PyMOL is a tool for the visualization, analysis, and rendering of protein and molecular structures. It operates in a headless environment using OSMesa for software rendering, allowing users to generate images of structures, measure distances, perform structural alignments, and analyze protein-ligand interactions. The skill requires existing structure files and provides output in PNG format along with session files for further local exploration.

What it does

Renders protein and molecular structure images
Performs structural alignments and superpositions
Measures distances and contacts between residues
Highlights binding sites and active site residues
Colors structures by B-factor or pLDDT values
Analyzes protein-ligand interactions

When to use it

When you need to visualize a protein structure file
When you want to compare two structures via alignment
When you need to identify or highlight specific residues or binding sites
When you want to generate images of molecular structures for analysis
When you need to save a session for further inspection in local PyMOL

Advantages

Enables headless rendering without requiring a GPU or display
Supports standard structural analysis tasks like distance measurement and alignment
Provides session files for continued work in local environments
Automates visualization workflows through Python scripting

Usage examples

“Create an image of my protein structure colored by secondary structure.”: The agent generates a PNG image showing the protein with helices, sheets, and loops colored distinctly and saves a .pse session file.
“Show me the active site residues for this protein.”: The agent identifies the specified residues, renders them as sticks, and provides an image highlighting the active site.
“Align these two protein structures and tell me the RMSD.”: The agent performs the structural alignment and reports the calculated RMSD value to the user.
“Color my AlphaFold model by pLDDT confidence.”: The agent applies canonical AlphaFold coloring thresholds to the structure and renders the result.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/google-deepmind/pymol/download
Unzip it into the cross-client skills folder of your project:
```
mkdir -p .agents/skills && unzip pymol.zip -d .agents/skills
```

Documentation by Google DeepMind

PyMOL

Prerequisites

uv: Read the uv skill and follow its Setup instructions to ensure uv is installed and on PATH.
User Notification: If .licenses/pymol_LICENSE.txt does not already exist in the workspace root directory then (1) prominently notify the user to check the license at https://www.pymol.org/, then (2) create the file recording the notification text and timestamp.

Overview

All PyMOL commands run on the host via uv with OSMesa software rendering — no GPU, display, or X server is needed. Structure files must be downloaded to the host before running PyMOL.

Do NOT use when:

The user wants to run AlphaFold predictions.
The user wants docking or molecular dynamics simulations.
The user only has a sequence and no structure file — fetch the structure first. Check if any other installed skills can retrieve structures from the PDB or AlphaFold Database before proceeding.

Setup (Agent Instructions)

Ensure that uv is installed on the host system. The PyMOL scripts use PEP 0723 headers to declare their dependencies, and uv run will automatically handle installing them (including pymol-open-source-whl) when the script is executed.

Core Rules

Output paths must be absolute or relative to the user's project root. Always run PyMOL scripts from the user's project directory.
Software rendering only. Use cmd.png() for output. Never use cmd.draw() or cmd.ray() with hardware acceleration — OSMesa does not support it. Set environment variable PYOPENGL_PLATFORM=osmesa for headless rendering.
Always save a .pse session file alongside any PNG output. This lets the user open the session in their local PyMOL for further inspection.
Always call cmd.quit() at the end of every PyMOL script. Omitting it causes the process to stop responding.
Init boilerplate is mandatory. Every PyMOL script must begin with the initialization sequence. from pymol import cmd must come after finish_launching(), not before.
See references/PYMOL_REFERENCE.md for selection syntax, common commands, and gotchas.
Pre-Flight File Check: Before writing the PyMOL script or running it, you MUST verify that the requested structure file actually exists on the host machine.
Verify Structure Load: After loading a structure with cmd.load(), always verify it succeeded by checking cmd.count_atoms("all"). If the result is 0, print an error to stdout and call cmd.quit() immediately.
Auto-detect Alpha-Carbon Trace: For a cartoon representation your PyMOL scripts should automatically detect if the structure is an alpha-carbon trace (cmd.count_atoms("name CA") == cmd.count_atoms("all")), then you MUST follow the Alpha carbon trace cartoon recipe.
Notification: If this skill is used, ensure this is mentioned in the output.

Quick Start

Ensure structure files are downloaded to a directory in the user's project.
Write a PyMOL Python script (e.g., render.py) with the required init boilerplate and PEP 0723 header.
Run it via uv run: bash uv run render.py

Minimal example script (`render.py`)

# /// script
# requires-python = ">=3.10, <3.13"
# dependencies = [
#     "pymol-open-source-whl",
# ]
# ///

import os
import sys

# Set environment variable for headless rendering
os.environ["PYOPENGL_PLATFORM"] = "osmesa"

import pymol # pytype: disable=import-error
pymol.pymol_argv = ["pymol", "-cq"]
pymol.finish_launching()

from pymol import cmd # pytype: disable=import-error

cmd.load("AF-P00520-F1-model_v4.cif", "structure")
cmd.show("cartoon")
cmd.color("green", "ss h")
cmd.color("yellow", "ss s")
cmd.color("gray", "ss l+''")
cmd.orient()
cmd.set("ray_opaque_background", 1)
cmd.png("output/render.png", width=1200, height=900, dpi=150)
cmd.save("output/session.pse")
cmd.quit()

Common Recipes

See references/RECIPES.md for complete, copy-paste ready recipes. Available recipes:

Cartoon with secondary structure coloring — basic helix/sheet/loop coloring
Alpha carbon trace cartoon — force cartoon representation for CA-only structures
B-factor (pLDDT) coloring — continuous spectrum coloring by B-factor
AlphaFold pLDDT coloring — canonical threshold-based confidence colors
Highlight specific residues — show active site or key residues as sticks
Surface rendering — transparent surface over cartoon
Electrostatic surface rendering — vacuum electrostatics (qualitative)
Multi-chain complex colors — automatic per-chain coloring
B-factor putty analysis — tube width proportional to flexibility
Cavity and pocket visualization — surface cavity detection with ligand focus
Multi-structure batch rendering — render a directory of structures
Measure distance between residues — CA–CA distance with labels
Zoom into binding pocket — simple pocket focus
Protein-ligand interaction — ligand isolation, styled rendering, polar contacts
Two-structure superposition with RMSD — align/cealign with auto-fallback
In silico mutagenesis — mutate residues with the mutagenesis wizard
Load and modify an existing session — re-open a .pse file

Interpreting Output

The output/ directory contains PNG images and a .pse session file.
Any measurements or metrics (distances, RMSD, atom counts) are printed to stdout by the PyMOL script. Report these values to the user.
Present PNG images to the user and describe the visualization.
Tell the user they can open the .pse file in their local PyMOL to further explore, rotate, or modify the visualization.
If the user wants modifications, load the saved .pse in a new script and re-run.
Large sessions with surfaces can exceed the --max_output_mb limit (default 500 MB). Increase it with --max_output_mb=1000 if needed.

Files

ATTRIBUTION.mdAdded by AutoGineer892 B
LICENSELicence file added by AutoGineer11.1 KiB
SKILL.md6.5 KiB
references/PYMOL_REFERENCE.md5.3 KiB
references/RECIPES.md11.1 KiB
references/citation.bib143 B

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by

Google DeepMind

Publisher

Google DeepMind (Official)

Source

google-deepmind/science-skills · skills/pymol · commit 4de6786

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

AutoGineer is not affiliated with or endorsed by Google DeepMind or Google DeepMind.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download pymol.zip