proof-carrying-code-generator
Generate executable code together with formal proofs certifying safety and correctness properties in Isabelle/HOL or Coq. Use when building verified software, safety-critical systems, or when formal guarantees are required. Produces code with accompanying proofs for memory safety, bounds checking, functional correctness, invariant preservation, and termination. Supports extraction to OCaml/Haskell/SML and integration with existing codebases.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill proof-carrying-code-generator93
Does it follow best practices?
Validation 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 articulates specific capabilities (formal proofs, code generation, extraction), provides explicit trigger conditions ('Use when building verified software, safety-critical systems'), and uses highly distinctive terminology that would not conflict with other skills. The description is comprehensive yet concise, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate executable code together with formal proofs', 'proofs for memory safety, bounds checking, functional correctness, invariant preservation, and termination', 'extraction to OCaml/Haskell/SML', and 'integration with existing codebases'. | 3 / 3 |
Completeness | Clearly answers both what ('Generate executable code together with formal proofs certifying safety and correctness properties') AND when ('Use when building verified software, safety-critical systems, or when formal guarantees are required') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Isabelle/HOL', 'Coq', 'formal proofs', 'verified software', 'safety-critical systems', 'formal guarantees', 'memory safety', 'bounds checking', 'functional correctness', 'OCaml/Haskell/SML'. These cover both domain-specific terms and common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting formal verification with specific proof assistants (Isabelle/HOL, Coq). The combination of formal proofs, specific theorem provers, and extraction targets makes it unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent actionability through complete, executable code examples in both Isabelle and Coq. The workflow clarity is good with explicit steps and a verification checklist. The main weakness is some verbosity in the overview and explanatory sections that assume less of Claude's existing knowledge about formal verification concepts.
Suggestions
Trim the Overview section - Claude already knows what proof-carrying code is; jump directly to the workflow and approaches
Remove the ASCII workflow diagram and integrate the steps directly into the approach descriptions to save tokens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanatory content like the overview section explaining what PCC is, which Claude would already know. The workflow diagram and some introductory text could be trimmed. | 2 / 3 |
Actionability | Provides fully executable code examples in both Isabelle and Coq with complete syntax. Examples are copy-paste ready with clear patterns for specifications, implementations, proofs, and extraction commands. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit sequences (specification → implementation → proof → extraction). Includes a verification checklist with explicit validation steps and the three approaches are well-sequenced with numbered steps. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, detailed examples inline, and appropriate references to separate files (references/isabelle_pcc.md, references/coq_pcc.md, references/safety_properties.md) for framework-specific details. Navigation is clear and one-level deep. | 3 / 3 |
Total | 11 / 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.
- 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.