BF agent-relay
Bridge between an AI agent and a phone — send/receive messages with attachments and push notifications. Push-first webhook architecture with polling fallback.
As a process F 43/100 · Will not run — References files that are not bundled: scripts/poll-inbox, scripts/relay, scripts/poll-inbox-fallback
IntegrationAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/poll-inbox - warning
missing-refreference to a missing file: scripts/relay - warning
missing-refreference to a missing file: scripts/poll-inbox-fallback
Process rating: all ten parameters 43/100
Will not run. References files that are not bundled: scripts/poll-inbox, scripts/relay, scripts/poll-inbox-fallback
- 0Tools and files. 3 referenced file(s) missing: scripts/poll-inbox, scripts/relay, scripts/poll-inbox-fallback
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 15 mutating operations with no state check
- 100Steps. 20 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1135 tokens
- 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
- +1No license
- +2Single-language instructions
- +3Description length 158: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: suspicious
The skill is a coherent phone-to-agent relay, but its public webhook setup can automatically wake an agent with broad tools and the authentication guidance is under-scoped.
LLM: suspicious (medium) · 30 Jun 2026