[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E41RCK5YHJ7ERKZKM6DFQ9":3,"skill-same:01M6E41RCK5YHJ7ERKZKM6DFQ9":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6E41RCK5YHJ7ERKZKM6DFQ9","wolfram-setup",null,"Install and activate the Wolfram Engine, and set up the Wolfram MCP server (local or remote). Use when: installing Wolfram Engine, activating a Wolfram Engine license, setting up wolframscript, configuring the Wolfram MCP server for any AI assistant or coding client, or connecting to the free remote Wolfram MCP service.","WolframResearch\u002Fskills","WolframResearch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11549616?v=4","01M6E41JCSCYS27VBY50QF2Q66","Wolfram Research, Inc.","01M6E41JH6XYAVRJE6BEZB531E",20,"MIT","https:\u002F\u002Fgithub.com\u002FWolframResearch\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwolfram-setup\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"wolfram setup","setup","ai assistant","name","free","local","activate","up","use","install","engine","MCP","SET","specify","server","license","mcp client","windows","mcp server","linux","2026-11-10 10:12:30",false,"---\nname: wolfram-setup\ndescription: >\n  Install and activate the Wolfram Engine, and set up the Wolfram MCP server (local or remote).\n  Use when: installing Wolfram Engine, activating a Wolfram Engine license, setting up wolframscript,\n  configuring the Wolfram MCP server for any AI assistant or coding client,\n  or connecting to the free remote Wolfram MCP service.\nargument-hint: 'Optional: specify OS (macOS, Windows, Linux) and\u002For MCP client name'\n---\n\n# Wolfram Setup\n\nThis skill gets a user set up with Wolfram tools. The goal is a working Wolfram MCP server connected to their AI assistant or client environment. It works across any combination of LLM and client — chat interfaces, coding agents, terminal-integrated assistants, etc.\n\n## Step 1: Determine what kind of assistance is possible\n\nFirst, establish whether you can execute shell commands in this session.\n\n**If you can execute shell commands on the user's system** (coding agent, terminal-integrated assistant):  \nRun the smoke test and proceed interactively — go to Step 2A.\n\n**If you cannot execute shell commands on the user's system** (chat interface, read\u002Fwrite-only environment):  \nAll steps will be instructional. Ask the user to run commands and report results back to you — go to Step 2B.\n\n## Step 2A: Assess the user's installation (shell-capable)\n\nRun the following:\n\n```bash\nwolframscript -code 'Print[$InstallationDirectory]; Print[$Version];'\n```\n\nThree possible outcomes:\n\n- **Succeeds** → they have a local kernel. Go to Step 3.\n- **Fails, but a Wolfram app is present** → `wolframscript` may not be on PATH. Check before concluding nothing is installed:\n  - macOS: `\u002FApplications\u002FWolfram*.app`, `\u002FApplications\u002FMathematica.app`\n  - Windows: `C:\\Program Files\\Wolfram Research\\`\n  - Linux: `\u002Fusr\u002Flocal\u002FWolfram\u002F`\n\n  If a Wolfram app is found, guide the user to fix PATH or run `wolframscript -configure` — do not install a redundant Engine. See `references\u002Fget-wolfram-engine.md` § Advanced configuration.\n- **Fails, no Wolfram app found** → they have nothing. Go to Step 3 to choose a path.\n\n## Step 2B: Assess the user's installation (instructional mode)\n\nAsk the user: \"Do you have Mathematica, the Wolfram app, or the Wolfram Engine installed on your system?\"\n\n- **Yes** → they have a local kernel. Go to Step 3.\n- **No** → Go to Step 3 to choose a path.\n\n## Step 3: Get a Wolfram kernel (only if needed)\n\nIf the user already has a kernel, skip to Step 4. Otherwise, explain both options and let them choose:\n\n**Option A — Remote MCP service (quick, no install)**  \nNo software to install. The free remote service at `agenttools.wolfram.com\u002Fmcp` gives immediate access to Wolfram tools. The evaluator is stateless with fixed resource limits, but it's a great starting point. Skip to Step 4 and use Option 2 in `references\u002Fsetup-mcp-server.md`.\n\n**Option B — Wolfram Engine (local, more powerful)**  \nA full local kernel with stateful evaluation and no resource limits — better for computation-heavy work. Requires a free Wolfram ID and license. See `references\u002Fget-wolfram-engine.md` for platform-specific steps, including automated install commands (winget on Windows, brew on macOS). Key points:\n- The user must [create a Wolfram ID](https:\u002F\u002Faccount.wolfram.com\u002Flogin\u002Fcreate) and [obtain a free license](https:\u002F\u002Faccount.wolfram.com\u002Faccess\u002Fwolfram-engine\u002Ffree) themselves\n- Offer to run the platform installer automatically; always ask permission first\n- Activate with `wolframscript -activate` (run interactively if possible; otherwise relay to the user)\n- Each Wolfram ID supports 2 free activation keys; contact [support@wolfram.com](mailto:support@wolfram.com) to reset if needed\n- **Required verification:** after activation, run `wolframscript -code '1+1'` and confirm it prints `2` before proceeding to Step 4. On Windows in IDE environments, restart the editor first if `wolframscript` is not found.\n\n## Step 4: Set up the Wolfram MCP server\n\nRead `references\u002Fsetup-mcp-server.md` for full instructions. Summary:\n\n- **Has local kernel** → Option 1 (local server via `InstallMCPServer`). Ask which client they're using; the paclet picks the right tool bundle automatically, but an explicit server name can be passed if the user has a preference.\n- **No local kernel** → Option 2 (remote service at `agenttools.wolfram.com\u002Fmcp`). Add the URL to their client's MCP config — no API key needed.\n\nIn instructional mode, provide the exact commands and config snippets for the user to run themselves.\n\nAfter setup, ask the user to restart or reload their client.\n\n## Step 5: Verify\n\nConfirm the MCP server is working by asking the client to evaluate a simple Wolfram Language expression:\n\n```\nWhat is Expand[(x+1)^5] in Wolfram Language?\n```\n\nIf the MCP tools respond correctly, setup is complete.\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `wolframscript` not found after install (Windows\u002FIDE) | The new PATH entry isn't visible until the editor is restarted — restart VSCode\u002FJetBrains and try again before further troubleshooting |\n| `wolframscript` still not found after restart | Check PATH; run `wolframscript -kernelpath \u002Fpath\u002Fto\u002FWolframKernel` — see [support article](https:\u002F\u002Fsupport.wolfram.com\u002F47243) |\n| \"No valid keys\" on activation | Each Wolfram ID has 2 keys — [contact Wolfram](mailto:support@wolfram.com) to reset |\n| Activation fails behind a proxy | Set `https_proxy` environment variable before running `wolframscript` |\n| macOS Gatekeeper blocks the app | Right-click the `.app` → Open, then confirm in the security dialog |\n| MCP server not appearing in client | Restart the client; check MCP config JSON for syntax errors |\n| MCP server installed but not appearing in client | `InstallMCPServer` may have written to a different config path than the one the client reads. See `references\u002Fsetup-mcp-server.md` § Config path troubleshooting. |\n\nFor `wolframscript -configure` usage and advanced configuration keys, see `references\u002Fget-wolfram-engine.md` § Advanced configuration.\n\n## Technical Support\n\nContact Wolfram at [support@wolfram.com](mailto:support@wolfram.com).\n","# Wolfram Setup\n\nThis skill gets a user set up with Wolfram tools. The goal is a working Wolfram MCP server connected to their AI assistant or client environment. It works across any combination of LLM and client — chat interfaces, coding agents, terminal-integrated assistants, etc.\n\n## Step 1: Determine what kind of assistance is possible\n\nFirst, establish whether you can execute shell commands in this session.\n\n**If you can execute shell commands on the user's system** (coding agent, terminal-integrated assistant):  \nRun the smoke test and proceed interactively — go to Step 2A.\n\n**If you cannot execute shell commands on the user's system** (chat interface, read\u002Fwrite-only environment):  \nAll steps will be instructional. Ask the user to run commands and report results back to you — go to Step 2B.\n\n## Step 2A: Assess the user's installation (shell-capable)\n\nRun the following:\n\n```bash\nwolframscript -code 'Print[$InstallationDirectory]; Print[$Version];'\n```\n\nThree possible outcomes:\n\n- **Succeeds** → they have a local kernel. Go to Step 3.\n- **Fails, but a Wolfram app is present** → `wolframscript` may not be on PATH. Check before concluding nothing is installed:\n  - macOS: `\u002FApplications\u002FWolfram*.app`, `\u002FApplications\u002FMathematica.app`\n  - Windows: `C:\\Program Files\\Wolfram Research\\`\n  - Linux: `\u002Fusr\u002Flocal\u002FWolfram\u002F`\n\n  If a Wolfram app is found, guide the user to fix PATH or run `wolframscript -configure` — do not install a redundant Engine. See `references\u002Fget-wolfram-engine.md` § Advanced configuration.\n- **Fails, no Wolfram app found** → they have nothing. Go to Step 3 to choose a path.\n\n## Step 2B: Assess the user's installation (instructional mode)\n\nAsk the user: \"Do you have Mathematica, the Wolfram app, or the Wolfram Engine installed on your system?\"\n\n- **Yes** → they have a local kernel. Go to Step 3.\n- **No** → Go to Step 3 to choose a path.\n\n## Step 3: Get a Wolfram kernel (only if needed)\n\nIf the user already has a kernel, skip to Step 4. Otherwise, explain both options and let them choose:\n\n**Option A — Remote MCP service (quick, no install)**  \nNo software to install. The free remote service at `agenttools.wolfram.com\u002Fmcp` gives immediate access to Wolfram tools. The evaluator is stateless with fixed resource limits, but it's a great starting point. Skip to Step 4 and use Option 2 in `references\u002Fsetup-mcp-server.md`.\n\n**Option B — Wolfram Engine (local, more powerful)**  \nA full local kernel with stateful evaluation and no resource limits — better for computation-heavy work. Requires a free Wolfram ID and license. See `references\u002Fget-wolfram-engine.md` for platform-specific steps, including automated install commands (winget on Windows, brew on macOS). Key points:\n- The user must [create a Wolfram ID](https:\u002F\u002Faccount.wolfram.com\u002Flogin\u002Fcreate) and [obtain a free license](https:\u002F\u002Faccount.wolfram.com\u002Faccess\u002Fwolfram-engine\u002Ffree) themselves\n- Offer to run the platform installer automatically; always ask permission first\n- Activate with `wolframscript -activate` (run interactively if possible; otherwise relay to the user)\n- Each Wolfram ID supports 2 free activation keys; contact [support@wolfram.com](mailto:support@wolfram.com) to reset if needed\n- **Required verification:** after activation, run `wolframscript -code '1+1'` and confirm it prints `2` before proceeding to Step 4. On Windows in IDE environments, restart the editor first if `wolframscript` is not found.\n\n## Step 4: Set up the Wolfram MCP server\n\nRead `references\u002Fsetup-mcp-server.md` for full instructions. Summary:\n\n- **Has local kernel** → Option 1 (local server via `InstallMCPServer`). Ask which client they're using; the paclet picks the right tool bundle automatically, but an explicit server name can be passed if the user has a preference.\n- **No local kernel** → Option 2 (remote service at `agenttools.wolfram.com\u002Fmcp`). Add the URL to their client's MCP config — no API key needed.\n\nIn instructional mode, provide the exact commands and config snippets for the user to run themselves.\n\nAfter setup, ask the user to restart or reload their client.\n\n## Step 5: Verify\n\nConfirm the MCP server is working by asking the client to evaluate a simple Wolfram Language expression:\n\n```\nWhat is Expand[(x+1)^5] in Wolfram Language?\n```\n\nIf the MCP tools respond correctly, setup is complete.\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `wolframscript` not found after install (Windows\u002FIDE) | The new PATH entry isn't visible until the editor is restarted — restart VSCode\u002FJetBrains and try again before further troubleshooting |\n| `wolframscript` still not found after restart | Check PATH; run `wolframscript -kernelpath \u002Fpath\u002Fto\u002FWolframKernel` — see [support article](https:\u002F\u002Fsupport.wolfram.com\u002F47243) |\n| \"No valid keys\" on activation | Each Wolfram ID has 2 keys — [contact Wolfram](mailto:support@wolfram.com) to reset |\n| Activation fails behind a proxy | Set `https_proxy` environment variable before running `wolframscript` |\n| macOS Gatekeeper blocks the app | Right-click the `.app` → Open, then confirm in the security dialog |\n| MCP server not appearing in client | Restart the client; check MCP config JSON for syntax errors |\n| MCP server installed but not appearing in client | `InstallMCPServer` may have written to a different config path than the one the client reads. See `references\u002Fsetup-mcp-server.md` § Config path troubleshooting. |\n\nFor `wolframscript -configure` usage and advanced configuration keys, see `references\u002Fget-wolfram-engine.md` § Advanced configuration.\n\n## Technical Support\n\nContact Wolfram at [support@wolfram.com](mailto:support@wolfram.com).\n",{"name":5,"description":49,"argument-hint":50},"Install and activate the Wolfram Engine, and set up the Wolfram MCP server (local or remote). Use when: installing Wolfram Engine, activating a Wolfram Engine license, setting up wolframscript, configuring the Wolfram MCP server for any AI assistant or coding client, or connecting to the free remote Wolfram MCP service.\n","Optional: specify OS (macOS, Windows, Linux) and\u002For MCP client name","main","359f7770bdc49be4390669f9f96d0afd6822d88c","skills\u002Fwolfram-setup",1,"https:\u002F\u002Fgithub.com\u002FWolframResearch\u002Fskills","https:\u002F\u002Fgithub.com\u002FWolframResearch","https:\u002F\u002Fwolfram.com\u002Fopen-materials\u002F","2026-07-23 13:10:47",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add WolframResearch\u002Fskills --skill wolfram-setup",{"tool":65,"command":66},"bunx","bunx skills add WolframResearch\u002Fskills --skill wolfram-setup",{"tool":68,"command":69},"pnpm","pnpm dlx skills add WolframResearch\u002Fskills --skill wolfram-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWolframResearch\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwolfram-setup\u002FSKILL.md",true,[73,79],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fget-wolfram-engine.md","REFERENCE","参考文档",5307,"https:\u002F\u002Fgithub.com\u002FWolframResearch\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwolfram-setup\u002Freferences\u002Fget-wolfram-engine.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fsetup-mcp-server.md",6904,"https:\u002F\u002Fgithub.com\u002FWolframResearch\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwolfram-setup\u002Freferences\u002Fsetup-mcp-server.md",[84,94],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":91,"publishedAt":44},"01M6E41VKQMDFQY7XHRN2SCCDK","template-skill","Replace with description of the skill and when Claude should use it.","https:\u002F\u002Fgithub.com\u002FWolframResearch\u002Fskills\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[90],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,93,32],"template","template skill",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":101,"publishedAt":44},"01M6E41MBNMPJHVSN0D6S1G477","astro-observation-planner","Use this skill when both of these are present: (1) a night or time reference — \"tonight\", \"tomorrow\", \"this weekend\", \"Saturday night\", or any specific date; (2) observing intent — stargazing, skywatching, telescope or binocular use, wanting to know what's visible or \"up\", asking whether a specific object (planet, galaxy, nebula, cluster) can be seen, or planning any kind of sky-watching session. None of these needs to be stated formally — \"what's up from Austin tonight\" and \"going skywatching in Champaign tomorrow\" both qualify. Outputs twilight windows, Moon phase, planetary visibility, and a filtered deep-sky catalog. Do not trigger for general astronomy education, equipment setup, or conceptual questions lacking location + night + observing intent.","https:\u002F\u002Fgithub.com\u002FWolframResearch\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fastro-observation-planner\u002FSKILL.md",[100],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[102,103,104,105,106,107,108,109,110,111,112,35,113,31,32,114,115,116,41,117],"astro","planner","astro observation planner","intent","qualify","cluster","trigger","deep","time","location","do","general","catalog","session","planning","kernel"]