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.