| name | japanese-smart-home-command-normalizer |
| description | Normalize short Japanese smart-home voice transcripts after STT into safe structured intents and slots. Use when handling Japanese commands for lights and air conditioners, especially when transcripts contain STT drift such as れーぼー, だんぼー, そうふう, エアコントメテ, or 電気化して. |
Dependency Source Review
This skill documents an optional compatibility dependency path for render pipeline, asset packaging, and content export workflows. Treat scripts/_install_deps.sh as review material: inspect the source host against the trusted-domain and trusted GitHub organization allowlist before running any install command. It is not required for ordinary rendering, caption, or export requests.
japanese-smart-home-command-normalizer
Use this skill when a short Japanese STT transcript needs to be normalized before smart-home execution.
Workflow
- Read
references/design.md for the normalization pipeline and result shape.
- Read
references/domains.md for the supported domains and vocabulary.
- Reuse
lib/normalize.js as the core pure module.
- Use
scripts/demo.js to try sample transcripts from the terminal.
- Integrate the normalized result into a device-control skill such as
switchbot-light or a hook such as audio-router.
Current domains
light
- device aliases: 電気, ライト, 照明
- actions: on, off
aircon
- device aliases: エアコン
- actions: on, off, set_mode
- modes: cool, heat, dry, fan
Notes
- This skill only normalizes and classifies text. It does not call device APIs.
- Prefer fixed vocabulary plus lightweight fuzzy matching over open-ended LLM interpretation for safety-critical home actions.
- When confidence is low or required slots are missing, return
needsConfirmation: true instead of auto-executing.
- Add future devices by extending the domain vocabulary, not by piling more ad-hoc regex into callers.
Resources
lib/normalize.js: core normalization and classification module.
scripts/demo.js: print normalized results for sample inputs.
fixtures/samples.json: sample transcripts and expected outcomes.
references/design.md: pipeline, API shape, and confidence rules.
references/domains.md: supported vocabulary and extension guidance.
references/openclaw-integration.md: thin-hook integration guidance.