Sharing specialists, skills, playbooks, templates, variables and memory

Move specialists, skills, playbooks, prompt templates, variable definitions and project notes between BattleLab installs: your own second machine, or a colleague's. You export a selection to one file (*.battlelab) and import that file on the other install through a preview. Importing always makes new copies and never changes anything that was already there.

Export

1. Open Library → Specialists, Library → Skills, Library → Playbooks, Prompt templates or Library → Variables and choose Export….
2. Tick what to share. Anything a chosen item needs comes along and is marked Included: a playbook's role skills, the skills a specialist pins, or the variables a template's fields use. An included item can't be unticked on its own; untick the item that needs it instead.
3. Choose Download bundle.

The file holds the chosen items exactly as written; no settings, deployment files or stored values of your secret variables are added. Check the text before you share it: a token, password or key pasted into a skill or playbook file goes into the bundle with it, even when it is the value of one of your secret variables. A role skill your library doesn't hold travels as a name only, the same as it works on this install.

A mission plan travels as its document: its slots, objectives, order, procedures and the names of its inputs. Its title, summary and slot labels are checked for your stored secrets first. See Mission plans.

A specialist travels as its job: title, summary, capacity, and the skills it pins, exactly at the versions it pins. Its agent, model and effort go along only as a suggestion. Its notes, sessions, grade and project names stay on your install. If a skill it pins has changed since the specialist was saved, or is gone, it can't be exported as that version: open the specialist and save a new version, then export it. Archived specialists aren't offered.

A prompt template travels as its message: name, description, tags, text, fields and reference images, plus every library variable its fields use. Its usage counts stay here. A variable travels as its definition (type, label, description and default) and, for a text variable, its value. A secret, or a secret file, travels as its definition only: the export never adds its stored value. Before anything is written, every template and variable text, defaults included, is checked for your stored secrets and for keys, tokens and passwords. One that holds any isn't exported; the reason names the field, never the value. Project bindings, collections and agent access stay here too.

Import

1. Choose Import… on any of those Library pages, then choose or drop a .battlelab file (up to 32 MB).
2. BattleLab checks the whole file before it shows anything. A file that isn't a valid bundle is refused with the reason, and nothing is read into your library. A bundle made by a newer BattleLab asks you to update first.
3. The preview lists every item and what it becomes here:
   • New copy: the ID is free.
   • Renamed: an item with that ID already exists here. Yours stays untouched; the copy gets a new ID such as tdd-2. A playbook in the same file that uses a renamed skill is pointed at the new ID. A variable is renamed api_url_2 (names have no hyphen), also when a template or project here already uses its name, and a template in the file that uses it follows: its field and every in its text become api_url_2.
   • Arrives empty: a secret (or a variable the file carries no value for). It is created without a value; set it on Library → Variables before you send a template that uses it.
   • Reused: a skill you imported from a file earlier, with exactly this content, and haven't changed since. Nothing is copied; the specialists and playbooks in the file use your copy. A skill that only has the same name is never reused: it gets a renamed copy instead.
   • Refused: it can't be imported, with the reason. If you untick a skill that a playbook or specialist needs, or a variable a template uses, that item is refused too ("needs skill …, which isn't being imported"). Nothing is ever created without what it needs.
4. Open Review files on an item to read its complete text. A file too large to show, or not text, can't be reviewed there: importing it needs an explicit acknowledgement. For a renamed playbook, or one that uses a renamed skill, the files are shown as sent. On import a renamed playbook's ID changes, the role skill names in its flows follow any renamed skill, and each rewritten TOML file is saved without its comments or original layout. Bundles aren't signed, and skills and playbooks are instructions your agents will read.
5. For each specialist, choose what it runs on here (Runs on). The file only suggests an agent, model and effort. When the suggestion works on this install it's already filled in. When it doesn't (for example, the suggested agent isn't installed), the row says why, and Import stays unavailable until you choose an agent. Only agents that can start a session here are offered, and a specialist that pins skills needs an agent that can load them. The grade shown comes from your own model grades (Settings → Agents).
6. Choose Import. Nothing changes until you do. If a choice stopped working in the meantime, nothing at all is imported: the row says which choice and why, so you can change it and import again.

The result lists each item as Created (with an Open link), Refused, Failed or Skipped (it needed an item that failed). Imported copies carry an Imported from a file mark. A variable that arrived empty (a secret, or a text variable the file carried no value for) offers Set value, which opens Library → Variables at it. A reused skill is listed as Reused. An imported specialist is a new specialist at version 1, pinned to the imported or reused skills; nothing is started. An imported template is never sent, and an imported variable is bound to no project and offered to no agent. Nothing is activated, deployed, launched or made a default by an import.

When to preview again

A preview lasts 15 minutes and matches your library as it was when the preview was made. If the preview expired, or your library changed in the meantime (for example, a skill named tdd-2 was created), BattleLab asks you to Preview again instead of applying an out-of-date plan.

Confirming the same preview twice is safe. Items already imported are reported as they were, and no second copy is made. Retry failed items tries only what didn't make it.

Project memory

A project's shared notes travel in the same file. Open Library → Memory, select the project, and use Export… or Import… in its bar.

Export. The project's notes start chosen. You can add the notes a specialist keeps in this project; that brings the specialist (and the skills it pins) along, marked Included. A file holds the memory of one project. Each note travels as its name, description, type and text: not the project's name or ID, and not who wrote it. A note that holds one of your stored secrets or looks like a key, token or password stays here, and so does every quarantined item. The picker and the download say only how many stayed, never which. If the secret check can't run, no memory is exported. The Markdown .zip of the notes is still there, as a link in the export dialog.

Import. Notes go into the project open on the page, and only while its memory is on: an import never turns memory on. From any other Library page, a file's notes wait and say where to import them. The preview judges each note the way an agent's note is judged:

• New: it will be added.
• Held back: it holds one of your stored secrets or looks like a credential. It is never stored and never put in the review tray, and its text isn't shown.
• Refused: it isn't a note memory can hold.

A note is added beside your own, never over it: one with the same name as yours gets -2, and one identical to a note you already have is left as it is (Already here in the result). A specialist's notes go into the notebook of the specialist this import creates. Each note has its own result, and one failed note never stops the others; Retry failed items tries only it. Imported notes read imported from a file. To undo an import, delete the notes you don't want.

Coming later

Secret values will stay out unless you choose to include them encrypted under a passphrase you type.