extend-toolset

Create forged tools, connect MCP servers, and chain tool calls in one script.

33|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/infinition/LaRuche --skill extend-toolset-infinition
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extend-toolset
Source: https://github.com/infinition/LaRuche/tree/main/laruche/skills/extend-toolset
Command: npx skills add https://github.com/infinition/LaRuche --skill extend-toolset-infinition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI agent lacks a needed capability, it is easy to pick the wrong extension mechanism or create duplicates of tools that already exist. This Skill guides you to the right approach—Forged Tool, MCP server, run_script chaining, or a skill—and walks through creating and verifying each one correctly. ## Core Features & Use Cases - Forged Tool Creation: Build a new capability as a folder containing a tool.json manifest and a backing script, with a shell command template using {{slots}} and a JSON Schema for arguments. - MCP Server Integration: Connect external MCP servers with mcp_add, activate them with reload_mcp, and browse their resources via list_mcp_resources and read_mcp_resource. - Tool Chaining: Run sequences of existing tools in a single turn with run_script, injecting step outputs into later arguments via {{N}} placeholders. - Use Case: You need a weather lookup capability that does not exist. After confirming with tool_search that nothing similar is registered, you create a Forged Tool with a Python script, verify it through tool_call, and it becomes callable immediately in the same mission. ## Quick Start Create a new tool that runs a Python script to fetch weather data for a given city, then verify it works by calling it with a real city name.

Frequently Asked Questions about extend-toolset

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

FAQPage Schema
How do I create a new tool for an AI agent?▼

Use forged_tool_create with a name, description, command template, and JSON Schema. It writes a tool.json manifest and backing script into forged_tools/<name>/ and loads the tool into the live registry immediately, making it callable via tool_call in the same mission.

How do I connect an MCP server to my agent?▼

Run mcp_add with the server name and command, then run reload_mcp, which is mandatory because mcp_add only writes configuration. Confirm with mcp_list and use list_mcp_resources to see what the server exposes before reading any resource.

Why does my new tool not appear in the tool list?▼

The tool list is frozen when the mission starts to keep the cached prompt prefix stable, so newly created tools never appear mid-mission. Verify the tool with tool_search and call it through tool_call instead; it will be listed normally in the next mission.

When should I use run_script instead of separate tool calls?▼

Use run_script when a later step's arguments are fully determined by an earlier step's output, injected as {{N}} placeholders. Avoid it when you need to read intermediate results and make a judgement, since that decision requires a normal turn.

Why does my forged tool run with empty arguments?▼

The slot names in the command template do not match the property names in the JSON Schema. They must match character for character, otherwise the placeholder is never filled and the command runs malformed.