AGENT SKILL

custom_tool_builder_guide

Guidance for creating reusable Custom Tools from repos or folders.

License 许可
Apache-2.0
所属仓库
siddsachar/row-bot
最近更新
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:

  1. Start with action="start".
  2. For a repo URL, pass source_url. If the user gave a clone parent, pass fields={"clone_parent": "..."}. If no clone parent is known, ask for one.
  3. Show the proposed tool name, warnings, and commands before creating anything.
  4. Use action="refine" when the user asks to adjust commands or behavior.
  5. Use action="test" for a smoke test when requested.
  6. For Python repos with missing dependencies, use action="setup" to create/reuse the tool folder's .venv and install dependencies there.
  7. Use action="create" only after the user accepts the draft.
  8. Use action="enable" for Developer availability and action="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.json or internal config files.
  • Use custom_tool_builder for lifecycle state: clone/import source, draft, refine, create, enable, promote, delete.
  • Use custom_tool_builder action="setup" for Python dependency setup. Do not run pip install manually 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