BuildSkill

Create and validate Forge skills with SKILL.md frontmatter and body structure.

5|3|Updated Feb 19, 2026

Search Tags:#validation #build #conventions #skill #frontmatter #forge

Ready to run

npx skills add https://github.com/N4M3Z/forge-core --skill buildskill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: BuildSkill
Source: https://github.com/N4M3Z/forge-core/tree/main/skills/BuildSkill
Command: npx skills add https://github.com/N4M3Z/forge-core --skill buildskill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forge module teams struggle to consistently draft and validate Skill definitions that meet the Forge conventions, frontmatter, and body structure.

Core Features & Use Cases

Enforces SKILL.md frontmatter presence (name, description, version) and a compliant body structure.
Provides guidance for writing, reviewing, and auditing skills for Forge modules.
Supports optional sidecar metadata for provider-specific configuration and multi-provider workflows.

Quick Start

Create a new BuildSkill by writing SKILL.md following the Forge Skill Conventions.

Frequently Asked Questions about BuildSkill

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

FAQPage Schema

How do I validate Forge skill frontmatter and body structure?▼

To validate Forge skill frontmatter and body structure, draft your SKILL.md ensuring required fields (name, description, version) are present and the body aligns with Forge conventions. This process audits and enforces compliant skill definitions.

What is the required frontmatter for a Forge SKILL.md file?▼

The required frontmatter for a Forge SKILL.md file includes the name, description, and version fields. Ensuring these fields are present and correctly formatted is essential for meeting Forge conventions and passing skill validation checks.

Can I use sidecar metadata for provider-specific configuration in Forge skills?▼

Yes, you can use optional sidecar metadata for provider-specific configuration in Forge skills. This feature supports multi-provider workflows by allowing supplementary settings alongside the standard SKILL.md frontmatter and body structure.

How do I create a new Forge skill from scratch?▼

To create a new Forge skill from scratch, write a SKILL.md file following the Forge Skill Conventions. Include the mandatory frontmatter fields and structure the body correctly to pass validation checks for module integration.

What are the common validation errors when drafting Forge skills?▼

Common validation errors when drafting Forge skills include missing required frontmatter fields like name, description, or version, and a malformed body structure. Ensuring compliance with Forge conventions prevents these issues during skill auditing and updates.