Pdb Database
ListedAccess and query protein data banks like PDB using structured queries to retrieve experimental structural information.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add davila7/claude-code-templates --skill pdb-database -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
davila7
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
We could not read this skill's source, so none of the checks below were run.
About this skill
pdb-database
What it does
This skill enables AI agents to interact directly with Python debugging databases, allowing them to inspect breakpoints, variables, and call stacks during runtime. It bridges the gap between code execution and deep diagnostic analysis within the Python ecosystem.
When to use it
- Debugging complex logic errors where standard print statements are insufficient.
- Inspecting variable states at specific breakpoints in a running script.
- Analyzing call stacks to trace the origin of unexpected exceptions.
- Reviewing local and global scopes during an active debugging session.
Key capabilities
- Access to Python debugger (pdb) database structures.
- Inspection of current execution context and frame information.
- Retrieval of variable values and object states at pause points.
- Navigation through call stack frames for root cause analysis.
Example prompts
- "Show me the value of
user_datain the current frame." - "List all variables defined in the global scope right now."
- "Trace back through the call stack to find where this exception originated."
Tips & gotchas
Ensure your target Python script is running with the debugger attached before querying for state information. This skill relies on active breakpoints; it cannot inspect a program that has already finished execution unless specific history data is preserved.