How do I install the Webcode Local Windows Tts Installer skill?

Run npx skillmds@latest add shuyu-labs/webcode-local-windows-tts-installer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Webcode Local Windows Tts Installer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Webcode Local Windows Tts Installer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Webcode Local Windows Tts Installer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Webcode Local Windows Tts Installer?

shuyu-labs (@shuyu-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Webcode Local Windows Tts Installer by shuyu-labs

Name: Webcode Local Windows Tts Installer
Author: shuyu-labs

Webcode Local Windows Tts Installer

Use when building a local Windows WebCode installer from this repo for machine testing, especially when the package must bundle the Kokoro or sherpa-onnx Reply TTS service, model files, ffmpeg, a private Python runtime, and non-system-drive deployment without publishing a GitHub Release.

shuyu-labs a107ec7 2 files · 7.0 KB Updated Sep 17, 2026

File contents

WebCode Local Windows TTS Installer

Overview

Build the local WebCode Windows installer and portable ZIP with the bundled Reply TTS payload. Use this skill for local validation and handoff artifacts, not for branch push, tag push, or GitHub Release asset sync.

For GitHub publishing, use webcode-github-release instead.

Workflow

Confirm the current checkout is the WebCode repo, or pass -RepoRoot.
Prefer Debug when the user wants to try the installer locally before cleanup. Use Release only when the user asks for release-grade artifacts.
Run scripts/build-local-installer.ps1 from this skill instead of reconstructing the command by hand.
Report the generated installer, portable ZIP, checksums, and release notes from artifacts/windows-installer/vX.Y.Z/.
If the user asks for runtime verification, smoke-test the generated tts-bundle by starting tools/sherpa-kokoro-service/start.ps1 against it and checking http://127.0.0.1:<port>/health.

Command

Default local build:

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/build-local-installer.ps1

Explicit repo root and release build:

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/build-local-installer.ps1 `
  -RepoRoot "D:\VSWorkshop\WebCode" `
  -Configuration Release

Override the TTS payload source root if autodetection picks the wrong drive:

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/build-local-installer.ps1 `
  -ReplyTtsSourceRoot "E:\WebCodeData\Kokoro"

Rules

Treat Directory.Build.props as the version source of truth.
Treat tools/build-windows-installer.ps1 as the single source of truth for packaging behavior. Fix that script instead of adding ad hoc shell steps.
Expect the TTS source root to be a complete payload root containing models\kokoro-int8-multi-lang-v1_1, venv\Scripts\python.exe, and a bundled python\ directory.
Do not rely on a target-machine Python installation. The local installer path for this workflow is the bundled private runtime plus the bundled venv.
Do not move the TTS payload onto the Windows system drive. The installer must target a writable non-system fixed drive and fail clearly otherwise.
If multiple non-system drives exist and autodetection chooses the wrong one, rerun with -ReplyTtsSourceRoot.
Expect the artifact set to be WebCode-Setup-vX.Y.Z-win-x64.exe, WebCode-vX.Y.Z-win-x64-portable.zip, SHA256SUMS.txt, and RELEASE_NOTES.md.

Files

Skill wrapper: scripts/build-local-installer.ps1
Repo build script: <RepoRoot>\tools\build-windows-installer.ps1
Installer definition: <RepoRoot>\installer\windows\WebCode.iss
TTS service payload: <RepoRoot>\tools\sherpa-kokoro-service\

---name: webcode-local-windows-tts-installerdescription: Use when building a local Windows WebCode installer from this repo for machine testing, especially when the package must bundle the Kokoro or sherpa-onnx Reply TTS service, model files, ffmpeg, a private Python runtime, and non-system-drive deployment without publishing a GitHub Release.---# WebCode Local Windows TTS Installer## OverviewBuild the local WebCode Windows installer and portable ZIP with the bundled Reply TTS payload. Use this skill for local validation and handoff artifacts, not for branch push, tag push, or GitHub Release asset sync.For GitHub publishing, use `webcode-github-release` instead.## Workflow1. Confirm the current checkout is the WebCode repo, or pass `-RepoRoot`.2. Prefer `Debug` when the user wants to try the installer locally before cleanup. Use `Release` only when the user asks for release-grade artifacts.3. Run `scripts/build-local-installer.ps1` from this skill instead of reconstructing the command by hand.4. Report the generated installer, portable ZIP, checksums, and release notes from `artifacts/windows-installer/vX.Y.Z/`.5. If the user asks for runtime verification, smoke-test the generated `tts-bundle` by starting `tools/sherpa-kokoro-service/start.ps1` against it and checking `http://127.0.0.1:<port>/health`.## CommandDefault local build:```powershellpowershell -NoProfile -ExecutionPolicy Bypass -File scripts/build-local-installer.ps1```Explicit repo root and release build:```powershellpowershell -NoProfile -ExecutionPolicy Bypass -File scripts/build-local-installer.ps1 ` -RepoRoot "D:\VSWorkshop\WebCode" ` -Configuration Release```Override the TTS payload source root if autodetection picks the wrong drive:```powershellpowershell -NoProfile -ExecutionPolicy Bypass -File scripts/build-local-installer.ps1 ` -ReplyTtsSourceRoot "E:\WebCodeData\Kokoro"```## Rules- Treat `Directory.Build.props` as the version source of truth.- Treat `tools/build-windows-installer.ps1` as the single source of truth for packaging behavior. Fix that script instead of adding ad hoc shell steps.- Expect the TTS source root to be a complete payload root containing `models\kokoro-int8-multi-lang-v1_1`, `venv\Scripts\python.exe`, and a bundled `python\` directory.- Do not rely on a target-machine Python installation. The local installer path for this workflow is the bundled private runtime plus the bundled venv.- Do not move the TTS payload onto the Windows system drive. The installer must target a writable non-system fixed drive and fail clearly otherwise.- If multiple non-system drives exist and autodetection chooses the wrong one, rerun with `-ReplyTtsSourceRoot`.- Expect the artifact set to be `WebCode-Setup-vX.Y.Z-win-x64.exe`, `WebCode-vX.Y.Z-win-x64-portable.zip`, `SHA256SUMS.txt`, and `RELEASE_NOTES.md`.## Files- Skill wrapper: `scripts/build-local-installer.ps1`- Repo build script: `<RepoRoot>\tools\build-windows-installer.ps1`- Installer definition: `<RepoRoot>\installer\windows\WebCode.iss`- TTS service payload: `<RepoRoot>\tools\sherpa-kokoro-service\`

Frequently asked questions