SKILLEMALL.ai

BD faster-whisper-local-service

Local speech-to-text (STT) transcription service for OpenClaw using faster-whisper. Runs as HTTP microservice on localhost for voice input, microphone transcription, and speech recognition. No recurring API costs — after initial model download, runs fully local. Supports WebChat voice input, Telegram voice messages, and any OpenClaw voice workflow. Keywords: STT, speech to text, voice transcription, local transcription, whisper, faster-whisper, offline, microphone, speech recognition, voice input.

modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files · 2 scripts body ≈ 908 tokens Open the sourcegithub.com analyzed 3 d ago

Local speech-to-text (STT) transcription service for OpenClaw using faster-whisper.

As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureTelegramInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
D
44/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 44/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 85Steps. 16 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 908 tokens
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 502: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 16 items
  • +4Has examples (5 code blocks)
  • +3All 2 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.