forge

Create and verify Skills using a RED-GREEN-REFACTOR workflow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Milovan-Crowley/Consilium --skill forge-milovan-crowley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge
Source: https://github.com/Milovan-Crowley/Consilium/tree/main/generated/claude/skills/forge
Command: npx skills add https://github.com/Milovan-Crowley/Consilium --skill forge-milovan-crowley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forge provides a structured, repeatable process for creating, editing, and validating Skills, reducing deployment risk by enforcing a formal test-driven workflow on Skill documents.

Core Features & Use Cases

  • Create new Skills from templates with frontmatter validation and guided structure.
  • Edit existing Skills with a disciplined review and regression-testing workflow.
  • Verify Skills before deployment using a red-green-refactor approach and deployment checklist.

Quick Start

Run a baseline pressure scenario, write a minimal SKILL.md, and complete RED-GREEN-REFACTOR until deployment is verified.

Frequently Asked Questions about forge

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

FAQPage Schema
How do I validate Skill documents before deployment?

Validate Skill documents before deployment by applying a red-green-refactor workflow that runs baseline pressure scenarios and completes a deployment checklist to verify readiness.

What is the test-driven workflow for creating new Skills?

The test-driven workflow for creating Skills follows a RED-GREEN-REFACTOR cycle: writing failing baseline tests, implementing minimal SKILL.md documents, and refining to close loopholes.

What frontmatter is required in a SKILL.md file?

A SKILL.md file requires frontmatter containing at minimum the name and description fields to pass validation and enable reproducible Skill creation and deployment.

Can I use optional directories like scripts and references when structuring a Skill?

You can include optional directories such as scripts/, references/, and assets/ when structuring a Skill to support documentation and organize supplementary workflow components.

What's the best way to edit existing Skills without causing regressions?

Edit existing Skills without causing regressions by applying a disciplined review workflow that enforces regression testing alongside the red-green-refactor validation cycle.