AIBAST Easy Mode
Once you have read this file (the person sent one line naming its public URL;
nothing was downloaded or attached), you own the whole workshop: discovery,
local testing, Draft deployment, Preview validation, and the evidence verdict.
If the line that pointed you here also named a solution or workshop ("…and run
the X workshop for me"), treat that as the first request and start at once.
There is one mode. The person never picks "with Brainstem" or "Copilot only";
you decide the engine yourself in the first minute (see "Pick the engine") and
never mention the choice unless they ask.
Public source
- Repository:
microsoft/aibast-agents-library
- Workshop branch:
main
- Registry path:
registry.json
Resolve the branch through the GitHub API and pin one immutable commit SHA
before downloading anything.
Persist the active run in .aibast/easy-mode-state.json, including solution,
revision, engine (brainstem or copilot), local test results, Copilot
Studio identity, status, and published: false. When the direct engine is
used, also persist the Copilot Studio plugin repository, installed plugin ID,
resolved revision or installed version, PAC CLI version, and verification
status.
Pick the engine (you, silently, in the first minute)
Brainstem is the person's personal, on-device training AI. It works alongside
Copilot, remembers the workshop, and hot-loads specialized instructors while
Copilot remains the familiar work surface. Prefer it; fall back without fuss.
- Check
http://localhost:7071/health. If it answers, the engine is
brainstem. Go to "Show it in VS Code".
- If it does not answer, start or install it yourself and wait up to two
minutes for
/health:
- prefer
~/.copilot/bin/brainstem start, then brainstem on the PATH
- otherwise the public installer:
Mac or Linux
curl -fsSL https://microsoft.github.io/aibast-agents-library/install.sh | bash,
Windows (PowerShell) irm https://microsoft.github.io/aibast-agents-library/install.ps1 | iex
- if
/health reports Copilot is not signed in, open
http://localhost:7071/login for the person and say: "Sign in with your
GitHub account, then tell me when you're done."
- If
/health still does not answer (no permission to install, the port is
held by something else, the installer failed), the engine is copilot.
Record why in the state file in one line and continue. Never ask the
person to fix it and never stop here.
Show it in VS Code (engine brainstem, when you are running in VS Code)
Put the Brainstem's own folder in the Explorer so the person sees their AI as
files they own: run code --add ~/.brainstem/src/rapp_brainstem (Windows:
code --add %USERPROFILE%\.brainstem\src\rapp_brainstem), or the VS Code
command Workspaces: Add Folder to Workspace with that folder. Then open
http://localhost:7071 in VS Code's built-in browser beside this chat: use
your open-browser tool if you have one, otherwise the VS Code command
Simple Browser: Show with that address. Say in one sentence: "This is your
Brainstem; soul.md is its personality and every *_agent.py in agents/ is
a skill." Outside VS Code, open it in the person's normal browser instead.
Choose from the library
When the user asks what is available, or asks for a workshop without naming
one (for example Show me the AIBAST library, then give me the workshop I pick using Easy Mode and test it for me):
- Fetch
registry.json from the pinned commit.
- List every entry whose
_catalog_kind is solution, grouped by
category written as a plain industry name, one line per workshop:
display_name — description. Do not paste JSON or file paths.
- Ask one question: which workshop they want. Accept a number, a name, or a
description, resolve it to exactly one registry entry, and confirm the
display_name back to them.
- Continue as
Give me <solution> using Easy Mode and test it for me with
that entry.
Never choose for the user, and never download a workshop before they choose.
Build and test
When the user says Give me <solution> using Easy Mode and test it for me:
With engine brainstem:
- Resolve
@aibast-agents-library/workshop from the immutable registry.
- Download its exact
_file, verify _sha256, and import it through
POST http://localhost:7071/agents/import.
- Send the user's request to
POST http://localhost:7071/chat.
- Continue executing every Brainstem handoff without asking the user to steer.
- Brainstem's generic workshop engine must discover the requested package,
hot-load the business agent, and run every locked local case.
With engine copilot:
- Run the repository-owned, fail-closed setup step
python3 tools/easy_mode_preflight.py --json and require passed: true.
Stop when it exits nonzero or reports passed: false, and report the
remediation it printed. Record the installed plugin/version and PAC CLI
version in .aibast/easy-mode-state.json.
- Resolve the requested solution from immutable
registry.json.
- Fetch its
deployment.json, export-manifest.json, portable *_agent.py,
tests/demo_cases/<slug>.json, reviewed instructions, knowledge, skills,
Copilot Studio source, and every tool named by the manifest.
- Verify the portable source SHA.
- Create an isolated workspace with only required files and BasicAgent.
- Import the class named by
deployment.json.
- Execute every locked case with its operation and arguments.
- Validate every
must_include and must_not_include marker.
Either way: persist status: tested, return the verdict with exact case
totals, and offer the next message:
Deploy it into Copilot Studio for me.
Required Copilot Studio plugin (engine copilot, before any deployment)
The preflight owns plugin discovery, installation, and PAC remediation. Its
explicitly reviewed CLI sequence is:
Check whether the mcs-assistant Copilot Studio capabilities are already
available.
If they are missing, execute these GitHub Copilot plugin-manager commands
in order:
copilot plugin marketplace add microsoft/copilot-studio-plugin
copilot plugin install mcs-assistant@copilot-studio-plugin
Recheck copilot plugin list, then resolve
microsoft/copilot-studio-plugin through the GitHub API and record
its immutable default-branch commit SHA or the installed plugin version in
.aibast/easy-mode-state.json.
Inspect pac --version, including version output from a nonzero exit. The
plugin requires a Power Platform CLI version newer than 2.9.3. When PAC is
too old and .NET is available, run:
dotnet tool update --global Microsoft.PowerApps.CLI.Tool
Recheck PAC and otherwise stop with the reported remediation.
Verify the installed plugin exposes the Copilot Studio manage, describe,
initialize, and architect capabilities. Do not continue to deployment when
any required capability is unavailable.
Use only microsoft/copilot-studio-plugin and the installed ID
mcs-assistant@copilot-studio-plugin. Do not substitute a fork or execute
unreviewed plugin source directly. The plugin is experimental, so validate all
generated YAML and stop on schema or PAC validation errors.
Deploy
When the user says Deploy it into Copilot Studio for me:
With engine brainstem:
- Send that exact request to Brainstem
/chat.
- Resolve
it from Brainstem's persisted active workshop.
- Continue every returned handoff.
- Use the real Copilot Studio front door for Preview validation.
- Return captured evidence to Brainstem using its callback schema.
- Do not stop until Brainstem reports
status: complete.
With engine copilot:
- Resolve
it from .aibast/easy-mode-state.json.
- Re-verify
mcs-assistant@copilot-studio-plugin, its recorded revision or
version, and the required PAC CLI version.
- Resolve the active PAC environment without asking when one is selected.
- Use the plugin's read-only describer for an existing agent and its
deterministic initializer only when a new target project is required.
- Use the plugin architect to assemble or migrate the exact reviewed
instructions, knowledge, skills, model, and modern agentic-loop YAML.
- If the recorded schema exists, use the plugin manager to clone and
reconnect automatically, then pull and reconcile it.
- Remove web search and unapproved tools, then validate the generated source
and PAC project before any remote write.
- Use the plugin manager to push the Draft. Never invoke publish.
- Open the real Draft and run every locked case in a fresh Preview chat.
- Validate all markers and capture evidence.
Either way: persist status: complete and report exact totals, the engine
used, plugin provenance when the direct engine deployed, and
published: false.
Rules
- Own all terminal, file, PAC CLI, browser, and evidence work.
- Never ask the user for URLs, environment IDs, commands, or test markers.
- Never ask the user to choose an engine, a lane, or a mode.
- Never mix assets from different Git revisions.
- Never deploy through the direct engine without the verified Microsoft
Copilot Studio plugin and supported PAC CLI.
- Never invent a missing result or success-shaped fallback.
- Never retry until a response happens to pass.
- Stop at Draft. Never publish.
1---2name: aibast-easy-mode3description: Run any supported AIBAST workshop for a person from one line in GitHub Copilot Chat. The skill sets up and uses the person's Brainstem when it can, runs directly in Copilot when it cannot, and the person never has to choose.4metadata:5 source: https://skillmd.com/skills/microsoft/aibast-easy-mode6---78# AIBAST Easy Mode910Once you have read this file (the person sent one line naming its public URL;11nothing was downloaded or attached), you own the whole workshop: discovery,12local testing, Draft deployment, Preview validation, and the evidence verdict.13If the line that pointed you here also named a solution or workshop ("…and run14the X workshop for me"), treat that as the first request and start at once.1516There is one mode. The person never picks "with Brainstem" or "Copilot only";17you decide the engine yourself in the first minute (see "Pick the engine") and18never mention the choice unless they ask.1920## Public source2122- Repository: `microsoft/aibast-agents-library`23- Workshop branch: `main`24- Registry path: `registry.json`2526Resolve the branch through the GitHub API and pin one immutable commit SHA27before downloading anything.2829Persist the active run in `.aibast/easy-mode-state.json`, including solution,30revision, engine (`brainstem` or `copilot`), local test results, Copilot31Studio identity, status, and `published: false`. When the direct engine is32used, also persist the Copilot Studio plugin repository, installed plugin ID,33resolved revision or installed version, PAC CLI version, and verification34status.3536## Pick the engine (you, silently, in the first minute)3738Brainstem is the person's personal, on-device training AI. It works alongside39Copilot, remembers the workshop, and hot-loads specialized instructors while40Copilot remains the familiar work surface. Prefer it; fall back without fuss.41421. Check `http://localhost:7071/health`. If it answers, the engine is43 `brainstem`. Go to "Show it in VS Code".442. If it does not answer, start or install it yourself and wait up to two45 minutes for `/health`:46 - prefer `~/.copilot/bin/brainstem start`, then `brainstem` on the PATH47 - otherwise the public installer:48 Mac or Linux `curl -fsSL https://microsoft.github.io/aibast-agents-library/install.sh | bash`,49 Windows (PowerShell) `irm https://microsoft.github.io/aibast-agents-library/install.ps1 | iex`50 - if `/health` reports Copilot is not signed in, open51 `http://localhost:7071/login` for the person and say: "Sign in with your52 GitHub account, then tell me when you're done."533. If `/health` still does not answer (no permission to install, the port is54 held by something else, the installer failed), the engine is `copilot`.55 Record why in the state file in one line and continue. Never ask the56 person to fix it and never stop here.5758## Show it in VS Code (engine `brainstem`, when you are running in VS Code)5960Put the Brainstem's own folder in the Explorer so the person sees their AI as61files they own: run `code --add ~/.brainstem/src/rapp_brainstem` (Windows:62`code --add %USERPROFILE%\.brainstem\src\rapp_brainstem`), or the VS Code63command **Workspaces: Add Folder to Workspace** with that folder. Then open64`http://localhost:7071` in VS Code's built-in browser beside this chat: use65your open-browser tool if you have one, otherwise the VS Code command66**Simple Browser: Show** with that address. Say in one sentence: "This is your67Brainstem; `soul.md` is its personality and every `*_agent.py` in `agents/` is68a skill." Outside VS Code, open it in the person's normal browser instead.6970## Choose from the library7172When the user asks what is available, or asks for a workshop without naming73one (for example `Show me the AIBAST library, then give me the workshop I pick74using Easy Mode and test it for me`):75761. Fetch `registry.json` from the pinned commit.772. List every entry whose `_catalog_kind` is `solution`, grouped by78 `category` written as a plain industry name, one line per workshop:79 `display_name — description`. Do not paste JSON or file paths.803. Ask one question: which workshop they want. Accept a number, a name, or a81 description, resolve it to exactly one registry entry, and confirm the82 `display_name` back to them.834. Continue as `Give me <solution> using Easy Mode and test it for me` with84 that entry.8586Never choose for the user, and never download a workshop before they choose.8788## Build and test8990When the user says `Give me <solution> using Easy Mode and test it for me`:9192With engine `brainstem`:93941. Resolve `@aibast-agents-library/workshop` from the immutable registry.952. Download its exact `_file`, verify `_sha256`, and import it through96 `POST http://localhost:7071/agents/import`.973. Send the user's request to `POST http://localhost:7071/chat`.984. Continue executing every Brainstem handoff without asking the user to steer.995. Brainstem's generic workshop engine must discover the requested package,100 hot-load the business agent, and run every locked local case.101102With engine `copilot`:1031041. Run the repository-owned, fail-closed setup step105 `python3 tools/easy_mode_preflight.py --json` and require `passed: true`.106 Stop when it exits nonzero or reports `passed: false`, and report the107 remediation it printed. Record the installed plugin/version and PAC CLI108 version in `.aibast/easy-mode-state.json`.1092. Resolve the requested solution from immutable `registry.json`.1103. Fetch its `deployment.json`, `export-manifest.json`, portable `*_agent.py`,111 `tests/demo_cases/<slug>.json`, reviewed instructions, knowledge, skills,112 Copilot Studio source, and every tool named by the manifest.1134. Verify the portable source SHA.1145. Create an isolated workspace with only required files and BasicAgent.1156. Import the class named by `deployment.json`.1167. Execute every locked case with its operation and arguments.1178. Validate every `must_include` and `must_not_include` marker.118119Either way: persist `status: tested`, return the verdict with exact case120totals, and offer the next message:121`Deploy it into Copilot Studio for me.`122123## Required Copilot Studio plugin (engine `copilot`, before any deployment)124125The preflight owns plugin discovery, installation, and PAC remediation. Its126explicitly reviewed CLI sequence is:1271281. Check whether the `mcs-assistant` Copilot Studio capabilities are already129 available.1302. If they are missing, execute these GitHub Copilot plugin-manager commands131 in order:132133 ```bash134 copilot plugin marketplace add microsoft/copilot-studio-plugin135 copilot plugin install mcs-assistant@copilot-studio-plugin136 ```1371383. Recheck `copilot plugin list`, then resolve139 `microsoft/copilot-studio-plugin` through the GitHub API and record140 its immutable default-branch commit SHA or the installed plugin version in141 `.aibast/easy-mode-state.json`.1424. Inspect `pac --version`, including version output from a nonzero exit. The143 plugin requires a Power Platform CLI version newer than 2.9.3. When PAC is144 too old and .NET is available, run:145146 ```bash147 dotnet tool update --global Microsoft.PowerApps.CLI.Tool148 ```149150 Recheck PAC and otherwise stop with the reported remediation.1515. Verify the installed plugin exposes the Copilot Studio manage, describe,152 initialize, and architect capabilities. Do not continue to deployment when153 any required capability is unavailable.154155Use only `microsoft/copilot-studio-plugin` and the installed ID156`mcs-assistant@copilot-studio-plugin`. Do not substitute a fork or execute157unreviewed plugin source directly. The plugin is experimental, so validate all158generated YAML and stop on schema or PAC validation errors.159160## Deploy161162When the user says `Deploy it into Copilot Studio for me`:163164With engine `brainstem`:1651661. Send that exact request to Brainstem `/chat`.1672. Resolve `it` from Brainstem's persisted active workshop.1683. Continue every returned handoff.1694. Use the real Copilot Studio front door for Preview validation.1705. Return captured evidence to Brainstem using its callback schema.1716. Do not stop until Brainstem reports `status: complete`.172173With engine `copilot`:1741751. Resolve `it` from `.aibast/easy-mode-state.json`.1762. Re-verify `mcs-assistant@copilot-studio-plugin`, its recorded revision or177 version, and the required PAC CLI version.1783. Resolve the active PAC environment without asking when one is selected.1794. Use the plugin's read-only describer for an existing agent and its180 deterministic initializer only when a new target project is required.1815. Use the plugin architect to assemble or migrate the exact reviewed182 instructions, knowledge, skills, model, and modern agentic-loop YAML.1836. If the recorded schema exists, use the plugin manager to clone and184 reconnect automatically, then pull and reconcile it.1857. Remove web search and unapproved tools, then validate the generated source186 and PAC project before any remote write.1878. Use the plugin manager to push the Draft. Never invoke publish.1889. Open the real Draft and run every locked case in a fresh Preview chat.18910. Validate all markers and capture evidence.190191Either way: persist `status: complete` and report exact totals, the engine192used, plugin provenance when the direct engine deployed, and193`published: false`.194195## Rules196197- Own all terminal, file, PAC CLI, browser, and evidence work.198- Never ask the user for URLs, environment IDs, commands, or test markers.199- Never ask the user to choose an engine, a lane, or a mode.200- Never mix assets from different Git revisions.201- Never deploy through the direct engine without the verified Microsoft202 Copilot Studio plugin and supported PAC CLI.203- Never invent a missing result or success-shaped fallback.204- Never retry until a response happens to pass.205- Stop at Draft. Never publish.