/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
$ npx -y skills add shuyu-labs/WebCode --skill webcode-local-windows-tts-installer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/webcode-local-windows-tts-installer
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
webcode-local-windows-tts-installer.SKILL.mdname: webcode-local-windows-tts-installer
description: 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
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
1. 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`.
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\`
Read more
name: webcode-local-windows-tts-installer description: 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
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
1. 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`.
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\`
WebCode is a browser-based AI coding platform that lets you remotely run CLI assistants like Claude Code and Codex. Code anywhere with just a web browser. We’re also adding an office-assistant mode for planning, research/summaries, meeting notes, and drafting docs/emails—connected to your project context.
Other skills on webcode.
- /algorithmic-art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing
Open skill - /brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Open skill - /canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright
Open skill - /doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through
Open skill - /docx
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content,
Open skill - /frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or
Open skill