WolframInstitute

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.

Orchestrate publishable Wolfram Language documentation for a project or paclet - authored as literate-markdown (.md) and built into notebooks / ref pages with MarkdownToNotebook, using the family of Wolfram authoring skills hosted at github.com/WolframInstitute/MarkdownToNotebook. Use this whenever the user wants to document a Wolfram paclet or project, generate reference pages / a guide / tutorials / an overview / a computational essay for their Wolfram Language code, publish a Function/Data/Example/Prompt/Demonstration resource, port existing .nb documentation to markdown, or set up a Wolfram docs pipeline. This is the entry point for "/create-wolfram-documentation". It surveys the project, picks the right doc types, backs up existing .nb docs, ports them to .md, authors each page, and wires up the build.

Author a Wolfram Computational Essay (Stephen Wolfram's narrative-and-code notebook genre, published on the Notebook Archive or Wolfram Cloud) as a literate-markdown document and convert it to a publishable notebook with MarkdownToNotebook. Use this whenever the user wants to write, draft, or publish a Wolfram computational essay, a narrative notebook, an explanatory notebook combining prose and computation - especially when they would rather write markdown than hand-edit notebook cells. Also use it when asked to add abstract, byline, or sections to such an essay.

Author a Wolfram Data Repository resource (a curated dataset packaged with its statistical metadata, primary content, named accessors, and worked examples) as a literate-markdown document and convert it to the official definition notebook with MarkdownToNotebook. Use this whenever the user wants to create, write, draft, or publish a Wolfram Data Repository submission, a Data resource, a dataset accessible via ResourceData / WolframDataRepository, or anything that says `Template: Data` / `ResourceType: Data` - especially when they would rather write markdown than hand-edit notebook cells. Also use it when asked to add content elements, statistical metadata, or examples to such a resource.

Author a Wolfram Demonstration (a deployable interactive Manipulate-based visualization for the Wolfram Demonstrations Project) as a literate-markdown document and convert it to the official authoring notebook with MarkdownToNotebook. Use this whenever the user wants to create, write, draft, or publish a Wolfram Demonstration, an interactive Manipulate, an explorable visualization for demonstrations.wolfram.com - especially when they would rather write markdown than hand-edit notebook cells. Also use it when asked to add snapshots, caption, or metadata to such a Demonstration.

Author a Wolfram Example Repository resource (a deployable Example with named content elements and worked examples) as a literate-markdown document and convert it to the official definition notebook with MarkdownToNotebook. Use this whenever the user wants to create, write, draft, or publish a Wolfram Example Repository resource, an Example resource, a curated dataset or example notebook exposed via ResourceData - especially when they would rather write markdown than hand-edit notebook cells. Also use it when asked to add content elements, examples, or metadata to such a resource.

Author a Wolfram Function Repository resource (a deployable ResourceFunction) as a literate-markdown document and convert it to the official definition notebook with MarkdownToNotebook. Use this whenever the user wants to create, write, draft, or publish a Wolfram Language Function Repository function, a ResourceFunction, or a FunctionResource definition notebook - especially when they would rather write markdown than hand-edit notebook cells. Also use it when asked to add usage, examples, or metadata to such a function.

Author a Wolfram Language guide page (a paclet's documentation home page that lists its functions, like the built-in guide/ pages) as a literate-markdown document and build it with MarkdownToNotebook. Use this whenever the user wants to write or generate a guide page, a paclet landing/overview page, or a curated function index for a Wolfram paclet - rather than hand-editing the DocumentationTools guide authoring notebook.

Author a Wolfram Language paclet overview page (the high-level table-of-contents page a paclet's Documentation index links to, like the built-in Overview pages, with TOCChapter / TOCSection / TOCSubsection heading hierarchy) as a literate-markdown document and build it with MarkdownToNotebook. Use this whenever the user wants to write or generate an overview page, a TOC page, a documentation index, or a paclet landing-page TOC for a Wolfram paclet - especially when the paclet has more than one guide / several tutorials / a large set of symbol pages and needs a navigable index.