tool-radarlisted
Install: claude install-skill SVN11X/skills
# tool-radar
Turn a tool someone found into a recorded decision. Judge it with evidence, not with the post that announced it.
## Evaluate
1. Check that it exists. For a GitHub project, `git ls-remote https://github.com/<owner>/<repo>` and read its README and LICENSE. If you cannot open the source, say so and stop guessing.
2. Write down what it really does, in one or two sentences from the README, not from the announcement.
3. Record the license, the cost, and what leaves the machine (privacy).
4. Compare it with the radar entries in `<standard>/radar/radar.yml` and with the tools the owner already uses. Name any overlap.
5. Decide which profiles it serves and, for interface tools, which `DESIGN.md` expression levels it fits: sober, balanced, expressive.
6. For an MCP server, list what it exposes before any decision with `python <standard>/scripts/orchestrate.py mcp inspect <name>` (it uses MCP Inspector), name the tools that write or reach outside the machine, and compare them with the tools the agents already have. Add it to `settings/mcp/catalog.yml` with an exact version, off by default, read-only when it can be.
7. Propose a status. Prototypes, single-maintainer projects and unsigned installers start at assess or trial. Anything that sends repository content to a provider, or acts on events from public repositories, needs an explicit warning.
## Record
- Show the owner the proposed entry and the reasoning in a few lines.
- After approval, add or update the entry in