SKILLEMALL.ai
GitHub ↗ RU Sign in

BC twilio

OpenClaw skill for Twilio APIs: Messaging, WhatsApp, Voice, Conversations, Verify, plus Studio, Lookup, Proxy, Sync, TaskRouter, and Segment/Engage.

ClawHub Agent Skills author: codedao12 v1.0.1 16 files body ≈ 516 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 63/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

AnalyzerWhatsAppInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
C
63/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Running it twice w 4
30
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: 16. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: OpenClaw skill for Twilio APIs: Messaging, WhatsApp, Voice, Conver… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 63/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 29 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 516 tokens
  • 100Progress reporting. Reports progress
  • 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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 148: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 29 items
  • +4Reference files are cited in the instructions (14 of 14)

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

External checks

ClawHub: clean
This is a documentation-only Twilio API guide with expected external API use, but users should be careful because Twilio actions can send messages, emails, verifications, and phone calls that may cost money.
LLM: benign (high) · VirusTotal: benign · 10 Sept 2026