midnight-verify:verify-by-cli-execution

Execute compact and compactc commands to verify CLI behavioral claims.

37|9|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-verify-verify-by-cli-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: midnight-verify:verify-by-cli-execution
Source: https://github.com/devrelaicom/midnight-expert/tree/main/plugins/midnight-verify/skills/verify-by-cli-execution
Command: npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-verify-verify-by-cli-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable, evidence-first method to verify behavioral claims about the Compact CLI by running the actual commands and collecting observable outputs instead of relying solely on source inspection or secondary reports.

Core Features & Use Cases

  • CLI availability detection: Determines whether compact and compactc are installed and which wrapper is present.
  • Flag and behavior validation: Checks for flag existence in help output and compares compile results with and without flags to detect behavioral changes.
  • Output, error, and exit-code capture: Records stdout, stderr, and exit codes and inspects filesystem artifacts produced by compilation to confirm or refute claims.
  • Use Case: Validate a claim that --skip-zk changes the build artifacts by compiling a minimal contract with and without the flag and comparing directory listings and outputs.

Quick Start

Run a compact compile on a minimal contract, capture stdout, stderr, exit code, and the build directory listing, and produce a CLI Execution Report summarizing whether the observed outputs confirm the claim.

Frequently Asked Questions about midnight-verify:verify-by-cli-execution

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

FAQPage Schema
How do I verify Compact CLI behavior by running actual commands?

Verify Compact CLI behavior by executing compact and compactc commands to capture stdout, stderr, exit codes, and filesystem side-effects, producing a structured report that confirms, refutes, or marks claims inconclusive.

What is the best way to test if a compactc flag changes build artifacts?

Compile a minimal Compact contract with and without the target flag, then compare directory listings and command outputs to detect and validate behavioral changes in the build artifacts.

Can I check whether compact and compactc are installed before running a compile?

Yes, CLI availability detection determines whether compact and compactc are installed and identifies which wrapper is present before attempting contract compilation or flag validation.

How do I validate flag existence and behavior in the Compact CLI?

Validate flag existence by checking help output for the flag, then compare compile results with and without the flag to detect and verify behavioral changes in the Compact CLI.

Does CLI execution verification capture error messages and exit codes for Compact contracts?

Yes, CLI execution verification records stdout, stderr, and exit codes while inspecting filesystem artifacts produced during compilation to confirm or refute claims about Compact contracts.

Why should I use live command execution instead of source inspection to verify CLI claims?

Live command execution provides a repeatable, evidence-first method by collecting observable outputs like stdout, stderr, and exit codes rather than relying solely on source inspection or secondary reports.