Local TTS using the sherpa-onnx offline CLI.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsherpa-onnx-ttsExecute the skills CLI command in your project's root directory to begin installation:
Fetches sherpa-onnx-tts from steipete/clawdis and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate sherpa-onnx-tts. Access via /sherpa-onnx-tts in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
350.1K
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
350.1K
stars
Local TTS using the sherpa-onnx offline CLI.
$OPENCLAW_STATE_DIR/tools/sherpa-onnx-tts/runtime, default ~/.openclaw/tools/sherpa-onnx-tts/runtime)$OPENCLAW_STATE_DIR/tools/sherpa-onnx-tts/models, default ~/.openclaw/tools/sherpa-onnx-tts/models)Resolve the active state directory first:
STATE_DIR="${OPENCLAW_STATE_DIR:-$HOME/.openclaw}"
Then write those resolved paths into the active OpenClaw config file ($OPENCLAW_CONFIG_PATH, default ~/.openclaw/openclaw.json):
{
skills: {
entries: {
"sherpa-onnx-tts": {
env: {
SHERPA_ONNX_RUNTIME_DIR: "/path/to/your/state-dir/tools/sherpa-onnx-tts/runtime",
SHERPA_ONNX_MODEL_DIR: "/path/to/your/state-dir/tools/sherpa-onnx-tts/models/vits-piper-en_US-lessac-high",
},
},
},
},
}
The wrapper lives in this skill folder. Run it directly, or add the wrapper to PATH:
export PATH="{baseDir}/bin:$PATH"
{baseDir}/bin/sherpa-onnx-tts -o ./tts.wav "Hello from local TTS."
Notes:
tts-models release if you want another voice..onnx files, set SHERPA_ONNX_MODEL_FILE or pass --model-file.--tokens-file or --data-dir to override the defaults.node {baseDir}\\bin\\sherpa-onnx-tts -o tts.wav "Hello from local TTS."Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
sherpa-onnx-tts fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
sherpa-onnx-tts reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added sherpa-onnx-tts from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
sherpa-onnx-tts reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added sherpa-onnx-tts from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: sherpa-onnx-tts is the kind of skill you can hand to a new teammate without a long onboarding doc.
sherpa-onnx-tts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend sherpa-onnx-tts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sherpa-onnx-tts has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: sherpa-onnx-tts is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 69