midnight-verify:verify-compact

Classify Compact language claims and route them to verification methods and sub-agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a deterministic way to classify claims about the Compact language and decide which verification method(s) and sub-agents should be dispatched so verifications are consistent, efficient, and focused on the right evidence.

Core Features & Use Cases

  • Claim type → method routing: Maps claim categories (syntax, type behavior, stdlib, runtime semantics, disclosure rules, compiler errors, ZKIR/circuit constraints) to the appropriate verification approach.
  • Negative testing guidance: Prescribes how to design tests that demonstrate that a feature is not supported or that a claim fails as expected.
  • Operational hints: Recommends which sub-agents to run concurrently or sequentially (contract writer, source investigator, zkir checker) and which compact-core skills are useful as non-evidentiary hints.
  • Use Case: When presented with a Compact claim about a compiler error or runtime behavior, use this skill to determine whether to compile and run tests, inspect source, or inspect compiled ZKIR.

Quick Start

Ask the verifier to classify this Compact claim and return the recommended verification method(s), sub-agents to dispatch, and suggested negative tests.

Frequently Asked Questions about midnight-verify:verify-compact

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

FAQPage Schema
How do I classify Compact language claims for verification routing?

To classify Compact language claims, map claim categories such as syntax, type behavior, stdlib functions, and ZKIR circuit constraints to a deterministic routing table that dictates the appropriate verification approach.

What is the best way to design negative tests for Compact compiler behavior claims?

The best way to design negative tests for Compact claims is to apply prescribed guidance that demonstrates a specific language feature is unsupported or that a syntax and type behavior claim fails as expected during compilation.

Which sub-agents should I dispatch to verify Compact ZKIR properties?

To verify Compact ZKIR properties, dispatch the contract-writer, source-investigator, and zkir-checker sub-agents based on operational hints that recommend running them concurrently or sequentially within the verification workflow.

When do I need to inspect compiled ZKIR instead of running Compact tests?

You need to inspect compiled ZKIR instead of running tests when verifying claims about circuit constraint structures and compiled ZKIR properties, rather than claims about standard library functions or runtime return semantics.

Can I use compact-core skills as non-evidentiary hints during claim verification?

Yes, you can use compact-core skills as non-evidentiary hints during claim verification to provide operational context, while relying on dispatched sub-agents like the source-investigator to gather actual verification evidence.