prove

Prove validity of logical statements by negation and satisfiability checking. If the negation is unsatisfiable, the original statement is valid. Otherwise a counterexample is returned.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/prove/SKILL.md

Quality

Content

85%

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

The body is actionable, well-sequenced, and appropriately organized for a simple single-purpose skill, with only minor redundancy between the opening paragraph and the description.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and avoids explaining concepts Claude already knows, but the opening paragraph restates the description's method ('negate the conjecture and check satisfiability...') and could be tightened, fitting the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides fully executable SMT-LIB snippets and copy-paste-ready bash invocations of prove.py with concrete flags, plus a complete parameters table — copy-paste ready guidance.	3 / 3
Workflow Clarity	The three steps are clearly sequenced with Action/Expectation/Result blocks and explicit branch handling for valid/invalid/unknown/timeout, including recovery guidance ('try simplify or increase the timeout').	3 / 3
Progressive Disclosure	This is a simple, single-purpose skill under the line threshold; the body is well-organized into Step 1/2/3 plus a Parameters section and references its one bundle script (scripts/prove.py), which exists — meeting the simple-skill bar for a 3.	3 / 3
	Total	11 / 12 Passed

Description

67%

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

The description is concrete and occupies a distinct niche, but it omits explicit 'when to use' trigger guidance and only partially covers the natural terms a user would say.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks whether a logical statement, theorem, or SMT-LIB assertion is valid or always holds.'

Broaden trigger terms to include common phrasings such as 'theorem', 'is this valid', 'holds universally', and 'counterexample'.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions — 'Prove validity of logical statements by negation and satisfiability checking' and 'a counterexample is returned' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers 'what' (prove validity via negation/satisfiability and return a counterexample) but lacks any 'Use when...' clause or explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'prove validity', 'logical statements', 'counterexample', and 'satisfiability' are relevant but miss common user phrasings such as 'is this theorem true', 'check if it holds', or 'is this valid', so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	Proving logical-statement validity by negation and satisfiability checking is a clear, narrow niche with distinct triggers that is unlikely to collide with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: Z3Prover/z3
Path: .github/skills/prove/SKILL.md
Commit: 1c89937

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.