tool-advisor — Claude Code plugin: what it does, how to install
tool-advisor reads your MCP servers, skills, plugins and CLI tools, then offers up to three ranked ways to finish the task, each with commands you can copy.
MIT ★ 1,596 updated 2026-10-29
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install tool-advisor@awesome-codex-pluginsWhat tool-advisor does
It activates when the prompt names tool-advisor or asks which tool to reach for. Then it walks the live runtime: MCP servers, skills, plugins, command-line utilities. Your task gets profiled, including the finish line taken from your own wording, and checked against what is actually installed.
You get up to three routes: methodical, fast, deep. A Quick Action table follows with copy-paste steps. The plugin stays advisory — nine hard boundaries in its rules stop it from sliding into execution, and nothing is installed without your approval. Tools you lack are listed as gaps, with a note that the work can still be done without them. Short asks get a short answer, under ten lines.
Runs on the Claude Code CLI or Codex CLI. With no agent CLI running there is nothing to scan, since the inventory comes from the live session.
What it helps with
- see which MCP servers and skills are already in the project
- pick a fast or methodical route for a large refactor
- get runnable commands instead of a vague recommendation
- spot missing tools before the work starts
- write down the done criteria before touching code
Example prompts for the agent
- tool-advisor, how should I approach the database migration?
- Analyze with tool-advisor: move the auth module to JWT
- Which of my installed tools fit a rewrite of the payments service?
How to install tool-advisor
Plugin marketplace
/plugin marketplace add hashgraph-online/awesome-codex-plugins/plugin install tool-advisor@awesome-codex-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about tool-advisor
How do I install tool-advisor in Claude Code?
Add the marketplace first: /plugin marketplace add hashgraph-online/awesome-codex-plugins. Then install the plugin itself: /plugin install tool-advisor@awesome-codex-plugins.
What does tool-advisor do?
It scans your MCP servers, skills, plugins and CLI tools, profiles the task, and suggests up to three approaches with copy-paste commands. The suggestions are options, not orders.
Does tool-advisor work with Codex?
Yes, it supports Codex alongside Claude. You need the matching CLI, because the plugin builds its tool list from the running session.
Source text
claude-skills · MIT
# 🧭 Tool Advisor
**English** | [한국어](./README.ko.md) | [日本語](./README.ja.md) | [中文](./README.zh-CN.md) | [Español](./README.es.md) | [Português](./README.pt-BR.md) | [Русский](./README.ru.md) | [Français](./README.fr.md) | [Deutsch](./README.de.md)
**Discover your tool environment. Amplify your capabilities. (Claude Code + Codex)**
Tool Advisor scans your runtime environment — MCP servers, skills, plugins, CLI tools — and suggests optimal tool compositions as **non-binding options** with copy-paste commands. It arms the model with knowledge it wouldn't otherwise have.

## Install
**Option 1: One-line install (default: Claude Code + Codex)**
```bash
curl -fsSL https://raw.githubusercontent.com/dragon1086/claude-skills/main/install.sh | bash
```
Install for a single agent:
```bash
# Codex only
curl -fsSL https://raw.githubusercontent.com/dragon1086/claude-skills/main/install.sh | bash -s -- --agent codex
# Claude Code only
curl -fsSL https://raw.githubusercontent.com/dragon1086/claude-skills/main/install.sh | bash -s -- --agent claude-code
```
**Option 2: Via [skills.sh](https://skills.sh)**
```bash
npx skills add dragon1086/claude-skills -y --agent claude-code
npx skills add dragon1086/claude-skills -y --agent codex
```
To update, run the same command again.
## Usage
Just ask naturally:
```
"Analyze with tool-advisor: refactor the auth module"
"tool-advisor, how should I tackle this database migration?"
"What's the best approach for implementing user authentication?"
"Use $tool-advisor to analyze this task: ship v2 API migration"
```
The skill activates when you mention **tool-advisor** or ask for tool recommendations.
## What It Does
```
Your Prompt
↓
┌──────────────────────────────────┐
│ Tool Advisor v3.4 │
│ "Amplifier, not Commander" │
├──────────────────────────────────┤
│ 1. Discover Environment │
│ MCP / Skills / Plugins / CLI │
│ 2. Analyze Task + Done When │
│ 3. Match Capabilities │
│ 4. Suggest Options (up to 3) │
│ 5. Identify Gaps │
│ 6. Performance Tips │
└──────────────────────────────────┘
↓
Options + Quick Action table
```
## Features
| Feature | Description |
|---------|-------------|
| **4-Layer Environment Scan** | Discovers MCP servers, skills, plugins, and CLI tools at runtime |
| **Completion Criteria** | Extracts "Done when" from prompts so the model knows the finish line |
| **Scale-Adaptive Output** | Small tasks get <10 lines; large tasks get full analysis |
| **Multi-Option Suggestions** | Up to 3 approaches (Methodical / Fast / Deep) — never mandates |
| **Capability Gap Analysis** | Suggests missing tools with "doable without these" disclaimer |
| **Iron Rules & Anti-Patterns** | 9 hard boundaries prevent advisor-to-executor drift; 3 concise anti-patterns |
| **Phase Enforcement** | Every phase MUST produce output or explicit "N/A" — no skipping allowed |
| **Human-in-the-loop** | Never installs without your approval |
## Example
**Input:**
```
Analyze with tool-advisor: Refactor auth module to use JWT tokens
```
**Output:**
```markdown
## Tool Advisor v3.4 — Environment & Composition Analysis
Prompt: `Refactor auth module to use JWT tokens`
### Your Environment
| Layer | Available |
|-------|-----------|
| MCP Servers | lsp, context7 |
| Skills | /feature-dev, /code-review, /tdd |
| Plugins | oh-my-claudecode (33 agents) |
| CLI | git, node, pytest, docker |
### Task Profile
- **Type**: Modification / **Scale**: Large / **Traits**: Needs planning, has tests
- **Done when**: all session-based auth replaced with JWT, tests pass, no session imports remain
### Relevant Capabilities
- `lsp_diagnostics` — Type-check after changes
- `ast_grep_search` — Find all session usage patterns
- `/feature-dev` — Guided development workflow
### Suggested Approaches
**A — Methodical** (Recommended)
Task(Explore) -> EnterPlanMode -> Edit in stages -> Bash(pytest)
**B — Skill-guided**
/feature-dev (handles the full flow)
**C — Agent-parallel**
[Task(Explore, bg), WebSearch("JWT best practices")] -> plan -> implement
---
## Quick Action
| Approach | Copy & Paste |
|----------|--------------|
| Methodical | Start with `Task(Explore)` to scout the codebase |
| Skill-guided | `/feature-dev` then describe the refactoring |
| Fast | `Glob("**/auth/**") + Grep("session")` parallel |
-> Recommended: "Methodical" (large refactoring benefits from planning first)
```
## Requirements
- Claude Code CLI and/or Codex CLI
## License
MIT © 2026 dragon1086
© dragon1086 · MIT · hashgraph-online/awesome-codex-plugins