counterexample-guide

Interpret Ivy protocol verification counterexamples and debug failed assertions.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/ElNiak/panther-ivy-plugin --skill counterexample-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: counterexample-guide
Source: https://github.com/ElNiak/panther-ivy-plugin/tree/main/plugins/panther-ivy-plugin/skills/counterexample-guide
Command: npx skills add https://github.com/ElNiak/panther-ivy-plugin --skill counterexample-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users understand and debug complex verification failures in the Ivy protocol specification language, specifically when a counterexample is generated.

Core Features & Use Cases

  • Counterexample Interpretation: Guides users through analyzing structured counterexample traces to pinpoint the root cause of verification failures.
  • State and Assertion Analysis: Provides methods to examine violated assertions, trace state variable changes, and understand execution paths.
  • Use Case: When ivy_verify fails and provides a counterexample trace, use this skill to systematically break down the trace, identify the specific assertion that failed, and understand the sequence of actions that led to the violation, ultimately guiding you to the fix.

Quick Start

Use the counterexample-guide skill to interpret the latest ivy_verify counterexample.

Frequently Asked Questions about counterexample-guide

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

FAQPage Schema
How do I debug an Ivy verification failure when I get a counterexample trace?

To debug an Ivy verification failure, analyze the counterexample trace by examining violated assertions, tracing state variable changes, and understanding the execution path that led to the violation to pinpoint root causes.

What is a counterexample in Ivy protocol testing?

A counterexample in Ivy protocol testing is a structured execution trace generated when verification fails. It demonstrates the specific sequence of actions and state changes that violated an assertion, allowing you to identify protocol specification errors.

How do I interpret state variable changes in an Ivy counterexample trace?

Interpret state variable changes in an Ivy counterexample by systematically breaking down the trace to track how variables evolve across execution steps. This reveals the exact sequence of actions causing the violated assertion and guides your fix.

What's the best way to identify which assertion failed during Ivy verification?

To identify the failed assertion during Ivy verification, systematically analyze the counterexample trace provided by ivy_verify. The trace highlights the specific assertion that was violated and the execution path leading to that violation.

Can I use Ivy's MCP tools for deeper visualization of counterexample traces?

Yes, you can leverage Ivy's MCP tools for deeper analysis and visualization of counterexample traces. These tools help examine execution paths, violated assertions, and state variable changes to debug protocol verification failures.

Why does my Ivy protocol verification keep failing with counterexamples?

Ivy protocol verification fails with counterexamples when your specification contains errors that allow invalid execution paths. Analyzing the counterexample trace reveals the specific violated assertions and state changes that require fixes in your protocol specification.