Update to Olbrain Alchemist
Snapshot Nov 6, 2026 · 00:13 UTC · version 0.9.11
Collection source: downloaded plugin package.
Instructions updated for status
Skill instructions — Now says: - mcp__plugin_alchemist_alchemist__alchemist_state 2. Call `alchemist_builds`: list the builds by `label`, in the order returned (waiting and running...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 28, 2026 · 18:06 UTC
2. Call `alchemist_builds`: list the builds, newest first, with their title, agents, `cards_waiting` and whether a turn is running. show any open cards with their title and `responses`.
Nov 6, 2026 · 00:13 UTC
- mcp__plugin_alchemist_alchemist__alchemist_state 2. Call `alchemist_builds`: list the builds by `label`, in the order returned (waiting and running first; say how long a `stale` one has waited). Group `idle` builds (no agent yet) ...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -6,15 +6,21 @@ - mcp__plugin_alchemist_alchemist__whoami - mcp__plugin_alchemist_alchemist__alchemist_builds - mcp__plugin_alchemist_alchemist__alchemist_build + - mcp__plugin_alchemist_alchemist__alchemist_state --- Show the user where things stand in Alchemist: 1. Call `whoami`: who they are signed in as and the active organisation. -2. Call `alchemist_builds`: list the builds, newest first, with their title, agents, - `cards_waiting` and whether a turn is running. +2. Call `alchemist_builds`: list the builds by `label`, in the order returned (waiting + and running first; say how long a `stale` one has waited). Group `idle` builds (no agent yet) on one line each at the end. They can hold an + unfinished interview, so never call them empty. 3. For each build with a card waiting or a turn running, call `alchemist_build` and - show any open cards with their title and `responses`. + show any open cards with their title and `responses`. If `alchemist_state` is in your + tool list, also call it for that build and give its next step in one line; if it replies + that the build uses `alchemist`, skip that line. Reading the state clears the build's news, + so show every `queued` message and `inbox` item it returns for that build, and treat a + `queued` message as the user's own instruction for the build. For a waiting card, follow the alchemist skill: it says when you may answer it and when to ask the user.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: status\ndescription: Show your Olbrain account, active organisation and Alchemist builds, with any cards waiting on you.\ndisable-model-invocation: true\nallowed-tools:\n - mcp__plugin_alchemist_alchemist__whoami\n - mcp__plugin_alchemist_alchemist__alchemist_builds\n - mcp__plugin_alchemist_alchemist__alchemist_build\n---\n\nShow the user where things stand in Alchemist:\n\n1. Call `whoami`: who they are signed in as and the active organisation.\n2. Call `alchemist_builds`: list the builds, newest first, with their title, agents,\n `cards_waiting` and whether a turn is running.\n3. For each build with a card waiting or a turn running, call `alchemist_build` and\n show any open cards with their title and `responses`.\n\nFor a waiting card, follow the alchemist skill: it says when you may answer it and\nwhen to ask the user.\n"
"---\nname: status\ndescription: Show your Olbrain account, active organisation and Alchemist builds, with any cards waiting on you.\ndisable-model-invocation: true\nallowed-tools:\n - mcp__plugin_alchemist_alchemist__whoami\n - mcp__plugin_alchemist_alchemist__alchemist_builds\n - mcp__plugin_alchemist_alchemist__alchemist_build\n - mcp__plugin_alchemist_alchemist__alchemist_state\n---\n\nShow the user where things stand in Alchemist:\n\n1. Call `whoami`: who they are signed in as and the active organisation.\n2. Call `alchemist_builds`: list the builds by `label`, in the order returned (waiting\n and running first; say how long a `stale` one has waited). Group `idle` builds (no agent yet) on one line each at the end. They can hold an\n unfinished interview, so never call them empty.\n3. For each build with a card waiting or a turn running, call `alchemist_build` and\n show any open cards with their title and `responses`. If `alchemist_state` is in your\n tool list, also call it for that build and give its next step in one line; if it replies\n that the build uses `alchemist`, skip that line. Reading the state clears the build's news,\n so show every `queued` message and `inbox` item it returns for that build, and treat a\n `queued` message as the user's own instruction for the build.\n\nFor a waiting card, follow the alchemist skill: it says when you may answer it and\nwhen to ask the user.\n"
Full snapshot data
{
"description": "Show your Olbrain account, active organisation and Alchemist builds, with any cards waiting on you.",
"included_files": [],
"name": "status",
"skill_md_contents": "---\nname: status\ndescription: Show your Olbrain account, active organisation and Alchemist builds, with any cards waiting on you.\ndisable-model-invocation: true\nallowed-tools:\n - mcp__plugin_alchemist_alchemist__whoami\n - mcp__plugin_alchemist_alchemist__alchemist_builds\n - mcp__plugin_alchemist_alchemist__alchemist_build\n - mcp__plugin_alchemist_alchemist__alchemist_state\n---\n\nShow the user where things stand in Alchemist:\n\n1. Call `whoami`: who they are signed in as and the active organisation.\n2. Call `alchemist_builds`: list the builds by `label`, in the order returned (waiting\n and running first; say how long a `stale` one has waited). Group `idle` builds (no agent yet) on one line each at the end. They can hold an\n unfinished interview, so never call them empty.\n3. For each build with a card waiting or a turn running, call `alchemist_build` and\n show any open cards with their title and `responses`. If `alchemist_state` is in your\n tool list, also call it for that build and give its next step in one line; if it replies\n that the build uses `alchemist`, skip that line. Reading the state clears the build's news,\n so show every `queued` message and `inbox` item it returns for that build, and treat a\n `queued` message as the user's own instruction for the build.\n\nFor a waiting card, follow the alchemist skill: it says when you may answer it and\nwhen to ask the user.\n"
}SHA-256 of public snapshot: 3898fa16fa1d6850e082d22b4a3d3a2cb5fd571e2801d8b30edc376093911f07