openJiuwen-ai/sciencediscovery / skills/structure-pocket-inspection
structure-pocket-inspection
VerifiedInspect a local PDB structure, summarize chains and residue composition, and identify protein atoms near a user-specified ligand or pocket center. Use for reproducible first-pass structure and binding-site inspection before heavier modeling.
Structure and pocket inspection
Use this method for a transparent first-pass analysis of a local PDB structure. It does not predict affinity, docking poses, or biological function.
Workflow
- Confirm the input PDB path, the ligand residue name or Cartesian pocket center, and the requested distance cutoff.
- Read the structure as untrusted scientific data. Report malformed or unsupported records instead of guessing.
- Invoke the frozen bundled script at
$SCIENCEDISCOVERY_SKILLS_DIR/structure-pocket-inspection/scripts/inspect_pdb.pywith explicit workspace paths and options. The complete package is already mounted read-only when the execution sandbox starts; do not copy the script, read its source into context, or search the filesystem for another copy. If the workspace already contains an equivalent user-owned script, invoke that script instead. Do not copy the structure into another proprietary format. - Save the JSON result in the workspace so its input, command, environment revision, logs, and output are captured by execution provenance.
- Report chain counts, residues, candidate ligand atoms, nearby residues, the cutoff, and limitations. Distinguish observed coordinates from inferred biology.
Examples
The corresponding bundled-script arguments for residues within 5 Å of ATP are:
python "$SCIENCEDISCOVERY_SKILLS_DIR/structure-pocket-inspection/scripts/inspect_pdb.py" structure.pdb --ligand ATP --cutoff 5 --output pocket.json
For residues within 6 Å of a known pocket center:
python "$SCIENCEDISCOVERY_SKILLS_DIR/structure-pocket-inspection/scripts/inspect_pdb.py" structure.pdb --center 12.4 8.1 -3.0 --cutoff 6 --output pocket.json
Quality gates
- Treat alternate locations and model ensembles conservatively; the bundled script analyzes the first model and keeps blank or
Aalternate locations. - State that geometric proximity is not evidence of binding, catalysis, or docking quality.
- Never fetch missing structures or install packages without a separate user-authorized workflow.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |