Dynamic Tool

Intent-based tool selection. Activate when you want to know which tools are relevant for the current user message (weather→exec, document→feishu_doc, search→...

Security Scan

The skill's code and instructions are consistent with its stated purpose (keyword-based tool recommendation), but it includes guidance that could lead to risky gateway modifications and always recommends the exec tool — review and limit any changes before applying.

Purpose & Capability

Name/description match the implementation: index.js implements keyword-to-tool mapping and exposes get_recommended_tools which returns recommended_tools and a hint. No unrelated env vars, binaries, or credentials are required.

Instruction Scope

SKILL.md/README stay within purpose (call get_recommended_tools with the last user message) but also recommend: (1) specific system-prompt rules, and (2) optionally patching the OpenClaw distribution (auth-profiles-*.js) to perform gateway-level filtering. The README's recommendation to patch core gateway files is potentially risky and should be reviewed carefully. Also, the implementation unconditionally includes 'exec' in every recommendation, which may cause the agent to prefer running shell commands; ensure exec tool restrictions/policies are in place.

Install Mechanism

No install spec; skill is instruction + small JS module. Nothing is downloaded from external URLs and there are no install-time scripts, so no high-risk installation behavior is present in the package itself.

Credentials

No environment variables, credentials, or config paths are requested. The skill does not require secrets or unrelated service tokens.

Persistence & Privilege

The skill does not request always:true and is user-invocable only. However, README suggests modifying gateway-level code to enforce filtering — that change would grant persistent behavior to the gateway and should be treated as a privileged modification (backup and review recommended).

Assessment

This skill appears to do what it says: keyword-based recommendations for which tools to expose. Before installing or applying its suggestions: 1) Be cautious about following the README's 'gateway-level filtering' advice — it proposes patching OpenClaw distribution files (auth-profiles-*.js). Back up those files and review any code you paste into core bundles. 2) Note that the implementation always includes the 'exec' tool in recommendations; ensure your exec tool is safely sandboxed or disabled if you don't want agents running shell commands. 3) Verify and inspect any external links or code snippets (the README references a GitHub path that looks like a placeholder). 4) If you plan to apply the gateway patch, restrict who can perform that change and test in a non-production environment. If you want a lower-risk approach, use the skill's get_recommended_tools output in your agent logic without modifying core OpenClaw files.

Dynamic Tool Policy

When to use: Before calling many tools, or when the user message is about weather, search, documents, or Feishu — call get_recommended_tools with the latest user message to get a short list of recommended tools and a hint.

Intent mapping:

• 天气 / weather / wttr → use exec (e.g. curl wttr.in/<city>?format=3)
• 搜索 / search → use web_search once, then reply; do not call web_search again in the same turn
• 文档 / create doc / 飞书文档 → use feishu_doc only when the user explicitly asks for a document
• 读文件 / read file → read; 写/编辑 → write

Tool: get_recommended_tools({ user_message }) → returns recommended_tools (array of tool names) and hint (short instruction).