Generate structured proof skeletons with tactics, strategies, and intermediate lemmas for theorems in Isabelle/HOL or Coq. Use when users need to: (1) Create proof outlines for theorem statements, (2) Generate proof structure with tactic placeholders, (3) Identify key lemmas needed for a proof, (4) Plan proof strategies (induction, case analysis, forward/backward reasoning), (5) Scaffold proofs with intermediate steps and subgoals, or (6) Convert theorem statements into detailed proof templates. Supports both Isabelle/HOL and Coq equally.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill proof-skeleton-generator88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 excellent skill description that clearly defines a specialized niche in formal theorem proving. It provides comprehensive coverage of capabilities with six explicit use cases, uses appropriate domain-specific trigger terms, and maintains clear distinctiveness from other skills. The third-person voice and structured format make it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate structured proof skeletons', 'Create proof outlines', 'Generate proof structure with tactic placeholders', 'Identify key lemmas', 'Plan proof strategies', 'Scaffold proofs', 'Convert theorem statements into detailed proof templates'. Very comprehensive. | 3 / 3 |
Completeness | Clearly answers both what (generate proof skeletons, tactics, strategies, lemmas) AND when with explicit 'Use when users need to:' clause followed by six specific trigger scenarios. Excellent structure. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'proof skeletons', 'theorems', 'Isabelle/HOL', 'Coq', 'tactics', 'lemmas', 'induction', 'case analysis', 'proof outlines', 'subgoals', 'proof templates'. Good coverage of domain-specific terms users in this niche would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting formal theorem provers (Isabelle/HOL, Coq) with specific proof-related terminology. Unlikely to conflict with general coding skills or other document processing skills due to the specialized domain. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured workflow for generating proof skeletons with good progressive disclosure and clear sequencing. However, it could be more concise by removing explanations of concepts Claude already knows (logical structures, quantifiers) and more actionable by providing complete, executable proof examples rather than template patterns. The strategy selection guide is helpful but verbose.
Suggestions
Remove explanations of basic concepts Claude already knows (quantifiers, logical structures, what induction is) and focus only on the specific patterns and tactics
Add at least one complete, executable example with a real theorem statement and its full proof skeleton that can be directly tested in Isabelle/Coq
Consolidate the 'Proof Strategy Selection Guide' and 'Common Patterns' sections to reduce redundancy - they cover similar ground
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation that Claude would already know (e.g., explaining what quantifiers are, basic logical structures). The workflow section could be tightened, and some of the strategy explanations are verbose. | 2 / 3 |
Actionability | Provides structural templates and patterns but they are more like pseudocode/templates than fully executable examples. The code blocks show skeleton structure but lack complete, copy-paste ready proofs with actual theorem statements that could be tested. | 2 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with logical progression from analysis through output. Each step has clear purpose and the strategy selection guide provides explicit decision criteria for choosing proof techniques. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview, well-signaled references to external files (isabelle_tactics.md, coq_tactics.md, examples.md), and content appropriately organized into sections. Navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.