discovery-add-agentslisted

Cross-domain / Research platform engineering — Add agents from the public microsoft/discovery GitHub repository to a workspace, then deploy each selected agent to exactly one target: (a) the local Copilot app, emitting a `.github/agents/<name>.agent.md` companion invocable via `runSubagent`; (b) a Microsoft Discovery project plus Azure via `UpsertAgent`, binding existing tool ARM resources or building and registering missing ones; or (c) promoting an already-local agent up to a Discovery project without re-fetching upstream. USE FOR: 'add the discovery agents', 'download discovery agents', 'install all Microsoft discovery agents', 'add agents from microsoft/discovery', 'create copilot agents from microsoft/discovery', 'deploy discovery agents to Foundry', 'deploy discovery agents to Azure', 'promote a local agent to Microsoft Discovery'. DO NOT USE FOR: running a deployed agent (use runSubagent), or editing one agent's prompt (edit `agent.yaml`).
timothymeyers/discovery-tools · ★ 1 · AI & Automation · score 70

Install: claude install-skill timothymeyers/discovery-tools

# add-agent-from-catalog Add agents from the public `microsoft/discovery` repository to this workspace, then deploy each selected agent to exactly one of two targets: - **Local Copilot** - emit a `.github/agents/<name>.agent.md` companion for every agent so it can be invoked as a Copilot subagent via `runSubagent`. Tool container images are built lazily on first invocation, locally only. - **Microsoft Discovery + Azure** - pre-flight every tool the agent declares via `GetDiscoveryTool` against the workspace's RG. When a tool ARM resource already exists (common for shared catalog images on shared registries), skip Docker build / ACR push / AcrPull RBAC entirely and bind the existing ARM ID. When a tool is missing, build + push via `az acr build`, register the tool ARM, grant AcrPull. Either way, create the agent in the target Discovery project via `UpsertAgent` and poll **`GetAgent`** until `provisioningState=Succeeded`. Local Discovery runtime registration (`agents action=create`) is optional and skipped by default. - **Local app → Microsoft Discovery + Azure (promote)** - take an agent that is **already added to the local Copilot app** (present under `discovery_catalog/<name>/` with a `.github/agents/<name>.agent.md` companion and, for tool-bearing agents, a locally-built container image) and register it in a specific Discovery project. The **local** folder is the source of truth - the upstream `microsoft/discovery` repo is **not** fetched