Acorn Prover

v1.0.0

Verify and write proofs using the Acorn theorem prover for mathematical and cryptographic formalization. Use when working with Acorn proof files (.ac), verifying theorems, formalizing mathematical or cryptographic protocols, or writing proofs in the Acorn language. Triggers on: (1) Creating or editing .ac files, (2) Running acorn verify commands, (3) Formalizing math or crypto proofs, (4) Questions about Acorn syntax or standard library.

1· 1.7k·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for flyingnobita/acorn-prover.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Acorn Prover" (flyingnobita/acorn-prover) from ClawHub.
Skill page: https://clawhub.ai/flyingnobita/acorn-prover
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install acorn-prover

ClawHub CLI

Package manager switcher

npx clawhub@latest install acorn-prover
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill's name, description, and instructions align: it expects an Acorn CLI and an acornlib/project path and runs acorn commands. However, the registry metadata lists no required binaries or credentials even though SKILL.md assumes the 'acorn' CLI is on PATH and will optionally call 'mise' if present. This omission is an incoherence (declared requirements don't fully match runtime expectations).
Instruction Scope
SKILL.md limits actions to asking the user for two paths, validating them, running the provided setup.sh (which writes a local config.env), sourcing that config, and invoking acorn/mise commands against the user-supplied project. It does not instruct the agent to read unrelated system files, transmit data to external endpoints, or access unrelated credentials.
Install Mechanism
There is no install spec (instruction-only), and the only script included is a small setup.sh that validates directories and writes config.env inside the skill directory. No remote downloads or archive extraction are performed.
Credentials
The skill stores configuration in a local config.env (ACORN_LIB, ACORN_PROJECT, USE_MISE) rather than requiring platform-level environment variables or secrets — this is proportional. Note: the skill does not declare that it requires the acorn or mise binaries, so the metadata understates the runtime environment needs.
Persistence & Privilege
The skill does write a single config.env file into its own skill directory during setup, which is expected behavior for configuration. It does not request always:true or other elevated persistent privileges, and it does not modify other skills or system-wide settings.
What to consider before installing
This skill looks like a legitimate wrapper for running the Acorn theorem prover but has a small inconsistency you should be aware of: it expects the 'acorn' CLI (and will use 'mise' if present) even though those binaries are not listed in the skill metadata. Before installing or running: (1) confirm you have a trusted 'acorn' binary on your PATH (and 'mise' if you want that path), (2) ensure you are comfortable that the skill will write a skills/acorn-prover/config.env file containing the two paths you provide, and (3) do not point ACORN_LIB or ACORN_PROJECT at sensitive or system directories. If you need higher assurance, inspect or run the acorn binary and mise in a sandbox, and consider requesting the publisher to update the skill metadata to declare required binaries.

Like a lobster shell, security has layers — review code before you run it.

latestvk975mnnzjqga6byce7hfnyt94s80cxz7
1.7kdownloads
1stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Acorn Prover

Setup (MUST DO WHEN RUNNING FIRST TIME)

If config.env does not exist in the skill directory:

  1. Ask the user for the following paths:

    • ACORN_LIB - Path to acornlib (e.g., /path/to/acornprover/acornlib)
    • ACORN_PROJECT - Path to project directory for .ac files (e.g., /path/to/acorn-playground)
  2. Verify the paths exist using list_dir or equivalent. If a path is invalid, inform the user and ask again.

  3. Run setup.sh with the validated paths:

bash skills/acorn-prover/scripts/setup.sh "<ACORN_LIB>" "<ACORN_PROJECT>"
  1. Source the config to get ACORN_LIB, ACORN_PROJECT, and USE_MISE variables:
source skills/acorn-prover/config.env

If any of the above are blank / not set, inform the user to set the variable manually. If any of the above are changed, ask the user for new paths and run setup again.

Configuration

Config values are stored in skills/acorn-prover/config.env:

VariableDescription
ACORN_LIBPath to acornlib
ACORN_PROJECTProject directory for .ac files
USE_MISEtrue if mise is available

Verify Proofs

If USE_MISE=true:

mise run acorn verify <filename>.ac

Otherwise, use the direct CLI:

acorn --lib "$ACORN_LIB" verify <filename>.ac

Reverify Proofs (CI/CD)

Check that all proofs are cached with no AI searches required:

# With mise
mise run acorn reverify

# Or direct CLI
acorn --lib "$ACORN_LIB" reverify

Use for CI pipelines to ensure all proofs are complete.

Training Data Generation

Generate training data (problem-proof pairs) for AI model development:

# With mise
mise run acorn training ./training_data

# Or direct CLI
acorn --lib "$ACORN_LIB" training ./training_data

Argument: DIR - Directory to output training data.

Documentation Generation

Generate library reference documentation:

# With mise
mise run acorn docs ./docs/library

# Or direct CLI
acorn --lib "$ACORN_LIB" docs ./docs/library

Argument: DIR - Directory to output documentation.

Workflow

  1. Source config: source skills/acorn-prover/config.env
  2. Write proof file in $ACORN_PROJECT/
  3. Run the appropriate command (verify, reverify, training, docs)
  4. Always show the full command output to the user (success or error)
  5. Debug errors using the common errors table in references/syntax.md
  6. Iterate until verification passes

Quick Syntax Overview

from nat import Nat
from add_comm_group import AddCommGroup

// Theorems - auto-proved or with hints
theorem example(a: Nat, b: Nat) {
    a < b implies a != b
}

// Typeclasses - axioms are named blocks, no "axiom" keyword
typeclass A: AddGroup extends Zero, Neg, Add {
    inverse_right(a: A) { a + -a = A.0 }
}

// Structures
structure Pair[T, U] { first: T  second: U }

// Inductive types - constructors MUST be lowercase
inductive MyBool { tru fls }

Key points:

  • Built-in logic keywords (not, and, or, implies, iff, true, false) are reserved - do not redefine
  • Constructor names must be lowercase
  • Typeclass axioms use named blocks, not the axiom keyword

Standard Library (acornlib)

Key modules in $ACORN_LIB/src:

ModuleContents
nat/Natural number axioms, induction, addition
add_group.acAddGroup with a + -a = A.0
add_comm_group.acAbelian groups (AddCommGroup)

References

  • Full syntax, error table, examples: See references/syntax.md
  • Context7 docs: Use context7 MCP with /acornprover/acorn or /acornprover/acornlib for latest documentation

Comments

Loading comments...