discovery-provision-toolslisted
Install: claude install-skill timothymeyers/discovery-tools
# discovery-provision-tools
## Modes
- **Proposal-only** (called by `discovery-project-setup` Step 5): return
`## Tools / agents / skills` ops and stop.
- **Standalone**: gather, propose, approve, apply using
`../discovery-project-setup/references/{gather-state,proposal-format,apply,git-ledger,retirement}.md`.
Ask questions as plain chat.
## 1. Collect needs
Read the tasks (especially `access-pending` labels), outcomes, and
`data/external-sources.md`. Build a needs list: "T7 needs read access to
ERCOT historian", "O2 needs AC power-flow solver".
Then ask (plain chat):
> Do you have agents, skills, or tools to bring in — local paths, URLs,
> GitHub repos, MCP servers, or remote (A2A) agents running elsewhere?
## 2. Identify user-supplied sources
See [references/source-types.md](references/source-types.md) for detection
and the recommended install for each type. For A2A agents see
[references/a2a.md](references/a2a.md).
## 3. Catalog review (run in parallel)
Run one subagent per catalog. Each returns at most 10 candidates, each with a
name, kind, path, commit SHA, a one-line purpose, and the need it serves.
| Catalog | Visibility | How |
|---|---|---|
| `microsoft/discovery` | public | Read `../discovery-add-agents/SKILL.md` and use its catalog listing in recommend-only mode (no deploy). |
| `timothymeyers/discovery-tools` | public | `gh api repos/timothymeyers/discovery-tools/git/trees/HEAD?recursive=1`, then read the candidate manifests (`SKILL.md`, `*.agent.md`,