FStarLang
Official@fstarlang
Formal verification and proof engineering for F* and Pulse languages, focusing on SMT-based correctness, C-code extraction, and rigorous specification auditing.
Agent Skills by FStarLang
Showing 8 vetted skills indexed across 1 GitHub repositories.
sourcebuild
Build the F*, Pulse, and KaRaMeL toolchain from source.
proofdebugging
Diagnose failing F* and Pulse proofs by locating the exact assertion, lemma, or solver condition.
krmlextraction
Converts verified F* and Pulse modules to C using KaRaMeL extraction and bundling.
specreview
Review F* and Pulse specifications for weak or missing correctness guarantees.
fstarmcp
Typecheck F* and Pulse code incrementally via the fstar-mcp HTTP API.
smtprofiling
Profile F* SMT obligations sent to Z3 to diagnose slow verification queries.
projectsetup
Structure new F*/Pulse verification projects with Makefile and directory layout.
fstarverifier
Verify F* and Pulse programs and explain proof failures via command-line execution.
Frequently Asked Questions About FStarLang
FAQPage SchemaWhat specific verification tasks are enabled by these capabilities?βΌ
These capabilities enable incremental typechecking of F* and Pulse code, profiling of SMT obligations to resolve slow verification queries, and systematic diagnosis of failing proofs by isolating specific lemmas or solver conditions.
Which engineers benefit from these verification skills?βΌ
Formal methods engineers, security researchers, and systems developers working on high-assurance software benefit from these skills. They are designed for professionals building verified, memory-safe implementations that require rigorous mathematical proof of correctness.
What are the prerequisites for running these verification environments?βΌ
Users must have a functional environment capable of building the F*, Pulse, and KaRaMeL toolchain from source. Projects require a structured directory layout and Makefile configuration to support incremental typechecking and C-code extraction.