BuildAgent

Scaffold, validate, and audit agent markdown files for forge conventions.

5|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/N4M3Z/forge-core --skill buildagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: BuildAgent
Source: https://github.com/N4M3Z/forge-core/tree/main/skills/BuildAgent
Command: npx skills add https://github.com/N4M3Z/forge-core --skill buildagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold, validate, and audit agent markdown files to enforce forge conventions and ensure consistent deployment across providers.

Core Features & Use Cases

  • Scaffold new agent files with correct frontmatter and body structures following forge conventions.
  • Validate existing agent markdown files for required frontmatter fields, naming rules, and body structure.
  • Audit agent rosters and deployments to ensure alignment with module standards and deployment tooling.
  • Deployment readiness checks to verify compatibility with the install-agents workflow across providers.

Quick Start

Create a new agent by adding a properly formatted Markdown file in the agents/ directory and run make install-agents to deploy.

Frequently Asked Questions about BuildAgent

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

FAQPage Schema
How do I validate frontmatter fields in agent markdown files?

To validate frontmatter in agent markdown files, the tool checks required fields, enforces naming rules, and verifies body structure against forge conventions. This ensures existing agents meet module standards before deployment.

What is the best way to scaffold new forge agent definitions?

Scaffolding new forge agent definitions is automated by generating markdown files with correct frontmatter and body structures. Adding a properly formatted file in the agents/ directory and running make install-agents deploys it.

How does an agent audit ensure deployment readiness across providers?

An agent audit ensures deployment readiness by verifying alignment with module standards and the install-agents workflow across providers. It checks agent rosters and validates deployment compatibility to prevent configuration drift.

Do I need specific dependencies to scaffold and validate module agents?

No specific dependencies are required to scaffold and validate module agents. The tool operates independently to enforce forge conventions for module agents shipped with a forge module or project-local agents.

Why does my install-agents workflow fail validation on existing agent markdown?

Install-agents workflow validation fails when existing agent markdown lacks required frontmatter fields, violates naming rules, or has incorrect body structure. Auditing the agent roster identifies and resolves these convention misalignments.