Agent Skills › siddsachar/row-bot › developer_custom_tools

developer_custom_tools

GitHub

用于在 Developer Studio 中创建、测试、启用和推广自定义工具的工作流。支持将 GitHub 仓库或本地文件夹转化为可复用的 Custom Tool，涵盖从草稿生成、命令确认到最终发布的全生命周期管理。

bundled_skills/developer_custom_tools/SKILL.md siddsachar/row-bot

触发场景

用户要求将 GitHub 仓库添加为工具用户要求将本地文件夹转换为 Custom Tool 用户要求在当前工作区创建可复用工具

安装

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

更多选项

非标准路径

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

不安装直接使用

npx skills use siddsachar/row-bot@developer_custom_tools

指定 Agent (Claude Code)

npx skills add siddsachar/row-bot --skill developer_custom_tools -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": "developer_custom_tools",
    "tags": [
        "developer",
        "tools"
    ],
    "tools": [
        "developer"
    ],
    "author": "Row-Bot",
    "version": "1.0",
    "description": "Workflow for creating, testing, enabling, promoting, and removing Custom Tools from Developer Studio.",
    "display_name": "Developer Custom Tools",
    "enabled_by_default": false
}

Developer Custom Tools

Use this skill when the user asks to add a GitHub repo, local folder, or current workspace as a reusable Row-Bot Custom Tool.

The user can ask in natural language. Treat requests like "make this repo a tool", "add this GitHub repo as a Custom Tool", or "turn this folder into a tool" as Custom Tool creation requests.

Workflow:

Confirm the source: repo URL, local folder, or current workspace. For repo URLs, ask for an explicit clone parent folder if one is not already provided.
Start a draft with custom_tool_builder action start when that utility is enabled. It performs a compact repo scan plus one AI proposal pass, then validates the proposed commands.
Explain the draft commands in plain language. Do not ask the user to hand-write internal config files.
Refine the draft with action refine when the user asks for changes, or action update for a direct command/metadata edit.
Public repo Custom Tools require explicit user enablement of public repo tools before creation. Do not silently enable that gate.
Create only after the user accepts the proposed commands. Use action create.
Test at least one command with action test before enabling or promotion.
Enable Developer use with action enable when the user wants it active in Developer.
Promote with action promote only when the user wants the tool available in normal chat/plugin tools.
If removing a draft or Custom Tool, use action delete and preserve the source folder unless the user explicitly asks to delete files.

Be clear about scope: a Custom Tool starts as Developer-managed metadata around an existing repo/folder; promotion makes it appear in Settings -> Plugins and normal chat tools.