ワンクリックで
evaluate-tool
Evaluate an AI tool, skill, or plugin against the catalog and dev loop quality signals before adopting it
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Evaluate an AI tool, skill, or plugin against the catalog and dev loop quality signals before adopting it
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Find tools that probably belong in CATALOG.md but aren't there, via referenced-but-not-catalogued detection + a foundational-tools checklist. Use to audit the catalog for missing heavyweight tools. Triggers - "find catalog gaps", "what's missing from the catalog", "audit catalog completeness".
Add a tool to CATALOG.md + COMPARISON.md and propagate all counts, then sync and audit. Use when adding a single catalogued tool by its GitHub slug. Triggers - "add X to the catalog", "catalog this repo", "/add-catalog-entry owner/repo".
Bootstrap the recommended AI workflow in any repo — checks what's installed, creates CLAUDE.md with quality rules, and identifies gaps
Bootstrap the recommended AI workflow in any repo — checks what's installed, creates CLAUDE.md with quality rules, and identifies gaps
Audit your current AI tool setup against the recommended dev loop workflow and identify gaps
Evaluate an AI tool, skill, or plugin against the catalog and dev loop quality signals before adopting it
| name | evaluate-tool |
| description | Evaluate an AI tool, skill, or plugin against the catalog and dev loop quality signals before adopting it |
Evaluate a new AI tool before adding it to your workflow. Prevents tool sprawl by checking for overlap and assessing fit against the five quality signals.
/evaluate-tool <repo-url-or-name>
Fetch the repo description and README:
gh api repos/{owner}/{repo} --jq '.description'
gh api repos/{owner}/{repo}/readme --jq '.content' | base64 -d | head -100
Determine:
Read the catalog at CATALOG.md and find entries in the same category. For each overlapping tool:
Read WORKFLOW.md. Determine:
Check: does the user's current setup already have strong coverage for this stage and signal? Adding a third code review tool when Review is already well-covered is lower value than filling a gap in Verify or Integrate.
Output a structured evaluation:
## Tool Evaluation: {name}
**What it does:** {one-liner}
**Problem it solves:** {pain point}
**Type:** {type}
**Category:** {category}
**Dev loop stage:** {stage}
**Quality signals:** {signals}
### Overlap Analysis
{list overlapping tools from catalog, with comparison}
### Recommendation
- **ADOPT** — fills a gap in the current workflow
- **REPLACE {x}** — better than current tool for this problem
- **SKIP** — overlaps with {x} which is already in the workflow
- **DEFER** — relevant but current setup has higher-priority gaps elsewhere
### Catalog Entry (if adopting)
{pre-filled table row for CATALOG.md}
If the recommendation is ADOPT or REPLACE, offer to add the entry to CATALOG.md and update WORKFLOW.md.