AGENT SKILL
custom_tool_builder_guide
Guidance for creating reusable Custom Tools from repos or folders.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 1.7k
- Forks
- 204
01 前言 Front Matter
- icon
- extension
- name
- custom_tool_builder_guide
- tags
- [ "custom-tools", "developer" ]
- tools
- [ "custom_tool_builder" ]
- description
- Guidance for creating reusable Custom Tools from repos or folders.
- display_name
- Custom Tool Builder Guide
03 SKILL.md 正文
Custom Tool Builder Guide
Use custom_tool_builder when the user asks to turn a GitHub repo, local folder, or current project into a reusable Row-Bot Custom Tool.
Default flow:
- Start with
action="start". - For a repo URL, pass
source_url. If the user gave a clone parent, passfields={"clone_parent": "..."}. If no clone parent is known, ask for one. - Show the proposed tool name, warnings, and commands before creating anything.
- Use
action="refine"when the user asks to adjust commands or behavior. - Use
action="test"for a smoke test when requested. - For Python repos with missing dependencies, use
action="setup"to create/reuse the tool folder's.venvand install dependencies there. - Use
action="create"only after the user accepts the draft. - Use
action="enable"for Developer availability andaction="promote"only when the user explicitly wants it available in normal chat/workflows.
Rules:
- Do not ask the user to hand-write
row-bot-custom-tool.jsonor internal config files. - Use
custom_tool_builderfor lifecycle state: clone/import source, draft, refine, create, enable, promote, delete. - Use
custom_tool_builder action="setup"for Python dependency setup. Do not runpip installmanually in Row-Bot's own Python environment. - Shell can help with extra read-only inspection or explicit user-approved command testing when the builder needs more evidence.
- Do not use shell to manually register, enable, promote, delete, or edit Custom Tool metadata.
- Public repo Custom Tools do not have a separate hidden enablement gate. Safety comes from explicit clone destination, command review, test approval/sandboxing, and the separate enable/promote steps.
- Explain that generated commands usually operate on the cloned/local repo files unless a command is clearly network-enabled.
- Removing a Custom Tool should preserve source files unless the user explicitly asks to delete managed files.
04 同仓库更多 Skills
x_guide
Essential guidance for using X (Twitter) tools correctly — search syntax, time filtering, and engagement patterns.
★ 1.7k
workflow_guide
How workflows run (scheduled chats), how to write and change them, hand work between them, and check what a run did.
★ 1.7k
wiki_guide
Guidance for the Obsidian-compatible wiki vault.
★ 1.7k
weather_guide
Guidance for using weather tools effectively.
★ 1.7k
vision_guide
Guidance for using webcam, screen capture, and image analysis.
★ 1.7k
video_guide
Guidance for generating videos and animating images.
★ 1.7k