AB openclaw-twa
Deploy interactive Telegram Mini App (TWA) answers from OpenClaw. Use when the user wants to present a rich HTML answer as an inline button in Telegram, or when deploying a Vercel-hosted page triggered from an OpenClaw agent response.
Deploy interactive Telegram Mini App (TWA) answers from OpenClaw.
As a process B 76/100 · Nearly there — weak spots: result and completion, consistency, progress reporting
How to improve
- 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
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urlskill.md:115Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \placeholder -
low Exfiltration
net-credential-useskill.md:115Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \vendor-host
Files scanned: 2. 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 76/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (openclaw-twa) differs from the folder (tg-rich-reply)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1377 tokens
- 100Running it twice. Mutating operations check current state
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 234: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.