Menu
Use when loading Burrete's scoped capability registry and setup status before a molecular workspace workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | user-context |
| description | Use when loading Burrete's scoped capability registry and setup status before a molecular workspace workflow. |
This skill owns Burrete preflight. It does not store general memory.
Run the read-only preflight script before ordinary Burrete work:
node plugins/burette-agent/scripts/burette_agent_preflight.mjs
The script reports:
scripts/burrete-agent.mjs is available;scripts/agent-preview.mjs is available;BURRETE_AGENT_APP, if any;Use this payload to decide workflow routing, not to claim live viewer state. For
live state, run burrete-agent observe.
Persisted context should stay narrow:
auto, browser-agent-shell, browser-preview, or desktop-app);Do not store arbitrary molecule facts, user reports, private files, or workflow outputs here. Those belong in bounded artifacts or workspace reports.
If the CLI or browser preview script is missing, stop the current Burrete path and report the blocker. Do not fall back to Computer-only control for molecular operations because it cannot provide reliable chains, ligands, waters, or selection state.
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 visually verifying Burrete Browser preview or desktop app state without replacing typed observe/action contracts.
Use when molecular notes, property tables, charts, workflow reports, or provenance should be rendered beside an active Burrete workspace.