Install skills

The script extracts the zip automatically, then installs everything in one run. Inside codev-office-windows.zip:

The script extracts the zip automatically, then installs everything in one run. Inside codev-office-ubuntu.zip:

There is one bundle per chip — download the one matching yours. Check via menu → About This Mac, or run uname -m in Terminal: arm64 means Apple Silicon (M1/M2/M3/M4), x86_64 means Intel.

One setup script serves both chips: it reads uname -m and uses whichever bundle is next to it, so there is nothing to choose beyond the zip above.

The script extracts the zip automatically. Each bundle carries only its own chip's builds — the file names below show both, but you will see just yours:

Everything in the Windows table above is installed by one script, which first extracts codev-office-windows.zip on its own. Then:

1. Run the following command in any PowerShell window to open an elevated ("Run as administrator") PowerShell:

   Start-Process powershell -Verb RunAs

2. cd into the folder holding the script and the zip, then run the install command:

   cd "<download-folder>"
   powershell -ExecutionPolicy Bypass -File .\codev-office-windows-setup.ps1

3. Wait for the green codev-office setup complete closing message.

Running non-elevated also works — the script continues, but each installer pops its own UAC prompt (a declined prompt skips that component; that is fatal only for the .NET SDK).

powershell -ExecutionPolicy Bypass -File .\codev-office-windows-setup.ps1 -TargetUser <your-username>

codevhub skill office --uninstall --skills-only --yes
codevhub skill office --target-user <their-username>

[Environment]::SetEnvironmentVariable("LANG","en_US.UTF-8","Machine")
[Environment]::SetEnvironmentVariable("LANG",$null,"User")

What the script does (after extracting codev-office-windows.zip on first run — re-runs reuse the extracted folder while it still matches the zip):

1. Installs the .NET SDK 8 (required), Git for Windows, pandoc and LibreOffice — and puts LibreOffice's soffice on the PATH for doc_to_docx.sh (machine PATH when elevated, user PATH otherwise).
2. Installs Python 3.14.6 when no Python 3.10–3.14 is on PATH, then pip-installs pandas + openpyxl, markitdown[pptx] and reportlab + pypdf + matplotlib from the bundled python-wheels folder (fully offline).
3. Installs Node.js when none ≥ v18 is present, unpacks the prebuilt PptxGenJS and Playwright module trees into one shared %PUBLIC%\codev-office\node_modules (identical for every account) with the NODE_PATH variable pointing at it — machine-wide when elevated, user scope otherwise — so require() resolves them from any folder; and unpacks Playwright's Chromium build into a shared %PUBLIC%\codev-office\ms-playwright cache, pointing the PLAYWRIGHT_BROWSERS_PATH variable at it (same scope rules) for pdf covers.
4. Copies nuget-offline-feed to the shared %PUBLIC%\codev-office\nuget-offline-feed and writes %APPDATA%\NuGet\NuGet.Config pointing only at it — for the account the script runs as and, when elevated as a different admin account, for the signed-in user too (an existing config is backed up to NuGet.Config.bak; re-runs detect the offline feed and leave both untouched).
5. Unzips minimax-docx-skill.zip, minimax-xlsx-skill.zip, pptx-generator-skill.zip and minimax-pdf-skill.zip into the skills folder and builds the docx skill's CLI offline.
6. Verifies the install by generating a test Word document, by packing and validating a test spreadsheet, by compiling a one-slide test deck with PptxGenJS, and by probing the pdf skill's Python/Playwright dependencies; on success it prints codev-office setup complete - the skills are ready.

When the script finishes, reboot the computer — the installers update the system PATH, and some of their changes only take full effect after a restart. After rebooting, Windows is done — CoDev Code picks up the skills (optionally run the Step 8 check). The Windows tabs in Steps 1–8 below are the full manual fallback: use them if the script fails partway or you prefer to install by hand — first unzip codev-office-windows.zip yourself; the steps use the files inside it. The manual steps produce exactly the same result as the script.

Everything in the Ubuntu table above is installed by one script, which first extracts codev-office-ubuntu.zip on its own. From the folder holding the script and the zip, run:

bash codev-office-ubuntu-setup.sh

No root is needed for the required parts — the .NET SDK installs per-user into ~/.dotnet (one optional sudo prompt symlinks it machine-wide; declining keeps a terminal-only install). The optional pandoc/LibreOffice .deb packages use sudo too (a declined password prompt skips that component). The script needs unzip (to unpack the bundle zip and the skill) and checks for it up front (usually preinstalled; else sudo apt install unzip).

What the script does (after extracting codev-office-ubuntu.zip on first run — re-runs reuse the extracted folder while it still matches the zip):

1. Extracts the .NET SDK 8 to ~/.dotnet, adds DOTNET_ROOT/PATH exports to ~/.bashrc, and symlinks /usr/local/bin/dotnet (one sudo prompt) so non-interactive shells find it too — CoDev Code's shell tool runs /bin/sh, which never reads ~/.bashrc. If libicu is missing (minimal server images) it enables DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 instead.
2. Installs the optional pandoc and LibreOffice .deb sets — and symlinks /usr/local/bin/soffice (the debs only create a versioned libreofficeX.Y link, never plain soffice).
3. Checks for a Python 3.10–3.14 python3 (Ubuntu ships one), then pip-installs pandas + openpyxl, markitdown[pptx] and reportlab + pypdf + matplotlib from the bundled python-wheels folder (fully offline, with a PEP 668 --break-system-packages fallback on Ubuntu 23.04+).
4. Extracts Node.js to ~/.node (adding it to ~/.bashrc and symlinking /usr/local/bin/node, like dotnet), unpacks the prebuilt PptxGenJS and Playwright module trees into one shared ~/.codev-office/node_modules, linked as ~/.node_modules — one of Node's global require() fallback folders, so require() resolves them from any directory without NODE_PATH — and unpacks Playwright's Chromium build into ~/.cache/ms-playwright for pdf covers.
5. Copies nuget-offline-feed to ~/nuget-offline-feed and writes NuGet's user-global ~/.nuget/NuGet/NuGet.Config pointing only at it (an existing config is backed up to NuGet.Config.bak; re-runs detect the offline feed and leave both untouched).
6. Unzips minimax-docx-skill.zip, minimax-xlsx-skill.zip, pptx-generator-skill.zip and minimax-pdf-skill.zip into the skills folder and builds the docx skill's CLI offline.
7. Verifies the install by generating a test Word document, by packing and validating a test spreadsheet, by compiling a one-slide test deck with PptxGenJS, and by running the pdf skill's make.sh check; on success it prints Verification passed - codev-office skills are ready.

When the script finishes, Ubuntu is done — restart CoDev Code to pick up the skills (optionally run the Step 8 check). The Ubuntu tabs in Steps 1–8 below are the full manual fallback: use them if the script fails partway or you prefer to install by hand — first unzip codev-office-ubuntu.zip yourself; the steps use the files inside it.

Everything in the macOS table above is installed by one script — it auto-detects your chip (uname -m), picks up whichever of the two bundles is next to it and extracts it on its own, so there is nothing to choose. From the folder holding the script and the zip, run:

bash codev-office-macos-setup.sh

The .NET SDK and pandoc .pkg installers use sudo — enter your admin password when prompted. A declined prompt skips that component; that is fatal only for the .NET SDK (it has no non-admin installer). LibreOffice installs by copying the app bundle, no admin needed.

What the script does (after extracting codev-office-macos-arm64.zip or codev-office-macos-x86_64.zip on first run — it reads uname -m to know which one to expect, and re-runs reuse the extracted folder while it still matches the zip):

1. Installs the .NET SDK 8 .pkg from the bundle, then symlinks /usr/local/bin/dotnet — the pkg only puts dotnet on PATH for login shells (via /etc/paths.d), and CoDev Code's shell tool runs /bin/sh non-interactively.
2. Installs pandoc, and LibreOffice from the .dmg — clearing the app's quarantine flag (Gatekeeper otherwise blocks the skill's headless soffice runs) and symlinking /usr/local/bin/soffice for doc_to_docx.sh.
3. Installs Python from the bundled universal2 .pkg when no suitable python3 is present (sudo prompt) — 3.14.6 on Apple Silicon (accepts an existing 3.10–3.14), 3.13.14 on Intel (accepts 3.10–3.13: onnxruntime, the native runtime behind markitdown, ships no Intel-mac wheels for Python 3.14) — then pip-installs pandas + openpyxl, markitdown[pptx] and reportlab + pypdf + matplotlib from the bundled python-wheels folder (fully offline).
4. Installs Node.js from the universal .pkg when none ≥ v18 is present (sudo prompt), unpacks the prebuilt PptxGenJS and Playwright module trees into one shared ~/.codev-office/node_modules, linked as ~/.node_modules — one of Node's global require() fallback folders, so require() resolves them from any directory without NODE_PATH — and unpacks Playwright's Chromium build into ~/Library/Caches/ms-playwright for pdf covers.
5. Copies nuget-offline-feed to ~/nuget-offline-feed and writes NuGet's user-global ~/.nuget/NuGet/NuGet.Config pointing only at it (an existing config is backed up to NuGet.Config.bak; re-runs detect the offline feed and leave both untouched).
6. Unzips minimax-docx-skill.zip, minimax-xlsx-skill.zip, pptx-generator-skill.zip and minimax-pdf-skill.zip into the skills folder and builds the docx skill's CLI offline.
7. Verifies the install by generating a test Word document, by packing and validating a test spreadsheet, by compiling a one-slide test deck with PptxGenJS, and by running the pdf skill's make.sh check; on success it prints Verification passed - codev-office skills are ready.

When the script finishes, macOS is done — restart CoDev Code to pick up the skills (optionally run the Step 8 check). The macOS tabs in Steps 1–8 below are the full manual fallback: use them if the script fails partway or you prefer to install by hand — first unzip your chip's bundle yourself; the steps use the files inside it, and only your chip's builds are present.

Handled by codev-office-windows-setup.ps1 — manual equivalent:

1. Run dotnet-sdk-8.0.423-win-x64.exe (bundle root) and click Install (needs Admin rights).
2. Open a new Command Prompt (it must be new to pick up PATH) and check:

dotnet --list-sdks

The list must include an 8.0.x entry.

Handled by codev-office-ubuntu-setup.sh — manual equivalent:

The tar.gz build needs no root — extract and run:

mkdir -p $HOME/.dotnet
tar -xzf dotnet-sdk-8.0.423-linux-x64.tar.gz -C $HOME/.dotnet
 
# Add to PATH permanently
echo 'export DOTNET_ROOT=$HOME/.dotnet'      >> ~/.bashrc
echo 'export PATH=$HOME/.dotnet:$PATH'       >> ~/.bashrc
source ~/.bashrc
 
# ~/.bashrc only applies to interactive bash — CoDev Code's shell tool runs
# /bin/sh non-interactively and never reads it, so also symlink dotnet
# machine-wide (it resolves its install root through the symlink):
sudo ln -sf "$HOME/.dotnet/dotnet" /usr/local/bin/dotnet
 
# Check
dotnet --list-sdks    # must list an 8.0.x entry

Handled by codev-office-macos-setup.sh — manual equivalent:

1. Identify your chip — it decides which bundle you download, and the file names inside it. Check via menu → About This Mac, or run uname -m in Terminal:

2. Open the .NET SDK .pkg in the bundle root — only your chip's build is there:
   • Apple Silicon: dotnet-sdk-8.0.423-osx-arm64.pkg
   • Intel: dotnet-sdk-8.0.423-osx-x64.pkg
3. Install via the wizard (an admin password is required).
4. The pkg only puts dotnet on PATH for login shells (via /etc/paths.d) — CoDev Code's shell tool runs /bin/sh non-interactively, so also symlink it machine-wide:

sudo ln -sf /usr/local/share/dotnet/dotnet /usr/local/bin/dotnet

5. Open a new Terminal and check:

dotnet --list-sdks    # must list an 8.0.x entry

Handled by codev-office-windows-setup.ps1 — manual equivalent:

1. Run Git-2.55.0.3-64-bit.exe (bundle root), keep every default option, Next all the way.
2. After installing, right-click in any folder → Open Git Bash here to open Git Bash.

Why it's needed: the skill's operational scripts (env_check.sh, docx_preview.sh, doc_to_docx.sh) are bash scripts, and Windows needs Git Bash (or WSL) to run them — CoDev Code's shell tool finds bash.exe relative to git on PATH.

Not needed — Ubuntu already ships bash. Skip this step.

Not needed — macOS already ships bash. Skip this step.

Handled by codev-office-windows-setup.ps1 — manual equivalent:

1. Unzip minimax-docx-skill.zip to %USERPROFILE%\.claude\skills\minimax-docx and minimax-xlsx-skill.zip to %USERPROFILE%\.claude\skills\minimax-xlsx — the global skills folder, so the skills are available in every project. Both Claude Code and CoDev Code read skills from %USERPROFILE%\.claude\skills\<name>\SKILL.md. A project-scoped install (<project>\.claude\skills\) also works, but this guide installs globally.

2. Copy the nuget-offline-feed folder to a stable machine-wide path, e.g. C:\nuget-offline-feed. On Windows the feed carries 6 packages — the 4 above plus documentformat.openxml.3.2.0.nupkg and documentformat.openxml.framework.3.2.0.nupkg, the version the skill's C# scripting scaffold (SKILL.md) pins.

3. Create %APPDATA%\NuGet\NuGet.Config (back up any existing file first) containing:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="offline" value="C:\nuget-offline-feed" />
  </packageSources>
</configuration>

%APPDATA%\NuGet\NuGet.Config is NuGet's user-global config, so the offline feed resolves no matter which folder a build runs from — required here, because the skill lives in the global skills folder rather than inside any project. Note <clear /> disables nuget.org for every build under this user account until the original config is restored.

4. Build the skill's CLI (Command Prompt or Git Bash, from the skill folder). First create a global.json in scripts\dotnet pinning the build to SDK 8 — without it, a newer SDK on the machine wins the version pick and tries to fetch the net8.0 targeting packs from NuGet (NU1101). File content:

{ "sdk": { "version": "8.0.100", "rollForward": "latestFeature" } }

cd %USERPROFILE%\.claude\skills\minimax-docx\scripts\dotnet
dotnet restore MiniMaxAIDocx.Cli\MiniMaxAIDocx.Cli.csproj
dotnet build MiniMaxAIDocx.Cli\MiniMaxAIDocx.Cli.csproj --no-restore

Both commands must finish without errors.

Handled by codev-office-ubuntu-setup.sh — manual equivalent:

1. Unzip minimax-docx-skill.zip and minimax-xlsx-skill.zip to ~/.claude/skills/ — the global skills folder, so the skills are available in every project. Both Claude Code and CoDev Code read skills from ~/.claude/skills/<name>/SKILL.md. A project-scoped install (<project>/.claude/skills/) also works, but this guide installs globally.

mkdir -p ~/.claude/skills
unzip minimax-docx-skill.zip -d /tmp/skills-unzip
unzip minimax-xlsx-skill.zip -d /tmp/skills-unzip
mv /tmp/skills-unzip/minimax-docx ~/.claude/skills/minimax-docx
mv /tmp/skills-unzip/minimax-xlsx ~/.claude/skills/minimax-xlsx

2. Copy the nuget-offline-feed folder to a stable path, e.g. ~/nuget-offline-feed. The feed carries 6 packages — the 4 above plus documentformat.openxml.3.2.0.nupkg and documentformat.openxml.framework.3.2.0.nupkg, the version the skill's C# scripting scaffold (SKILL.md) pins.

3. Create ~/.nuget/NuGet/NuGet.Config (back up any existing file first) — this is NuGet's user-global config, so the offline feed resolves no matter which folder a build runs from. Use an absolute path: ~ is not expanded.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="offline" value="/home/YOUR_USER/nuget-offline-feed" />
  </packageSources>
</configuration>

Note <clear /> disables nuget.org for every build under this user account until the original config is restored.

4. Build the skill's CLI. First create a global.json in scripts/dotnet pinning the build to SDK 8 — without it, a newer SDK on the machine wins the version pick and tries to fetch the net8.0 targeting packs from NuGet (NU1101):

cd ~/.claude/skills/minimax-docx/scripts/dotnet
printf '%s\n' '{ "sdk": { "version": "8.0.100", "rollForward": "latestFeature" } }' > global.json
dotnet restore MiniMaxAIDocx.Cli/MiniMaxAIDocx.Cli.csproj
dotnet build MiniMaxAIDocx.Cli/MiniMaxAIDocx.Cli.csproj --no-restore

Both commands must finish without errors.

Handled by codev-office-macos-setup.sh — manual equivalent:

1. Unzip minimax-docx-skill.zip and minimax-xlsx-skill.zip to ~/.claude/skills/ — the global skills folder, so the skills are available in every project. Both Claude Code and CoDev Code read skills from ~/.claude/skills/<name>/SKILL.md. A project-scoped install (<project>/.claude/skills/) also works, but this guide installs globally.

mkdir -p ~/.claude/skills
unzip minimax-docx-skill.zip -d /tmp/skills-unzip
unzip minimax-xlsx-skill.zip -d /tmp/skills-unzip
mv /tmp/skills-unzip/minimax-docx ~/.claude/skills/minimax-docx
mv /tmp/skills-unzip/minimax-xlsx ~/.claude/skills/minimax-xlsx

2. Copy the nuget-offline-feed folder to a stable path, e.g. ~/nuget-offline-feed. The feed carries 6 packages — the 4 above plus documentformat.openxml.3.2.0.nupkg and documentformat.openxml.framework.3.2.0.nupkg, the version the skill's C# scripting scaffold (SKILL.md) pins.

3. Create ~/.nuget/NuGet/NuGet.Config (back up any existing file first) — this is NuGet's user-global config, so the offline feed resolves no matter which folder a build runs from. Use an absolute path: ~ is not expanded.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="offline" value="/Users/YOUR_USER/nuget-offline-feed" />
  </packageSources>
</configuration>

Note <clear /> disables nuget.org for every build under this user account until the original config is restored.

4. Build the skill's CLI. First create a global.json in scripts/dotnet pinning the build to SDK 8 — without it, a newer SDK on the machine wins the version pick and tries to fetch the net8.0 targeting packs from NuGet (NU1101):

cd ~/.claude/skills/minimax-docx/scripts/dotnet
printf '%s\n' '{ "sdk": { "version": "8.0.100", "rollForward": "latestFeature" } }' > global.json
dotnet restore MiniMaxAIDocx.Cli/MiniMaxAIDocx.Cli.csproj
dotnet build MiniMaxAIDocx.Cli/MiniMaxAIDocx.Cli.csproj --no-restore

Both commands must finish without errors.

Handled by codev-office-windows-setup.ps1 — manual equivalent:

Run pandoc-3.10.1-windows-x86_64.msi (bundle root), Next all the way. Check in a new terminal: pandoc --version.

Handled by codev-office-ubuntu-setup.sh — manual equivalent:

sudo dpkg -i pandoc-3.10.1-1-amd64.deb
pandoc --version

Handled by codev-office-macos-setup.sh — manual equivalent:

Open the .pkg matching your chip (bundle root) and install via the wizard:

• Apple Silicon: pandoc-3.10.1-arm64-macOS.pkg
• Intel: pandoc-3.10.1-x86_64-macOS.pkg

Check: pandoc --version

Handled by codev-office-windows-setup.ps1 (including the PATH step) — manual equivalent:

1. Run LibreOffice_26.2.5_Win_x86-64.msi (bundle root) → choose Typical.
2. The skill's doc_to_docx.sh finds LibreOffice only via soffice on PATH, so add it:
   • Open Settings → System → About → Advanced system settings → Environment Variables
   • Edit the Path variable (User or System) and add: C:\Program Files\LibreOffice\program
3. Check in a new terminal: soffice --version.

Handled by codev-office-ubuntu-setup.sh (including the symlink) — manual equivalent:

LibreOffice's official .deb set is fully bundled — no dependencies to download:

tar -xzf LibreOffice_26.2.5_Linux_x86-64_deb.tar.gz
cd LibreOffice_26.2.5*_Linux_x86-64_deb/DEBS
sudo dpkg -i *.deb
 
# The debs only create a versioned `libreoffice26.2` link, but the skill's
# doc_to_docx.sh finds LibreOffice only via `soffice` on PATH — create a symlink:
sudo ln -sf /opt/libreoffice26.2/program/soffice /usr/local/bin/soffice
soffice --version

Handled by codev-office-macos-setup.sh (including the quarantine and symlink steps) — manual equivalent:

1. Open the .dmg matching your chip (bundle root):
   • Apple Silicon: LibreOffice_26.2.5_MacOS_aarch64.dmg
   • Intel: LibreOffice_26.2.5_MacOS_x86-64.dmg
2. Drag LibreOffice into the Applications folder.
3. Clear the quarantine flag — Gatekeeper otherwise blocks the skill's headless soffice runs, since the app was downloaded outside the App Store and is never launched in the GUI (right-clicking the app → Open once also works):

xattr -dr com.apple.quarantine /Applications/LibreOffice.app

4. The skill's doc_to_docx.sh finds LibreOffice only via soffice on PATH — create a symlink:

sudo mkdir -p /usr/local/bin
sudo ln -sf /Applications/LibreOffice.app/Contents/MacOS/soffice /usr/local/bin/soffice
soffice --version

Handled by codev-office-windows-setup.ps1 — manual equivalent:

1. Check for a real Python with the py launcher — not bare python: with LibreOffice installed (Step 5), its folder on PATH ships its own python.exe (3.12) that masquerades as a system Python, and the Microsoft Store stub is another impostor — the py launcher exists only for real python.org installs. If py --version is missing or outside 3.10–3.14, run python-3.14.6-amd64.exe (bundle root) and tick Add python.exe to PATH.
2. Install the packages offline from the bundle's python-wheels folder:

py -m pip install --no-index --find-links .\python-wheels pandas openpyxl "markitdown[pptx]" reportlab pypdf matplotlib
py -c "import pandas, openpyxl, markitdown, reportlab, pypdf; print('OK')"

Handled by codev-office-ubuntu-setup.sh — manual equivalent:

Ubuntu ships python3 (20.04 = 3.8 is too old — upgrade it first; 22.04 = 3.10 and 24.04 = 3.12 are fine). Install the packages offline:

python3 -m pip install --user --no-index --find-links ./python-wheels pandas openpyxl 'markitdown[pptx]' reportlab pypdf matplotlib
# Ubuntu 23.04+ (PEP 668) refuses installs into the system Python — add:
#   --break-system-packages
python3 -c "import pandas, openpyxl, markitdown, reportlab, pypdf; print('OK')"

If pip itself is missing, install python3-pip via apt.

Handled by codev-office-macos-setup.sh — manual equivalent:

1. If python3 --version is missing or outside the supported range — 3.10–3.14 on Apple Silicon, 3.10–3.13 on Intel (Intel Macs have no markitdown/onnxruntime support on 3.14) — open the .pkg matching your chip (bundle root, both universal2): Apple Silicon python-3.14.6-macos11.pkg, Intel python-3.13.14-macos11.pkg, and install via the wizard.
2. Install the packages offline from the bundle's python-wheels folder:

python3 -m pip install --user --no-index --find-links ./python-wheels pandas openpyxl 'markitdown[pptx]' reportlab pypdf matplotlib
python3 -c "import pandas, openpyxl, markitdown, reportlab, pypdf; print('OK')"

Handled by codev-office-windows-setup.ps1 — manual equivalent:

1. If node --version is missing (or below v18), run node-v24.15.0-x64.msi (bundle root), Next all the way.
2. Extract pptxgenjs-node-modules.zip and playwright-node-modules.zip and merge both node_modules contents into C:\Users\Public\codev-office\node_modules, then point the user NODE_PATH environment variable at that folder (Settings → System → About → Advanced system settings → Environment Variables → New under "User variables").
3. Extract ms-playwright-chromium.zip into %LOCALAPPDATA%\ms-playwright (the browser Playwright launches for pdf covers).
4. Check in a new terminal:

node -e "console.log(require('pptxgenjs') && require('playwright') ? 'OK' : 'FAIL')"

Handled by codev-office-ubuntu-setup.sh — manual equivalent:

# Node.js, per-user (no root):
mkdir -p ~/.node
tar -xzf node-v24.15.0-linux-x64.tar.gz -C ~/.node --strip-components=1
echo 'export PATH=$HOME/.node/bin:$PATH' >> ~/.bashrc
source ~/.bashrc
# CoDev Code's shell tool never reads ~/.bashrc — symlink node machine-wide:
sudo ln -sf "$HOME/.node/bin/node" /usr/local/bin/node
 
# PptxGenJS + Playwright, prebuilt — merged into one tree linked as
# ~/.node_modules, one of Node's global require() fallback folders, so
# require() works from any directory without NODE_PATH:
mkdir -p ~/.codev-office/node_modules /tmp/js-modules/pptx /tmp/js-modules/pw
unzip -q pptxgenjs-node-modules.zip -d /tmp/js-modules/pptx
unzip -q playwright-node-modules.zip -d /tmp/js-modules/pw
cp -R /tmp/js-modules/pptx/node_modules/. ~/.codev-office/node_modules/
cp -R /tmp/js-modules/pw/node_modules/. ~/.codev-office/node_modules/
ln -sfn ~/.codev-office/node_modules ~/.node_modules
 
# Chromium for Playwright (pdf cover rendering):
mkdir -p ~/.cache/ms-playwright
unzip -q ms-playwright-chromium.zip -d ~/.cache/ms-playwright
 
# Check:
node -e "console.log(require('pptxgenjs') && require('playwright') ? 'OK' : 'FAIL')"

Handled by codev-office-macos-setup.sh — manual equivalent:

1. If node --version is missing (or below v18), open node-v24.15.0.pkg (bundle root — one universal build for both chips) and install via the wizard (admin password required). The pkg installs to /usr/local/bin, which non-interactive shells already have on PATH.
2. Install the prebuilt module trees and Chromium:

mkdir -p ~/.codev-office/node_modules /tmp/js-modules/pptx /tmp/js-modules/pw
unzip -q pptxgenjs-node-modules.zip -d /tmp/js-modules/pptx
unzip -q playwright-node-modules.zip -d /tmp/js-modules/pw
cp -R /tmp/js-modules/pptx/node_modules/. ~/.codev-office/node_modules/
cp -R /tmp/js-modules/pw/node_modules/. ~/.codev-office/node_modules/
ln -sfn ~/.codev-office/node_modules ~/.node_modules
 
# Chromium for Playwright (pdf cover rendering):
mkdir -p ~/Library/Caches/ms-playwright
unzip -q ms-playwright-chromium.zip -d ~/Library/Caches/ms-playwright
 
# Check:
node -e "console.log(require('pptxgenjs') && require('playwright') ? 'OK' : 'FAIL')"

After a manual install, first reboot the computer — the installers update the system PATH, and some of their changes only take full effect after a restart.

If you used codev-office-windows-setup.ps1, the skill is already built and verified — this check is an optional extra. Open Git Bash, cd into the skill folder and run:

cd ~/.claude/skills/minimax-docx
bash scripts/env_check.sh

Expected result: [OK] lines for dotnet and project and a final READY. If it says NOT READY: review Step 1 and Step 3 (the most common cause is NuGet not pointing at the offline folder, or the CLI not yet built — the check's automatic rebuild uses the folder form of dotnet restore, which fails on SDK 8, so run the Step 3 build commands first).

For a manual end-to-end test — the same thing the script's verification step does — generate a document:

cd ~/.claude/skills/minimax-docx/scripts/dotnet
dotnet run --project MiniMaxAIDocx.Cli -- create --type report --output "$TEMP/offline-test.docx" --title "Offline Test"

And for the xlsx skill (pack the bundled template, then validate it — pure Python stdlib, exit code 0 means PASS):

cd ~/.claude/skills/minimax-xlsx
py scripts/xlsx_pack.py templates/minimal_xlsx "$TEMP/offline-test.xlsx"
py scripts/formula_check.py "$TEMP/offline-test.xlsx"

And for the pptx skill (compile a one-slide deck — needs Node.js + PptxGenJS from Step 7; open a new terminal so NODE_PATH is set):

PPTX_OUT="$TEMP/offline-test.pptx" node -e 'const P=require("pptxgenjs");const p=new P();p.layout="LAYOUT_16x9";p.addSlide().addText("Offline Test",{x:1,y:1,w:8,h:1});p.writeFile({fileName:process.env.PPTX_OUT});'

And for the pdf skill (its own dependency doctor — every line should be ✓):

bash ~/.claude/skills/minimax-pdf/scripts/make.sh check

(py is the Python launcher — unlike bare python, it can never resolve to LibreOffice's bundled interpreter.)

If the xlsx check fails with UnicodeEncodeError, the installed skill predates the console-encoding fix — run export PYTHONUTF8=1 in the same Git Bash session and retry, or re-run the setup script with -ForceSkills to update the skill to the current bundle.

Both commands must finish without errors and create the files.

If you used codev-office-ubuntu-setup.sh, the skill is already built and verified — this check is an optional extra:

cd ~/.claude/skills/minimax-docx
bash scripts/env_check.sh

Expected result: [OK] for dotnet and project and a final status of READY. If it says NOT READY: the most common cause is NuGet not pointing at the offline folder (Step 3), dotnet missing from PATH (open a new terminal or run source ~/.bashrc), or the CLI not yet built — the check's automatic rebuild uses the folder form of dotnet restore, which fails on SDK 8, so run the Step 3 build commands first.

For a manual end-to-end test — the same thing the script's verification step does — generate a document:

cd ~/.claude/skills/minimax-docx/scripts/dotnet
dotnet run --project MiniMaxAIDocx.Cli -- create --type report --output /tmp/offline-test.docx --title "Offline Test"

And for the xlsx skill (pack the bundled template, then validate it — pure Python stdlib, exit code 0 means PASS):

cd ~/.claude/skills/minimax-xlsx
python3 scripts/xlsx_pack.py templates/minimal_xlsx /tmp/offline-test.xlsx
python3 scripts/formula_check.py /tmp/offline-test.xlsx

And for the pptx skill (compile a one-slide deck — needs Node.js + PptxGenJS from Step 7):

PPTX_OUT=/tmp/offline-test.pptx node -e 'const P=require("pptxgenjs");const p=new P();p.layout="LAYOUT_16x9";p.addSlide().addText("Offline Test",{x:1,y:1,w:8,h:1});p.writeFile({fileName:process.env.PPTX_OUT});'

And for the pdf skill (its own dependency doctor — every line should be ✓):

bash ~/.claude/skills/minimax-pdf/scripts/make.sh check

Both commands must finish without errors and create the files.

If you used codev-office-macos-setup.sh, the skill is already built and verified — this check is an optional extra (macOS already ships bash/zip/unzip, so run it directly):

cd ~/.claude/skills/minimax-docx
bash scripts/env_check.sh

Expected result: [OK] for dotnet and project and a final status of READY. If it says NOT READY: the most common cause is NuGet not pointing at the offline folder (Step 3), or the CLI not yet built — the check's automatic rebuild uses the folder form of dotnet restore, which fails on SDK 8, so run the Step 3 build commands first.

For a manual end-to-end test — the same thing the script's verification step does — generate a document:

cd ~/.claude/skills/minimax-docx/scripts/dotnet
dotnet run --project MiniMaxAIDocx.Cli -- create --type report --output /tmp/offline-test.docx --title "Offline Test"

And for the xlsx skill (pack the bundled template, then validate it — pure Python stdlib, exit code 0 means PASS):

cd ~/.claude/skills/minimax-xlsx
python3 scripts/xlsx_pack.py templates/minimal_xlsx /tmp/offline-test.xlsx
python3 scripts/formula_check.py /tmp/offline-test.xlsx

And for the pptx skill (compile a one-slide deck — needs Node.js + PptxGenJS from Step 7):

PPTX_OUT=/tmp/offline-test.pptx node -e 'const P=require("pptxgenjs");const p=new P();p.layout="LAYOUT_16x9";p.addSlide().addText("Offline Test",{x:1,y:1,w:8,h:1});p.writeFile({fileName:process.env.PPTX_OUT});'

And for the pdf skill (its own dependency doctor — every line should be ✓):

bash ~/.claude/skills/minimax-pdf/scripts/make.sh check

Both commands must finish without errors and create the files.