agent-builder

Guides writing, rebuilding, and reviewing agent definitions with sections, gates, and validation checks.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/bsamiee/Rasm --skill agent-builder-bsamiee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-builder
Source: https://github.com/bsamiee/Rasm/tree/main/.claude/skills/agent-builder
Command: npx skills add https://github.com/bsamiee/Rasm --skill agent-builder-bsamiee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing agent definitions that delegate correctly is hard: facts get duplicated between skills and agents, discovery steps repeat, gates lack proof, and descriptions fail to route. This Skill provides the rules for dividing knowledge between skills and agents, structuring agent files, and validating the finished result. ## Core Features & Use Cases - Skill/agent divide rules: Decides where each fact lives so knowledge is stated once, with criteria for when repeated discovery steps and gates justify a new agent. - Section-by-section authoring standards: Defines the twelve sections of an agent file (role, context_gathering, sources, decision, procedure, gate, done_when, and more) with concrete writing rules for each. - Proven tool forms reference: Ships a references file of verified command forms and behaviors for git, fd, rg, sd, mise, Nx, dotnet, ast-grep, pytest, ruff, biome, and MCP tools. - Use Case: When rebuilding an existing agent definition, apply the checks section to run ast-grep scans, claude plugin validate, and git diff against the earlier revision to confirm no commands or rows were dropped. ## Quick Start Use the agent-builder skill to review my agent definition file and check its sections, gates, and description against the standards.

Frequently Asked Questions about agent-builder

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

FAQPage Schema
How do I write an agent definition file?▼

Open with frontmatter (name, description, optional skills, tools, color) and a heading, then write sections in run order: role, context_gathering, sources, decision, procedure, gate, and done_when. Each section has specific rules, such as gates pairing commands with result lines.

When should knowledge go in a skill versus an agent?▼

Skills hold subject knowledge every caller applies: intent, criteria, and tool facts. Agents hold one role's purpose, scope, run order, and proof. Each fact is stated once, and repeated discovery steps with a shared gate justify creating an agent.

How do I validate a finished agent definition?▼

Run ast-grep scan --no-ignore hidden on the file expecting no output, then claude plugin validate on the agents directory expecting Validation passed. Also verify every named path, skill, target, and MCP tool exists, and that each command ran from repository root.

What belongs in an agent gate section?▼

Gate lines pair a command with its expected result line, such as exit 0 with no output or N passed; 0 failed. Gates name their scope selector, run once at close, and tools silent on clean runs need a coverage count or printed line as proof.

What should be excluded from an agent definition?▼

Exclude sentences a preloaded skill already states, Skill calls for listed skills, scope enumerations, output contracts, soft bounds, and steps that write tests or scripts to verify the run's own work. Narration of past runs is replaced by the criterion it showed.