CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

counterexample-debugger

Debug proof failures using counterexamples from Nitpick (Isabelle) or QuickChick (Coq) to identify specification errors, missing preconditions, and proof strategy issues. Use when: (1) A proof attempt fails and you need to understand why, (2) Counterexamples are generated by Nitpick or QuickChick, (3) Specifications may be incorrect or incomplete, (4) Theorems need validation before proving, (5) Missing preconditions or lemmas need identification, or (6) Proof failures need explanation and correction suggestions. Supports both Isabelle/HOL and Coq equally.

89

1.10x
Quality

88%

Does it follow best practices?

Impact

93%

1.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-organized with strong progressive disclosure and a clear, action-oriented workflow supported by real code examples. The main weakness is redundancy: the same root-cause material recurs across three sections, which inflates the body without adding guidance.

Suggestions

Consolidate 'Counterexample Analysis Patterns' and 'Common Root Causes' into a single section to eliminate the duplicated root-cause taxonomy and reduce token cost.

Tighten the 'Tips' section by removing items that already appear in the workflow and Debugging Checklist (e.g., 'Verify manually', 'Retest after fixing', 'Fix root cause').

Convert implicit validation into explicit gated checkpoints in the workflow (e.g., 'Only proceed to proof once retest finds no counterexample') to lift workflow_clarity.

DimensionReasoningScore

Conciseness

The body is mostly lean (bulleted lists, no concept padding), but the root-cause taxonomy is repeated across 'Counterexample Analysis Patterns', 'Common Root Causes', and 'Debugging Checklist', and the 'Tips' section restates workflow points — more than minor redundancy.

3 / 5

Actionability

Concrete before/after Isabelle and Coq code blocks and symptom/cause/fix pattern entries give actionable guidance, though they are illustrative snippets rather than runnable tool-invocation procedures.

4 / 5

Workflow Clarity

The six-step workflow is clearly sequenced and step 6 plus the checklist include retest/verify loops; validation is present but not framed as hard gate checkpoints, so it falls short of a 5.

4 / 5

Progressive Disclosure

The body is well sectioned with concise inline key-point summaries and three clearly signaled, one-level-deep reference files (nitpick_guide.md, quickchick_guide.md, examples.md), all of which exist on disk.

5 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an exemplary description: it states a clear purpose, lists multiple concrete capabilities, and provides an explicit six-condition trigger list using the exact terminology users would invoke. The only minor concern is length, but every clause earns its place.

DimensionReasoningScore

Specificity

The description names concrete actions ('identify specification errors, missing preconditions, and proof strategy issues') plus explanation and correction suggestions, giving comprehensive coverage of what the skill does.

5 / 5

Completeness

It explicitly answers both 'what' (debug proof failures using counterexamples) and 'when' via a six-item numbered 'Use when:' list with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes the natural domain terms a user would actually say — 'proof failures', 'counterexamples', 'Nitpick', 'QuickChick', 'Isabelle/HOL', 'Coq', 'theorems', 'preconditions', 'lemmas' — covering tool names and synonyms comprehensively.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — counterexample-based proof debugging for Isabelle/HOL and Coq via Nitpick/QuickChick — making conflict with other skills minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ArabelaTso/Skills-4-SE

Path

skills/counterexample-debugger/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.