Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

jonnybottles

@jonnybottles source repo

8 published skills

  1. ▌
    Copilot Studio Agent · jonnybottles bundle
    Create, edit, publish, and manage Microsoft Copilot Studio agents entirely from the command line using the Power Platform CLI (`pac copilot`) plus the Dataverse Web API, with no Copilot Studio web UI and no browser automation. Covers scaffolding a live agent in one step, cloning an existing agent to a local YAML workspace, the pull/push sync loop, publishing, controlling authentication mode and access control, verifying that an agent is private to its owner, and testing an agent conversationally via Direct Line or the authenticated Copilot Studio conversation API. Use whenever the user asks to create a Copilot Studio agent, build an agent from the CLI, clone/edit/push/publish an agent, change agent auth or sharing, script agent creation, or test a Copilot Studio agent. Triggers: create copilot studio agent, pac copilot, copilot studio cli, agent as code, clone agent, push agent, publish agent, copilot studio yaml, agent definition, copilot studio automation, share agent, private agent.
    0 installs
  2. ▌
    Copilot Studio MCP Tool · jonnybottles bundle
    Attach a remote MCP (Model Context Protocol) server to a Microsoft Copilot Studio agent entirely from the command line - no Copilot Studio web UI, no browser automation. Covers authoring the OpenAPI/swagger definition with x-ms-agentic-protocol mcp-streamable-1.0, creating the Power Platform custom connector with `pac connector create`, creating a no-auth connection via the Power Apps REST API, creating the required Dataverse connectionreference row, and writing the TaskDialog / InvokeExternalAgentTaskAction / ModelContextProtocolMetadata action YAML into the agent workspace so `pac copilot push` succeeds. Also covers restricting which MCP tools the agent may call. Use when the user wants to add an MCP server or MCP tool to a Copilot Studio agent, wire up a custom MCP connector, or script MCP tool onboarding. Triggers: add mcp server to copilot studio, mcp tool copilot studio, mcp custom connector, x-ms-agentic-protocol, copilot studio mcp, streamable mcp connector.
    0 installs
  3. ▌
    Copilot Studio Agent Flow · jonnybottles
    Create, attach, troubleshoot, and verify Copilot Studio agent flows from the CLI and APIs. Use this skill whenever the user asks for an agent flow, "When an agent calls the flow", Power Automate tool, InvokeFlowTaskAction, AI Builder action, flow input/output, or a flow that writes to Dataverse - even if they do not name the skill. Covers solution-aware workflow clientdata, embedded connector bindings, Maker-mode tools, publishing, and proof that the flow actually ran.
    0 installs
  4. ▌
    Copilot Studio Agent Test · jonnybottles bundle
    Verify a Microsoft Copilot Studio agent actually works at runtime by holding a real conversation with it from the terminal, and prove that a specific tool (MCP server, connector, or knowledge source) genuinely fired rather than the model answering from its own knowledge. Generates a ready-to-run Node test script that performs an Entra ID device-code sign-in and talks to the authenticated Copilot Studio conversation API via Microsoft's official agents-copilotstudio- client, including the one-time app registration that grants CopilotStudio.Copilots.Invoke. Also diagnoses common failure modes: connection-manager blocking, Integrated-auth channel errors, and empty responses. Use when the user wants to test, verify, smoke-test or chat with a Copilot Studio agent from the CLI, confirm a tool is being called, or debug an agent that returns nothing. Triggers: test my copilot studio agent, did the tool fire, agent returns nothing, smoke test agent.
    0 installs
  5. ▌
    Power Platform Solution Alm · jonnybottles
    Create and package Power Platform solutions from CLI/API tooling. Use this skill whenever the user asks for a publisher, unmanaged solution, managed solution, solution component membership, pac solution export/import, ALM packaging, connection references, Dataverse tables/flows/agents in one solution, or deployment artifacts - even if they do not name the skill. Covers component type IDs, export verification, and safe managed-vs-unmanaged guidance.
    0 installs
  6. ▌
    Copilot Studio Headless Test · jonnybottles
    Test Copilot Studio agents from the terminal or authenticated portal and prove a tool really fired. Use this skill whenever the user asks to test, smoke-test, invoke, or debug an agent; verify a flow/connector/MCP tool call; diagnose plausible but false agent answers; handle CopilotStudio.Copilots.Invoke device-code auth; or inspect flow runs and Dataverse side effects - even if they do not name the skill. Includes a Playwright fallback for unattended CLI authentication.
    0 installs
  7. ▌
    Dataverse Flow Create Record · jonnybottles
    Build and debug Power Automate Dataverse CreateRecord/Add a new row actions from table metadata. Use this skill whenever a flow must create a Dataverse row, map custom columns, use entityName, fix "Invalid property" OData errors, handle Boolean/date/decimal fields, or translate display/schema names into connector parameters - even if the user does not name the skill. Enforces exact entity-set names and lowercase logical column names.
    0 installs
  8. ▌
    Copilot Studio Connected Agent · jonnybottles bundle
    Wire one Microsoft Copilot Studio agent to another as a connected agent (multi-agent / agent-to- agent orchestration) from the command line - no Copilot Studio web UI, no browser automation. Covers the InvokeConnectedAgentTaskAction tool YAML, child-first build order, referencing a connected agent from the parent agent's instructions, passing inputs and outputs across the agent boundary with inputType / outputType and global variables, and pac CLI quirks that mangle or over-length component schema names. Leads with the AgentpluginActionNoOutputSetInEmitMode failure seen when a connected-agent tool is left in emit mode with no declared outputs. Use when the user wants an agent to call another agent, build a parent/orchestrator agent, add a connected or child agent, or debug an agent-calls-agent error. Triggers: connected agent copilot studio, multi agent copilot studio, orchestrator agent, InvokeConnectedAgentTaskAction, NoOutputSetInEmitMode, botSchemaName.
    0 installs