Verify the authenticity of AI-agent authorization receipts and human-device signoffs. Use this whenever a user shares a "trust receipt", an "authorization receipt", a "signoff", or WebAuthn/passkey approval evidence and asks whether it is valid, genuine, or tampered with. Pairs with the public EMILIA Protocol MCP…
Write programs in the Vera programming language. Use when asked to write, edit, debug, or review Vera code (.vera files). Vera is a statically typed, purely functional language with algebraic effects, mandatory contracts, and typed slot references (@T.n) instead of variable names.
Write programs in the Vera programming language. Use when asked to write, edit, debug, or review Vera code (.vera files). Vera is a statically typed, purely functional language with algebraic effects, mandatory contracts, and typed slot references (@T.n) instead of variable names.
Run the FizzBee model checker or simulator on a .fizz spec. Use when the user wants to verify a spec, run the model checker, simulate behavior, check a guided trace, or interpret model checker output.
Create model-based tests (MBT) connecting a FizzBee spec to a real system under test (SUT). Use when the user has a .fizz spec and wants to generate and run tests against a TypeScript/Playwright UI, Go service, Rust library, or Java application. Also use when working with fizzbee-mbt adapter code in any of these…
Write, edit, or review FizzBee (.fizz) specifications for model checking distributed systems. Use when the user asks to model a system, write a formal spec, define invariants or liveness properties, or when working with a .fizz file.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
Review uncommitted or recent Verus code changes for exec-code modifications, unnecessary == introductions, and verification issues. Use before committing to catch regressions in executable semantics, set reasoning, and proof quality.
Run the full Rust-to-Verus pipeline (migrate → spec → fix → eval → semantic audit → postprocess) in one command. Use when converting Rust code to verified Verus code end-to-end.
Aggressively strip redundant proof code from a Verus codebase while keeping verification passing. Use when you want to slim down Verus proof bloat, simplify redundant proof asserts, or run postprocess cleanup without breaking verification.
Write and iteratively refine executable TLA+ specs (.tla) and TLC model configs (.cfg) from natural-language system designs; run TLC model checking; summarize pass/fail and counterexamples with explicit assumptions and bounds. Use when asked to design or validate a protocol/state machine, create or edit .tla/.cfg…
Write and iteratively refine TLA+ theorem proofs in .tla modules with TLAPS (tlapm); run proof checks and summarize proved vs failed/omitted obligations with explicit assumptions and trust boundaries. Use when asked to create or fix THEOREM or PROOF blocks, diagnose TLAPS failures, strengthen inductive invariants…
Prove one EasyCrypt lemma in place with a managed Codex proof node. Use when the user explicitly invokes $prove or selects Prove from the Codex skill menu.
Verify and proofread C code with ACSL using this repository's Frama-C MCP workflow, Frama-C WP static proof, EVA alarms, and optional E-ACSL runtime checks. Use when asked to run Frama-C, check ACSL contracts, explain WP goals, inspect EVA alarms, validate C annotations, or state what a C proof does and does not…
How to develop the Edict compiler — architecture, coding patterns, structured error conventions, and how to add new features end-to-end. Use this skill when contributing to the Edict TypeScript codebase, adding new AST node types, implementing new builtins, extending the compiler pipeline, fixing bugs in the…
How to write correct Edict JSON AST programs. Covers the AST format, node types, ID conventions, common patterns, and how to interpret and fix structured errors. Use this skill when writing Edict programs, creating example programs, producing JSON ASTs for the Edict compiler, demonstrating language features, or…
How to write and run tests for the Edict compiler. Covers vitest conventions, test directory structure, patterns for testing each pipeline stage, structured error assertions, and coverage expectations. Use this skill when writing tests, fixing failing tests, adding coverage for new features, or understanding the test…
Screen informal↔Lean 4 statement pairs for faithfulness defects. Use whenever writing, editing, translating, or reviewing Lean 4 theorem or definition statements that are meant to formalize informal mathematics: after drafting a statement, before committing formalizations, when auditing a benchmark file, or when the…
Extend Sounio's epistemic types with advanced uncertainty quantification methods, such as confidence intervals, non‑Gaussian distributions, and Dempster‑Shafer evidence combination, positioning the language at the state‑of‑the‑art in measurement science.
Work on the profile-guided optimization pipeline: counter injection, .sprof file output, strategy promotion, inlining, layout, const-fold/DCE, and register allocation; use when editing any sprint 38–52+ IR optimization files.