cli-forge-validate

Validate Rust CLI Skill projects against a 47-check compliance suite.

Updated Apr 2, 2026

Search Tags:#cli #verification #compliance #reporting #rust #validate

Ready to run

npx skills add https://github.com/ByteLandTechnology/cli-forge --skill cli-forge-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cli-forge-validate
Source: https://github.com/ByteLandTechnology/cli-forge/tree/main/cli-forge-validate
Command: npx skills add https://github.com/ByteLandTechnology/cli-forge --skill cli-forge-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates a Rust CLI Skill project against the cli-forge 47-check compliance suite to ensure structural integrity, correct metadata, and conformity with runtime conventions before publication.

Core Features & Use Cases

Runs the authoritative 47-check rules across STRUCT, NAME, DEPS, META, SKILL, BUILD, TREE, HELP, DIR, CTX, ERR, REPL, and DAEMON categories.
Produces a machine-readable validation-report.yml detailing pass/fail status, warnings, and remediation guidance.
Guides takeovers, scaffolds, and extensions by aligning the target project with the planning brief and contract surfaces.

Quick Start

Run the validation on your Rust CLI Skill project to generate a comprehensive compliance report.

Frequently Asked Questions about cli-forge-validate

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

FAQPage Schema

How do I validate a Rust CLI project against compliance rules before publication?▼

To validate a Rust CLI project, run a 47-check compliance suite that verifies structural integrity, metadata, and runtime conventions. This process inspects your Cargo.toml and SKILL.md contract to produce a structured validation report.

What is a cli-forge compliance report and how does it work?▼

A cli-forge compliance report is a machine-readable validation-report.yml file detailing pass/fail status, warnings, and remediation guidance. It works by enforcing a 47-check suite across categories like STRUCT, NAME, DEPS, META, SKILL, BUILD, TREE, HELP, DIR, CTX, ERR, REPL, and DAEMON.

Do I need a Cargo.toml and SKILL.md file to run CLI skill validation?▼

Yes, CLI skill validation requires a valid Cargo.toml-based Rust project, the presence of .cli-forge/cli-plan.yml when in scope, and a SKILL.md contract. These files are necessary to verify structure, metadata, and daemon surfaces.

How do I check if my scaffolded or takeover-adopted Rust CLI skill meets metadata requirements?▼

Check a scaffolded or takeover-adopted Rust CLI skill by applying the 47-check compliance suite across the design, plan, scaffold, and validate stages. This aligns the target project with the planning brief and contract surfaces to generate a structured compliance report.

Can I use this validation suite for extended Rust CLI skills or only newly scaffolded ones?▼

This validation suite applies to scaffolded, takeover-adopted, and extended Rust CLI skills. It guides all three project types by enforcing the 47-check rules to ensure conformity with runtime conventions before publication.

Why does my Rust CLI skill validation fail and how do I get remediation guidance?▼

Rust CLI skill validation fails when the project violates one or more of the 47 structural, metadata, or daemon surface checks. The generated validation-report.yml provides specific pass/fail status, warnings, and remediation guidance to fix the compliance issues.