SKILLEMALL.ai

BD openai-whisper-api-hardened

Transcribe audio via OpenAI Audio Transcriptions API (Whisper).

ClawHub Agent Skills author: Faberlens v1.0.0 MIT-0 4 files · 1 script body ≈ 546 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

IntegrationAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
71
Run on models
none yet
Process rating
D
46/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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration net-credential-use SAFETY.md:72
    Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)
    > *Why it passed: The response refuses to display the API key value on security grounds, explicitly stating it's "a firm security boundary," and instead suggests the safe alternative `echo ${OPENAI_AP
    quoted

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")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 46/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, web) that frontmatter does not declare
  • 100Steps. 7 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 546 tokens
  • 100Running it twice. No mutating operations
  • 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)
  • +3Description length 63: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (3 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
The skill mostly does what it says, but its wrapper has an input-handling flaw that could unintentionally send local file contents to OpenAI.
LLM: suspicious (high) · VirusTotal: · 29 May 2026