solve

Check satisfiability of SMT-LIB2 formulas using Z3. Returns sat/unsat with models or unsat cores. Logs every invocation to z3agent.db for auditability.

Quality

78%

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/solve/SKILL.md

Quality

Content

86%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.

A well-structured, actionable skill body with copy-paste commands, a full parameter table, and a clear three-step workflow that doubles as gating. Only mild scaffolding redundancy and a soft validation hint keep conciseness and workflow_clarity just below 5.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence without explaining SMT or Z3 basics; the repeated Action/Expectation/Result scaffolding restates a few points and could be trimmed slightly, matching the score-4 anchor of efficient content with minor over-explanation.	4 / 5
Actionability	Copy-paste ready commands cover the common cases — `python3 scripts/solve.py --formula ...`, `--file`, `--debug` — and a complete Parameters table gives every flag, matching the score-5 anchor of fully executable, copy-paste ready guidance.	5 / 5
Workflow Clarity	Steps 1–3 are clearly sequenced with Result clauses acting as proceed/gate checkpoints and a retry hint ('try simplify or increase the timeout') for unknown/timeout; this is a read-only check rather than a destructive/batch op, so the score-4 anchor of a clear sequence with most checkpoints applies, with only minor validation gaps.	4 / 5
Progressive Disclosure	This is a short, single-purpose skill (under 50 lines) with one real bundle script referenced as `scripts/solve.py` (verified present) and well-organized Step sections, so per the rubric's simple-skill guidance progressive disclosure scores 5 on well-organized sections alone.	5 / 5
	Total	18 / 20 Passed

Description

70%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.

A crisp, third-person description with concrete actions and a distinct niche, but it lacks any explicit 'Use when' trigger guidance, which caps completeness. Adding a trigger clause would lift the weakest dimension.

Suggestions

Add a 'Use when ...' clause stating when to invoke this skill (e.g., 'Use when checking whether an SMT-LIB2 formula is satisfiable or when the user mentions Z3, SMT, sat/unsat, models, or unsat cores').

Include natural-language synonyms users might say (e.g., 'SMT solver', 'is this formula satisfiable') alongside the technical terms.

Clarify the auditability hook's relevance to triggering (e.g., when an auditable solver run is required).

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Check satisfiability', 'Returns sat/unsat with models or unsat cores', 'Logs every invocation' — comparable to the score-4 anchor listing several specific actions with minor coverage gaps.	4 / 5
Completeness	The 'what' is clear but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3 even though the capability description is well stated.	3 / 5
Trigger Term Quality	Good keyword coverage for the niche — 'satisfiability', 'SMT-LIB2', 'Z3', 'sat/unsat', 'models', 'unsat cores' — though a few natural phrasings like 'is this formula satisfiable' or 'SMT solver' are absent, matching the score-4 anchor.	4 / 5
Distinctiveness Conflict Risk	The SMT-LIB2/Z3/satisfiability niche has distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor of a clear niche with distinct triggers.	5 / 5
	Total	16 / 20 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/solve/SKILL.md
Commit: 6aa9416

Reviewed: ~2 hours 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.