BC android-sms-gateway
Self-hosted SMS via Android phone HTTP API. Use when you need to send/receive SMS messages using an Android device as a gateway. Supports popular SMS Gateway apps (SMS Gateway API, SMSGate, etc.). Ideal for security teams wanting full control without third-party SMS providers.
Self-hosted SMS via Android phone HTTP API.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 2
-
high Exfiltration
exfil-webhook-urlscripts/register_webhook_capcom6.sh:78Webhook / callback URL commonly used for exfiltration (verify the destination)- For testing, use https://webhook.site to get a temporary URL
Medium and low: 1
-
low Dangerous commands
cmd-cron-mentionSKILL.md:289Mentions editing / listing crontab (documentation of a security skill)# crontab -e
security skill
Files scanned: 12. 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 16 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2246 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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
- +1No license
- +2Single-language instructions
- +3Description length 277: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (19 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
- +3All 8 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.