forge

Generate NexusOS procedures using the FORGE standard template with validation and Cortex save.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/cryptopafi/nexusos-skills --skill forge-cryptopafi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge
Source: https://github.com/cryptopafi/nexusos-skills/tree/main/forge
Command: npx skills add https://github.com/cryptopafi/nexusos-skills --skill forge-cryptopafi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This starter helps create NexusOS procedures using the FORGE standard template, ensuring consistent structure, validation, and governance for new workflows.

Core Features & Use Cases

  • Generates a complete NexusOS procedure following the standard structure §1-§4 with a mandatory enforcement loop and Cortex save.
  • Performs input validation, handles edge cases, and emits two verification keys (VKs) upon successful completion.
  • Supports linking a rule and updating procedure-health status to support auditing and governance.

Quick Start

Invoke forge <procedure-name> with an appropriate domain, scope, and optional rule to draft a new NexusOS procedure.

Frequently Asked Questions about forge

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

FAQPage Schema
How do I create a NexusOS procedure with the FORGE template?

To create a NexusOS procedure, invoke forge <procedure-name> with a defined domain, scope, and optional rule. This generates a complete procedure following the standard structure §1-§4 with a mandatory enforcement loop and Cortex save.

What is a NexusOS procedure enforcement loop and when do I need it?

A NexusOS procedure enforcement loop is a required structural component for operational and training workflows. You need it when generating new procedures to ensure consistent governance, validation, and compliance with the FORGE standard template.

Does the FORGE procedure template validate inputs and handle edge cases?

Yes, the FORGE procedure template validates inputs and handles edge cases during procedure generation. Upon successful completion, it writes to procedure-health.json with locking and emits two verification keys (VKs) for auditing.

Can I link a rule and update procedure-health status when generating a NexusOS procedure?

Yes, you can link an optional rule and update procedure-health status when generating a NexusOS procedure. This supports auditing and governance by writing locked status updates to procedure-health.json and performing a Cortex save.

What's the best way to structure a NexusOS procedure for governance and auditing?

The best way to structure a NexusOS procedure for governance is using the FORGE standard template. It enforces a complete §1-§4 structure, mandatory enforcement loops, input validation, linked rules, and emits verification keys (VKs) upon successful completion.

Why does my NexusOS procedure generation fail to emit verification keys?

NexusOS procedure generation only emits verification keys (VKs) upon successful completion. If input validation fails or edge cases are not handled correctly, the process terminates without emitting VKs or performing the Cortex save.