ClaudePluginComputationalResearch

Build an LLM-generated "dev notebook" for the paclet under development: a self-contained, evaluated, cloud-deployed Wolfram notebook that presents every exported function (a reference card) plus a sequence of worked examples, each mostly code and each producing a picture. Outputs are embedded (graphics rasterized, small symbolic results kept as live boxes), the build is smoke- tested headless to zero messages, deployed public to the Wolfram Cloud, and the stable URL is linked from the README. Use when the user says "dev notebook", "demo notebook", "build the paclet demo", "show what the paclet does", "reference notebook for the paclet", or the /dev-notebook command.

Create or modify Wolfram Notebooks (.nb) from structured Markdown content using the Wolfram MCP. This is the unified notebook skill — use it for creating new notebooks, editing existing ones, or converting NotebooksLLM/ markdown sources into .nb files. Triggers on: "create notebook", "make a notebook", "notebook about X", "edit notebook", "update notebook", "put this in a notebook", "generate .nb". Also used by other skills (new-project, start-tour) when they produce notebooks.

Add a resource (paper, repo, notebook, dataset, tool, web page) to the wiki. Downloads the file locally (gitignored), creates a wiki article with a Recover section for reproducibility, and updates the index. Use when the user says "add this paper", "save this resource", "note this repo", or when encountering a new reference during work. Also use during new-project to register discovered papers and Wolfram Community resources.

Build a Wolfram paclet archive and install it locally. Use when the user says "build paclet", "build the paclet", "install paclet locally", "make paclet", "create paclet archive", or "test the paclet install".

Run a health check on the wiki. Finds stale articles, missing coverage, broken backlinks, and opportunities for cross-linking. Use at the start of a new session, or when the user says "check wiki", "wiki health", "audit wiki", "wiki status".

Produce a BibTeX/biblatex entry from an arXiv ID or DOI. Optionally appends to Paper/references.bib if it exists. Use when the user says "cite this", "bibtex for arXiv:...", "DOI 10.xxx/...", "add citation", or when adding a reference during paper writing.

Initialize a plain-markdown knowledge base (Wiki/) in the current repo. Use when the user says "init wiki", "set up knowledge base", "add wiki to this repo", or when starting a new project that needs a wiki. Also triggers when update-wiki or check-wiki is invoked but Wiki/ does not exist yet.

Optionally maintain a running scientific journal in LaTeX or Typst — a concise, structured, append-only stream of dated def/thm/rem/claim entries recording the math and physics content and main claims established during research, with every resource cited. Off by default; gated by a per-project toggle in CLAUDE.md. Scaffold it, append dated entries automatically when on, and list the index. Use when the user says "keep a journal", "scientific journal", "journal this", "turn the journal on/off", "journal status", or the /journal command. Distinct from the Wiki (deduplicated encyclopedia): the journal is the typeset, cited record of what was learned and when. Other skills (update-wiki, next-session, cite) feed it when on.

Drive a Lean 4 / Mathlib formalization session via the lean-lsp MCP. Opens a file, reads the goal state, searches Mathlib for closing lemmas, verifies proofs, and writes a formalization checklist to Work/. Use when the user says "formalize in Lean", "prove this in Lean", "what's the Mathlib name for X", "check this Lean proof", "lean state", or during math-research projects with a Lean/ subdirectory.

Scaffold a new project with the wiki-based knowledge management system and perform initial setup. Use whenever the user asks to start a new project, create a new research project, set up a project folder, scaffold a project, begin investigating a new topic, explore something computationally, or create a new paclet. Trigger on: "new project on X", "let's start a project about Y", "set up folders for Z", "init project", "explore X computationally", "investigate Y", "let's look into Z", "create a paclet for X", "new paclet dev repo".

Run one disciplined work session against a Work/ item: pick the next incomplete task, study the Spec, implement exactly ONE task, append a Progress report, mark the task done, sync durable knowledge to the Wiki, commit, and STOP. Built to be run in a FRESH session each time to avoid context accumulation. Use for: "next session", "next task", "work the next task", "continue the work item", "resume <Name>", or the /next-session command. It does exactly one task then stops — it never chains tasks.

Optionally record the prompts/intent behind generated artifacts — notebooks, paclet functions/code, wiki articles, and work items. Maintains an append-only ledger at Wiki/Prompts.md and embeds a back-pointer in each artifact so provenance travels with the file. Off by default; gated by a per-project toggle in CLAUDE.md. Use when the user says "track prompts", "record the prompt", "where did this come from", "turn provenance on/off", "show the prompt ledger", or the /provenance command. Other skills (new-notebook, update-wiki, work, next-session) follow this skill's format when the toggle is on.

Build a Wolfram paclet, install locally, and publish to Wolfram Cloud with a public install URL. Use when the user says "publish paclet", "upload paclet", "deploy paclet", "release paclet", "push paclet to cloud", "share the paclet", or "make paclet available".

Human revision workflow for code, functionality, plans, and deliverables. This skill defines how the LLM interacts with the user when producing anything that needs review. It is not invoked directly — it is a protocol that all other skills follow. Read this skill at the start of every session to internalize the revision rules.

Scaffold a Paper/ folder with LaTeX (amsart, biblatex) or Typst article templates and a shared preamble, then act as an editor on the user-owned document. Use when the user says "scaffold paper", "add paper", "create paper folder", "set up latex", "set up typst", or during new-project when the user wants a paper. Trigger on: "paper setup", "latex template", "typst template", "add Paper/", "I want to write a paper".

Search external mathematics resources for a topic: MathWorld, nLab, OEIS, DLMF, and Wikipedia math articles. Returns ranked results, optionally hands them to add-resource. Use when the user says "search math", "find on MathWorld", "look up in nLab", "OEIS sequence", "DLMF formula", "search Wikipedia math", or during math-research project setup when external math sources are needed.

Search Wolfram ecosystem resources for a topic: documentation, Function Repository, Community forum, Stephen Wolfram's writings, and the Wolfram Physics Technical Introduction. Downloads notebooks, creates wiki articles, and logs findings. Use when the user says "search wolfram", "find wolfram resources", "wolfram community search", "what functions exist for X", "check the function repository", or during project setup when the user wants Wolfram-specific resource gathering.

Start, resume, or manage a guided tour of the project. Creates an interactive walkthrough with narrative and runnable code for each topic. Use when the user says "start tour", "give me a tour", "continue tour", "where were we", "tour status", or when presenting the project to someone.

Update the wiki after a substantial change. Creates or updates articles, maintains the index, status, log, and backlinks. Use after any significant step — code changes, new functionality, completed tasks, discoveries. Triggers on: "update wiki", "log this", or automatically after substantial work. Also invoke proactively after completing any multi-step task.

Create and manage work items in the top-level Work/ folder — each a multi-session effort with a Spec (what to build), a Tasks checklist (one task ≈ one session), and a Progress log. This is the project's execution state, separate from the Wiki knowledge base. Use for: "new work item", "start a work item", "spec out X", "plan for X", "break X into tasks", "track this across sessions", "add a task", "update the spec", or the /work command. Creates Work/Backlog/<Name>.md, bootstrapping the folder if missing. A work item's status is its folder (Active/Backlog/Done/Dropped), not a field. Specs follow the revise protocol. Do NOT trigger on casual uses of the word "work".