Tutorials

The Copilot Studio ladder

Each rung turns RAPP agent.py files and SKILL.md skills into one published Copilot Studio agent on the GitHub Copilot harness, then proves it with real prompts. Every rung is reproducible from this repo alone, and every published agent keeps working with no RAPP brainstem behind it.

0
Skills only
Four SKILL.md files become skills on one agent. No connectors, no flows. Exported straight out of Copilot Studio.
proved 3/3
1
Starter with live tools
Hacker News, ManageMemory and ContextMemory agents run for real: a custom connector, an agent flow and two Dataverse tools.
proved 3/3
2
Live tools plus skills
Rung 1 plus two SKILL.md skills on the same agent, built and deployed by one call to a brainstem agent.
proved 5/5
3
Skills with scripts
Skills whose SKILL.md ships code: inline code runs in the harness sandbox, separate script files never ship.
proved 3/3
4
Two AIs, one routine
A briefing desk that delegates news and memory to rung 2's agent through a connected agent, and keeps one skill of its own.
proved 3/3
5
Thirty-four community skills
The whole coleam00/skills collection on one agent; routing holds, with one early sign of a width limit.
proved 5/5
6
Brainstem bridge
One connector that calls a hosted brainstem's /chat, so the agent gets every capability without porting any.
next

What every rung has in common

One build, one deploy. scripts/deploy-harness-agent.mjs imports a workspace as a solution, provisions connection references and flows, binds tools, publishes and verifies. The tutorial script adds the proven infrastructure profiles for agents that match them.
Proof, not a demo. A turns file of prompts and regular expressions is sent to the published agent over the SDK's copilot-studio-3p route (a delegated user token) and the answers are recorded. The proof files live next to each rung.
No brainstem at runtime. Once published, the agent is an ordinary Copilot Studio solution. The manual way imports the exported solution with pac alone.

Before you start

Need	Why
Node 20.19+ and `npm install` in this repo	the deploy, tutorial and proof scripts are plain Node
Power Platform CLI 2.10+ with `pac auth create --environment <url>`	solution import, publish, connector creation
Azure CLI signed in as the same user (`az login --tenant <tenant>`)	Dataverse bearer tokens; the user must be a member of the environment's tenant
A Copilot Studio environment with the GitHub Copilot harness enabled	every agent here is a `cliagent-1.0.0` harness agent, never a classic agent
For the proofs: a public-client Entra app with delegated `CopilotStudio.Copilots.Invoke`	the authenticated `/3p` route is the only one that runs connectors, flows and Dataverse tools from outside the Studio

Environment URLs, environment ids, tenant ids and app ids are placeholders in every page here: <org>, <env-id>, <tenant>, <client-id>. Put yours in a shell or a .env, never in a repo.