메뉴
Checks, builds, and submits Wolfram Language paclets. Use this skill when working on paclet packaging, release readiness, and paclet repository submission workflows.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | wolfram-paclets |
| description | Checks, builds, and submits Wolfram Language paclets. Use this skill when working on paclet packaging, release readiness, and paclet repository submission workflows. |
| compatibility | Requires the Wolfram MCP server or wolframscript on PATH |
| metadata | {"author":"Wolfram Research","version":"2.1.28"} |
Paclet development and release workflow tools for checking, building, and submitting Wolfram Language paclets.
These scripts require wolframscript. If it is not installed or not on your PATH, read references/GetWolframEngine.md (relative to this skill directory) for installation instructions.
If you have Wolfram paclet tools available in your tool list (e.g., mcp__WolframLanguage__CheckPaclet), use those directly. They provide richer integration and better performance than the bundled scripts.
For a richer experience, consider setting up the Wolfram MCP server. See references/SetUpWolframMCPServer.md (relative to this skill directory) for instructions.
If no MCP tools are available, use the bundled scripts in the scripts/ directory (relative to this skill directory). Run them with:
wolframscript -f scripts/<ScriptName>.wls <arguments>
Pass --usage to any script to see its argument documentation:
wolframscript -f scripts/<ScriptName>.wls --usage
For detailed usage, arguments, and invocation syntax for each script, see references/Scripts.md (relative to this skill directory).
Reminder: These scripts are only relevant when you do not have the equivalent MCP tool available.
| Script | When to use |
|---|---|
CheckPaclet | Check a paclet for issues before building or submitting |
BuildPaclet | Build a .paclet archive from a paclet directory |
SubmitPaclet | Submit a paclet to the Wolfram Language Paclet Repository |
Use CheckPaclet before building or submitting a paclet. It reports errors, warnings, and suggestions organized by severity. The path should be an absolute path to the paclet root directory or the definition notebook (.nb) file.
Use BuildPaclet to produce a .paclet archive. Optionally pass --check true to run CheckPaclet before building. The build is aborted if errors are found.
Use SubmitPaclet to submit a paclet to the Wolfram Language Paclet Repository. This builds the paclet internally before submitting. Requires prior authentication via $PublisherID or an active Wolfram Cloud connection. Use CheckPaclet first to verify readiness.
CheckPaclet first, then BuildPaclet, and only then SubmitPaclet for a reliable release flow.Queries Wolfram|Alpha for up-to-date computational results and retrieves contextual information via semantic search. Use this skill when the user needs real-world data, calculations, or factual answers about entities in science, math, geography, history, finance, and more.
Evaluates Wolfram Language code, searches documentation, inspects code, runs tests, and retrieves symbol definitions. Use this skill when the user needs Wolfram Language computation or development assistance, including symbolic math, data analysis, visualization, or working with .wl/.wls/.wlt files.
Reads and writes Wolfram notebook (.nb) files. Use this skill when the user needs to create, read, or convert Wolfram notebooks, including converting between markdown and notebook format.
Add a new custom CodeInspector rule to detect problematic Wolfram Language patterns. Use when asked to: "add a code inspector rule", "create an inspection rule", "add a lint rule", "detect [pattern] in code inspector", "add CodeInspector rule", "new code analysis rule".
Generate a TODO task list from a design specification. Reads a spec file from Specs/, explores the codebase to identify what's already implemented vs. what remains, and produces a markdown TODO file with checkboxes in TODO/. Use when asked to: "create a task list from a spec", "make a TODO from a spec", "what needs to be done for [feature]", "generate tasks from the spec", "create a work plan for [feature]", "turn this spec into a checklist", or any request to break a specification into trackable work items.
Review a design specification in Specs/ against the actual codebase to find inaccuracies, potential issues, or things that need correction before implementation. Use when asked to: "review a spec", "check a spec for issues", "validate a spec", "find problems in a spec", "review the spec for [feature]", "audit a spec against the codebase", or any request to verify that a specification accurately reflects the current code and conventions.