midnight-verify:verify-by-execution

Compile and execute Compact test contracts to verify runtime behavior.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that Compact smart contract claims are true by observing actual runtime behavior rather than relying on compilation success alone, reducing false positives caused by code that compiles but misbehaves at execution time.

Core Features & Use Cases

  • End-to-end verification: create a minimal test contract related to the claim, compile it with the Compact CLI, run the compiled output with the Compact runtime, and interpret the observed results.
  • Ledger-level evidence: extract cost breakdowns, well-formedness checks, and transaction properties when claims concern ledger semantics or cost models.
  • Reproducible job workspace: lazy-initialized workspace per job, structured job directories, runner scripts, and standardized report format to capture compiler and runtime outputs.

Quick Start

Create a minimal Compact test contract that exercises the claimed behavior, compile it with the Compact CLI, run the compiled output with the @midnight-ntwrk/compact-runtime, and report whether the observed output confirms the claim.

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

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

FAQPage Schema
How do I verify Compact smart contract claims beyond just checking if the code compiles?

Verify Compact claims by compiling a minimal test contract with the Compact CLI and executing it with @midnight-ntwrk/compact-runtime to observe actual runtime behavior, reducing false positives from code that compiles but misbehaves.

What runtime errors and ledger costs can I check when testing Compact contracts?

You can check syntax, types, return values, runtime errors, and ledger-level cost breakdowns or well-formedness by executing the compiled contract and capturing the runner output in a structured execution report.

How do I test Compact contract runtime behavior using a JavaScript runtime?

Create a minimal test contract, compile it with the Compact CLI, then run the compiled output with @midnight-ntwrk/compact-runtime inside a lazy-initialized job workspace to capture and interpret runtime behavior.

Does the Compact CLI runtime execution environment support structured reporting for smart contracts?

Yes, runtime execution produces a reproducible job workspace with standardized report formats that capture both compiler output and runner output, formatting a structured execution report for verification.

Why does my Compact smart contract compile successfully but fail during runtime execution?

Code that compiles can still misbehave at execution time; observing actual runtime behavior via @midnight-ntwrk/compact-runtime execution reduces false positives that compilation success alone cannot detect.