메뉴
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".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | publish-paclet |
| description | 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". |
Build a .paclet archive, install it locally, and upload it to Wolfram Cloud as a public object.
Produces a URL that anyone can use to install the paclet.
Prefer the AgentTools MCP (mcp__Wolfram__WolframLanguageEvaluator and the other mcp__Wolfram__* tools) for build, install, and cloud upload — it reuses one persistent kernel and consumes no extra license seat.
Only fall back to wolframscript if the MCP is unavailable, and before spawning it check headroom via the MCP:
With[{free = $MaxLicenseProcesses - $LicenseProcesses}, free]
If free <= 0, do not spawn wolframscript — it will fail with a license error.
Publish through the MCP instead, or tell the user a seat must be freed.
PacletInfo.wl files.Before publishing, verify:
PacletInfo.wl version.
If this is an update, the version should be higher than the last published version.
Ask the user if they want to bump it.mcp__Wolfram__CodeInspector is available, run it on each kernel file.
Otherwise skip.Tests/*.wlt), run them:
mcp__Wolfram__TestReport (if available via MCP)wolframscript -f <PacletName>/run_tests.wlsmcp__Wolfram__CreateSymbolDoc is available, offer to generate or update documentation notebooks for exported symbols before publishing.
Documentation is not bundled by default — pass --with-docs (see below) to include it in the published paclet.Build and install locally via the evaluator exactly as in the build-paclet skill (CreatePacletArchive + PacletInstall[..., ForceVersionInstall -> True] in the persistent kernel).
Keep the resulting archive path.
Run in the persistent kernel with mcp__Wolfram__WolframLanguageEvaluator — mirrors publish_paclet.wls:
CloudConnect[];
With[{obj = CloudObject["<PacletName>.paclet", Permissions -> "Public"]},
CopyFile["<archivePath>", obj, OverwriteTarget -> True];
First[obj]]
The returned string is the public cloud URL — stable across versions, since each publish overwrites the same cloud object.
Fallback (MCP unavailable, and a seat is free per the headroom check): run
wolframscript -f "${CLAUDE_PLUGIN_ROOT}/scripts/publish_paclet.wls" "<PacletName>"(orScripts/publish_paclet.wls; add--with-docsto bundleDocumentation/). The script prints=== PACLET_URL: <url> ===— extract the URL from that line.
After successful publish, report:
PacletInstall["<cloud-url>"]
If the paclet has a README.md, check whether the install URL in the Installation section matches the new cloud URL.
If not, offer to update it.
CloudConnect[] via the MCP (or wolframscript -c 'CloudConnect[]') interactively first.The paclet is uploaded as <PacletName>.paclet in the user's cloud home.
This means each publish overwrites the previous version at the same URL — the URL is stable across versions.
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.