القائمة
Use when visually verifying Burrete Browser preview or desktop app state without replacing typed observe/action contracts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Preview supported molecular attachments or an explicit public PDB ID in Burrete's interactive viewer, or use the bounded hosted Ketcher editor for transient chemical sketches.
Use when an external agent must open, observe, control, or render into a Burrete molecular workspace without managing transport details.
Primary router for Burrete. Use when the plugin is at-mentioned or for molecular workspace work: opening structures, operating Mol* or Ketcher, reviewing SDF/property collections, trajectories, workflow result bundles, molecular reports, or Browser/Computer visual QA.
Use when opening molecular artifacts in Burrete Browser preview or desktop app sessions and establishing an observable workspace.
Use when molecular notes, property tables, charts, workflow reports, or provenance should be rendered beside an active Burrete workspace.
Use when reviewing SDF or molecule-property collections with bounded tables, filters, selected-molecule handoff, and Burrete panels.
| name | visual-qa |
| description | Use when visually verifying Burrete Browser preview or desktop app state without replacing typed observe/action contracts. |
Use Browser and Computer as verification surfaces.
Use Browser for:
scripts/burrete-agent.mjs open --mode browser-agent-shell ..., such as
http://127.0.0.1:<fresh-port>/?devFiles=<encoded absolute path>, when the user
wants ordinary Burrete UI chrome, sidebars, right dock, bottom dock, tabs, or
app-like behavior;Browser means the Codex in-app Browser plugin. Do not use macOS open, Arc,
Chrome, Safari, or another external browser for Browser visual QA unless the
user explicitly asks for an external browser. If the in-app Browser cannot open
the local URL, report that blocker and keep the URL available for the user
instead of silently switching browsers.
Prefer browser agent shell over tokenized browser-preview when the user is
checking menus, docks, sidebars, tabs, or other shell-level UI. Prefer
tokenized browser-preview when the QA depends on MCP agent transport,
observe, act, or action logs.
Do not reuse another browser-dev port for a new agent-owned shell. Reuse an already useful Browser tab only when the user explicitly asks to keep working on that exact surface or when a reload is required after a code or asset change.
Use Computer for:
Computer can see some Mol* toolbar elements, but it cannot reliably provide
chains, ligands, waters, atoms, residues, or selections as typed molecular
state. Always prefer observe for molecular truth.
Visual QA should cite what was checked:
For a requested molecular visualization, inspect the central viewer canvas, not only the shell chrome or Info/Inspector counts. A black, empty, or otherwise non-rendered central canvas fails QA even if the file name and molecular counts are correct elsewhere in the app.
If the central canvas is blank after typed readiness passes, run exactly one
reset_camera action, observe again, and take another screenshot. If it is
still blank, report the visualization as failed with the typed state and visual
evidence; do not claim success and do not loop on camera resets.