agent-tool
Skill0 starsChanged 12 days agoMITView on GitHub
Give a Copilot Studio agent a new capability by building a Power Automate flow it can call, plugging it in as a tool, updating the agent's instructions to use it, and publishing. Use when asked to add a tool, action or flow to an agent, connect an agent to data, update an agent's instructions, or "make the agent able to ...".
In this repository4 other files it gives its agents.
- build-flowSkill
- dataverse-schemaSkill
- debug-flowSkill
- solution-from-baseSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Start from demo-agent-flow.json.
- Very specific: line 34
Prove it: Ask the user to try one question in the test pane that should trigger the tool, then list_runs on the flow: a run means the agent …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Give an agent a tool it can call
Uses the power-platform-copilot server (copilot_studio.py). The loop, in order:
- Find the agent.
list_agents, thenget_agenton it. Read its current instructions and tools aloud before changing anything; keep them for the undo. - Build the flow as an AGENT flow.
create_agent_flow, notcreate_flow. Copilot Studio only calls solution flows, andcreate_flowmakes a My flows flow the agent cannot reach. The definition needs:- trigger
{"type": "Request", "kind": "Skills"}, inputs ininputs.schema.properties, each with adescriptionthe agent will read to fill it; - a
{"type": "Response", "kind": "Skills"}action ("Respond to the agent"), outputs ininputs.schema.properties, values ininputs.body. Start fromdemo-agent-flow.json. Keep it under 100 seconds: the agent waits for it. Passsolutionto keep the flow with the agent's solution for export.
- trigger
- Plug it in.
add_flow_toolwith adescriptionthat says what the tool does, what it needs and what it returns. That sentence is how the agent decides when to call it: write it like a brief to a colleague, not a label. - Tell the agent.
update_agent_instructionswith the COMPLETE new text: when to call the tool, how to phrase the answer, what language. Name the tool by its display name. No{or}(the tool refuses them; Copilot Studio parses them as Power Fx). - Publish.
publish_agent. OnlySucceededmeans live. The Copilot Studio test pane sees drafts before that; Teams and Microsoft 365 Copilot do not. - Prove it. Ask the user to try one question in the test pane that should trigger
the tool, then
list_runson the flow: a run means the agent called it, andexplain_runshows what it sent and got back. No run means the agent did not choose the tool - sharpen the tool description or the instructions, not the flow.
Undo
update_agent_instructions returns previous_instructions. A tool is a component of
the agent: remove it in Copilot Studio (Tools, the tool, Delete), or ask before deleting
it any other way. delete_flow (extras) removes the flow.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

