菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Checks, builds, and submits Wolfram Language paclets. Use this skill when working on paclet packaging, release readiness, and paclet repository submission workflows.
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.
| name | wolfram-alpha |
| description | 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. |
| compatibility | Requires the Wolfram MCP server or wolframscript on PATH |
| metadata | {"author":"Wolfram Research","version":"2.1.28"} |
Query Wolfram|Alpha for computational answers and retrieve contextual information using semantic search.
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|Alpha MCP tools available in your tool list (e.g., mcp__WolframLanguage__WolframAlpha), 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 |
|---|---|
WolframAlphaContext | Retrieve contextual information about a topic via semantic search |
WolframAlpha | Query Wolfram|Alpha for computational answers and real-world data |
Always use WolframAlphaContext as a first step before querying WolframAlpha. It uses semantic search to retrieve relevant background information and helps ensure you have up-to-date context. The context argument should be written in natural language (not as a search query) and be as detailed as possible (up to 250 words).
If your MCP server provides a WolframContext tool, you can use that instead of WolframAlphaContext. It's effectively equivalent, except it may include additional context from Wolfram Language documentation.
Use WolframAlpha for natural language queries that need computational answers or real-world data. This is especially useful for questions about:
Queries should be phrased in natural language, similar to how you would ask a question. For example: "population of France", "integrate sin(x) from 0 to pi", "distance from Earth to Mars".
WolframAlphaContext before WolframAlpha to ensure you have the most up-to-date context for your query.sin(x), x^2, sqrt(x)).