tool-finder

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Tool Finder

This skill is coordination-exempt: skip the ai-coord gate for its declared work.

Recommend the current option that best fits the user's actual constraints, backed by fresh primary evidence.

这个Skill无需协调：在执行其指定任务时跳过ai-coord校验。

推荐最符合用户实际限制条件的当前适用选项，并提供最新的一手证据支持。

Workflow

Infer the ecosystem, existing stack, must-haves, switching cost, and decision criteria from the request and repository. Ask only when an unknown would materially change the recommendation.
Check whether the standard library, platform, or an already-installed tool is sufficient before adding a dependency.
Search current authoritative sources. Read references/tool-finder.md only for the relevant ecosystem's source routing, fallback criteria, install conventions, and red flags.
Compare the viable options against the user's criteria. Use adoption, maintenance, security, documentation, performance, operational cost, and ecosystem fit only where they affect this decision; do not force fixed weights or a fixed number of candidates.
Recommend one option when the evidence supports it. State the decisive tradeoff, material red flags, and the closest alternative. Say when the evidence is too close or no external tool is justified.

从用户请求和代码仓库中推断技术生态、现有技术栈、必备需求、切换成本以及决策标准。仅当某个未知因素会实质性改变推荐结果时才向用户提问。
在添加新依赖前，先检查标准库、平台或已安装的工具是否足以满足需求。
搜索当前权威来源。仅在需要了解相关生态的来源路由、备选标准、安装惯例和警示信号时，才阅读references/tool-finder.md。
将可行选项与用户的标准进行对比。仅在这些因素会影响决策时，才考虑采用率、维护情况、安全性、文档、性能、运营成本和生态适配性；不要强行设定固定权重或固定数量的候选选项。
当证据充分时推荐一个选项。说明决定性的权衡因素、重大警示信号以及最接近的替代方案。当证据不分伯仲或无需外部工具时，也要明确说明。

Defaults

With no repository evidence, default to JavaScript/TypeScript and Node.js tooling.
For JavaScript installs, prefer the repository's package manager and otherwise
```
ni
```
; for macOS CLIs, prefer an official or well-maintained Homebrew formula.
Prefer registries, official docs, repositories, changelogs, and security advisories over secondary comparisons. For agent skills, search registries and GitHub because no single index is complete.

在没有代码仓库证据的情况下，默认采用JavaScript/TypeScript和Node.js工具链。
对于JavaScript安装，优先使用代码仓库的包管理器，否则使用
```
ni
```
；对于macOS CLI，优先选择官方或维护良好的Homebrew公式。
优先使用注册表、官方文档、代码仓库、变更日志和安全公告，而非二手对比内容。对于Agent技能，搜索注册表和GitHub，因为目前没有完整的单一索引。

Completion

The answer is complete when the recommendation is traceable to current sources, the deciding criteria are explicit, installation guidance matches the user's environment, and uncertainties or disqualifying risks are visible. Use a table only when repeated fields make the comparison easier to scan.

Lead with

### 🏆 Pick: <tool>

and the decisive reason. Follow with

### 📦 Install

and the exact command, a compact criteria/evidence table only when fields repeat,

### 🥈 Closest alternative

only for a credible material runner-up, and

### ⚠️ Caveats

only when material. Use symbols in comparison cells only with text; never manufacture scores. Keep URL targets exact and use descriptive Markdown links for human output. Keep install commands, versions, security advisories, and installer-risk wording exact and undecorated.

当推荐内容可追溯至当前来源、决策标准明确、安装指南匹配用户环境，且不确定性或排除性风险可见时，回答即完成。仅当重复字段较多、对比内容更易浏览时才使用表格。

以

### 🏆 Pick: <tool>

和决定性理由开头。接着是

### 📦 Install

和精确的命令；仅当字段重复时使用简洁的标准/证据表格；仅当存在可信的实质性备选方案时添加

### 🥈 Closest alternative

；仅当存在重大问题时添加

### ⚠️ Caveats

。对比单元格中仅在配有文字时使用符号；切勿编造分数。保持URL目标精确，为人工输出使用描述性Markdown链接。保持安装命令、版本、安全公告和安装器风险表述精确且无修饰。