SKILLEMALL.ai
GitHub ↗ RU Sign in

BC signal-integration

Full Signal messenger integration for OpenClaw agents. Send/receive text and voice messages via signal-cli with role-based permissions (owner/trusted/untrusted), automatic voice transcription (Whisper), voice replies (TTS), conversation history, new contact triage, typing indicators, read receipts, and instant wake-on-message via OpenClaw hooks API. Use when setting up Signal messaging, handling Signal contacts, sending/receiving Signal messages, or managing Signal contact permissions.

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files · 2 scripts body ≈ 1 776 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Full Signal messenger integration for OpenClaw agents.

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

IntegrationGitHubAI and agentsSoftware developmenttype 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
89/100
safety, quality, tests
Safety 60%
89
Quality 40%
89
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

    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 · 3

    ✓ No critical or high findings

    Medium and low: 3
    • medium Dangerous commands cmd-privilege SKILL.md:44
      Privilege escalation / world-writable permissions
      sudo mv signal-cli-${SIGNAL_CLI_VERSION}/bin/signal-cli /usr/local/bin/
    • medium Dangerous commands cmd-privilege SKILL.md:45
      Privilege escalation / world-writable permissions
      sudo mv signal-cli-${SIGNAL_CLI_VERSION}/lib /usr/local/lib/signal-cli
    • low Dangerous commands cmd-cron-mention SKILL.md:79
      Mentions editing / listing crontab
      crontab -e

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 16 mutating operations with no state check
    • 40Consistency. Frontmatter name (signal-integration) differs from the folder (signal-messenger-standalone)
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 32 steps
    • 100Execution cost. Instruction body is 1776 tokens
    • 100Progress reporting. Reports progress
    • low 10 top-level sections: this looks like several domains in one skill

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 490: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 32 items
    • +4Has examples (10 code blocks)
    • +4Reference files are cited in the instructions (1 of 2)
    • +3All 2 scripts are documented

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