Agent Skills › siddsachar/row-bot › custom_tool_builder_guide

custom_tool_builder_guide

GitHub

指导如何将 GitHub 仓库或本地文件夹转化为可复用的 Row-Bot 自定义工具。涵盖从克隆、配置依赖、测试到创建和发布的完整生命周期管理，确保操作安全与自动化。

tool_guides/custom_tool_builder_guide/SKILL.md siddsachar/row-bot

Trigger Scenarios

用户要求将项目或仓库打包为工具需要调整或测试现有自定义工具

Install

npx skills add siddsachar/row-bot --skill custom_tool_builder_guide -g -y

More Options

Non-standard path

npx skills add https://github.com/siddsachar/row-bot/tree/main/tool_guides/custom_tool_builder_guide -g -y

Use without installing

npx skills use siddsachar/row-bot@custom_tool_builder_guide

指定 Agent (Claude Code)

npx skills add siddsachar/row-bot --skill custom_tool_builder_guide -a claude-code -g -y

安装 repo 全部 skill

npx skills add siddsachar/row-bot --all -g -y

预览 repo 内 skill

npx skills add siddsachar/row-bot --list

SKILL.md

Frontmatter

{
    "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"
}

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, pass fields={"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 .venv and install dependencies there.
Use action="create" only after the user accepts the draft.
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.