developer_custom_tools

Automate converting a GitHub repo or folder into a Row-Bot Custom Tool.

1.4k|169|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/siddsachar/row-bot --skill developer-custom-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer_custom_tools
Source: https://github.com/siddsachar/row-bot/tree/main/bundled_skills/developer_custom_tools
Command: npx skills add https://github.com/siddsachar/row-bot --skill developer-custom-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps automate turning a GitHub repo, local folder, or current workspace into a reusable Row-Bot Custom Tool, reducing manual setup time and ensuring consistent tooling metadata.

Core Features & Use Cases

  • Create a draft Custom Tool from a repo or folder with minimal steps.
  • Validate and refine configurations through an interactive workflow before enabling or promoting the tool.
  • Manage lifecycle from creation to removal, including testing and promotion to normal tools.

Quick Start

Turn a GitHub repo, local folder, or current workspace into a reusable Custom Tool with the built-in builder.

Frequently Asked Questions about developer_custom_tools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a GitHub repo into a reusable custom tool?

To convert a GitHub repo into a reusable custom tool, the skill automates drafting, refining, and testing workflows. It turns repository code into structured tooling metadata through an interactive builder process.

Can I create custom tools from a local folder or current workspace?

Yes, you can create custom tools from a local folder or current workspace. The builder supports converting local development directories into reusable tools, enforcing explicit user decisions at each configuration gate.

What is the workflow for testing and promoting a draft custom tool?

The workflow for testing and promoting a draft custom tool involves validating configurations interactively before enabling. You test the draft tool and then promote it to a normal tool once refined and verified.

Does the custom tool builder safeguard public tools and sensitive data?

Yes, the custom tool builder safeguards public tools and sensitive data. It enforces explicit user decisions at each gate during the repository ownership and local development lifecycle to prevent accidental exposure.

How do I remove a custom tool after it has been promoted?

To remove a custom tool after it has been promoted, the skill manages the complete lifecycle from creation to removal. It guides you through the deletion workflow to safely retire the tool.