AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Co Math Init

skill-morankor-theorist-toolbox-co-math-init · by morankor

Initialize a new AI co-mathematician research project. Use when the user wants to start a new math research investigation with AI agent support, or types "/co-math-init", "start a co-math project", "new research project", or similar. Scaffolds a directory with paper.tex, goals.md, decisions.md, workstreams/, and per-project hooks/config that enforce the co-mathematician discipline (no hand-waving…

No reviews yet
0 installs
36 views
0.0% view→install

Install

$ agentstack add skill-morankor-theorist-toolbox-co-math-init

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-morankor-theorist-toolbox-co-math-init)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Co Math Init? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

> Author: Moran Koren, Ben-Gurion University of the Negev (korenmor@bgu.ac.il). Part of the Theorist Toolbox.

co-math-init

Bootstrap a new research project for the personal AI co-mathematician system, modelled after the Google DeepMind AI Co-Mathematician paper (Zheng et al., 2026-05-07).

This skill creates the directory layout, copies the LaTeX template, initializes the per-project hook configuration, and sets up the workstream registry. After init, the user can spawn workstreams via the project-coordinator sub-agent.

When to invoke

Trigger phrases:

  • /co-math-init
  • "start a new co-math project"
  • "init a research project"
  • "new mathematician project"

Steps

1. Gather inputs from the user

Ask via AskUserQuestion:

  1. Project name — short, lowercase-kebab-case (e.g., ambidextrous-sofa). This becomes the directory name.
  2. Initial research question — one sentence. Goes into goals.md. The user can refine later.
  3. Strict mode — strict (default) or pragmatic. Strict means the prover sub-agent must mark every gap with \unproven{...} and never hand-wave. Pragmatic allows informal prose for minor steps. Default is strict unless the user explicitly says otherwise; this default is recorded in user memory and must be respected.
  4. Parent directory — where to create the project. Default: current working directory.

2. Create the directory structure

Inside //:

paper.tex
goals.md
decisions.md
PROJECT_README.md
co-math-config.json
workstreams/
  .gitkeep
references/
  .gitkeep
failed-explorations/
  .gitkeep
.co-math/
  approvals/
    .gitkeep
  workstream-registry.json
.claude/
  settings.json        # per-project hooks (Phase 3 — empty for now)

3. Populate files from templates

Templates live in this skill's templates/ directory. For each entry below, Read the template, do placeholder substitution, then Write to the project path:

| Template | Destination in project | |---|---| | templates/paper.tex | paper.tex | | templates/goals.md | goals.md | | templates/decisions.md | decisions.md | | templates/PROJECT_README.md | README.md | | templates/co-math-config.json | co-math-config.json | | templates/claude-settings.json | .claude/settings.json |

Placeholders to substitute in each file:

| Placeholder | Replace with | |---|---| | {{PROJECT_NAME}} | the project name | | {{RESEARCH_QUESTION}} | the user's initial question | | {{DATE}} | today's date in YYYY-MM-DD | | {{STRICT_MODE}} | true or false (lowercase, JSON literal) |

4. Initialize the workstream registry

Write .co-math/workstream-registry.json:

{
  "project": "",
  "created": "",
  "strict_mode": ,
  "next_id": 1,
  "workstreams": []
}

5. Print next steps to the user

After scaffolding, output a concise message:

  • Confirm the directory was created (with absolute path).
  • Explain the files: goals.md for refining the question, paper.tex is the living working paper, workstreams/ will fill up as the project-coordinator spawns work.
  • Tell them to invoke the project-coordinator sub-agent (once Phase 2 ships) to start the first workstream, OR — if Phase 2 isn't built yet — to manually edit goals.md and start drafting in paper.tex.
  • Note the verification ladder available to the coordinator: an informal prover proof (\unproven{} for any gap), or — for results worth machine-checking — a lean-prover workstream that formalises the lemma in Lean 4 and verifies it with lake build, closing the theorem with \leanproved{W{NNN}}. After any proof is APPROVED, a proof-readability pass can polish the exposition without touching the mathematics.
  • Note that hooks are not yet wired up (Phase 3 deliverable).

What this skill does NOT do

  • It does not start any workstream itself. That is the project-coordinator sub-agent's job.
  • It does not invoke any agent. Pure scaffolding.
  • It does not modify global Claude Code settings, only writes a per-project .claude/settings.json.

Notes on respecting prior user decisions

The default strict_mode value is always strict. If the user has previously asked to relax this for a specific project, that is recorded in that project's decisions.md, not as a global default. Each new project starts strict.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.