CtrlK
BlogDocsLog inGet started
Tessl Logo

proof-failure-explainer

Analyze and explain why Isabelle or Coq proofs fail, identifying the root cause such as type mismatches, missing assumptions, incorrect goals, unification failures, or inapplicable tactics. Use when the user encounters proof failures, error messages in formal verification, stuck proof states, or asks why their Isabelle/Coq proof doesn't work.

84

1.01x
Quality

80%

Does it follow best practices?

Impact

88%

1.01x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/proof-failure-explainer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 diagnostic skill with concrete bilingual examples and a clean workflow, but it is somewhat verbose with redundant restating of failure categories and generic best-practice padding.

Suggestions

Collapse the redundant failure-category listings: present categories once in Step 2 and reference them from Step 3 and Diagnostic Questions rather than restating each.

Trim the 'Best Practices' section to only non-obvious guidance; drop generic advice like 'Read error messages carefully' and 'Consult documentation' that Claude already knows.

Consider moving the six full worked examples into references/failure_patterns.md and keeping one representative example inline to reduce body length.

DimensionReasoningScore

Conciseness

Mostly efficient but padded: the failure categories are restated across Step 2, Step 3, Diagnostic Questions, and Best Practices, and 'Best Practices' repeats generic advice Claude already knows ('Read error messages carefully', 'Consult documentation').

3 / 5

Actionability

Provides concrete, mostly executable Coq and Isabelle examples with exact error text and copy-paste solutions naming specific tactics, with only minor gaps.

4 / 5

Workflow Clarity

A clear 5-step sequence (Gather Context, Identify Category, Analyze Root Cause, Explain, Suggest Solutions) is present; this is a diagnostic (not destructive/batch) skill so the validation cap does not apply, though explicit checkpoints are light.

4 / 5

Progressive Disclosure

Well-sectioned body with a clearly signaled, one-level-deep reference to the real references/failure_patterns.md; content is mostly appropriately split, with minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

92%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 strong, third-person description that clearly states concrete capabilities and provides explicit 'Use when' trigger guidance covering natural user phrasings. Minor room for additional synonyms, but it is comprehensive and distinct.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Analyze and explain why ... proofs fail, identifying the root cause such as type mismatches, missing assumptions, incorrect goals, unification failures, or inapplicable tactics') with comprehensive coverage of root-cause categories.

5 / 5

Completeness

Explicitly answers both 'what' (analyze/explain/identify root cause) and 'when' ('Use when the user encounters proof failures, error messages in formal verification, stuck proof states, or asks why their Isabelle/Coq proof doesn't work') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('proof failures', 'error messages in formal verification', 'stuck proof states', 'why their Isabelle/Coq proof doesn't work'), but a few natural synonyms or phrasings users might say are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Isabelle/Coq proof failures) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ArabelaTso/Skills-4-SE
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.