skill-forge

Create, edit, and manage agent skills and bundled script tools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent solves a hard problem in a session, that solution is lost unless it is captured as a reusable procedure. This Skill provides the complete workflow for writing, editing, and deleting skills, and for turning one-off scripts into bundled or registered tools so solved problems stay solved. ## Core Features & Use Cases - Skill authoring workflow: Guides creation of skills with correct frontmatter, trigger-focused descriptions under 80 characters, and verifiable step-by-step bodies using skill_create, skill_view, and skill_list. - Safe editing and patching: Uses skill_patch with exact byte matching and skill_file_write for full rewrites, with failure-mode guidance for invisible whitespace and ambiguous fragments. - Script and tool forging: Defines a three-level escalation path from one-off scripts run via shell_exec, to scripts bundled under a skill's scripts/ folder, to registered Forged Tools callable on every turn. - Use Case: After manually debugging a tricky deployment, you write a skill documenting the fix with prerequisites and verification steps, bundle the diagnostic script under scripts/, and the next occurrence is resolved with a single skill invocation. ## Quick Start Ask the agent to create a new skill documenting the procedure you just completed, including prerequisites and verification steps.

Frequently Asked Questions about skill-forge

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

FAQPage Schema
How do I create a new agent skill?▼

Call skill_list first to check for overlaps, then call skill_create with a lowercase hyphenated name, a description under 80 characters starting with a verb, and a markdown body with prerequisites and numbered verifiable steps. Confirm with skill_view afterward.

How do I write a good skill description?▼

Write one sentence of 80 characters or fewer starting with a verb and naming the trigger rather than the technology. The catalog truncates after a dash, the first period, or 80 characters, and this line alone determines whether the skill gets selected.

When should I bundle a script in a skill versus registering a tool?▼

Bundle a script under the skill's scripts/ folder when it only makes sense inside that skill's procedure. Register it as a Forged Tool when the capability must be callable by name on any turn without the skill being loaded.

Why does skill_view return nothing for a skill that skill_list shows?▼

The name in the frontmatter does not match the folder name exactly, making the skill invisible to skill_view while still listed. Fix the frontmatter with skill_file_write so the name equals the folder name.

Why does skill_patch keep failing on an exact-looking string?▼

The old string must match byte for byte, and invisible differences like line endings, non-breaking spaces, or trailing whitespace cause failures. Copy the fragment verbatim from skill_view output, or replace the whole file with skill_file_write.