AC telegram-interactive-buttons
Create interactive Telegram messages with inline buttons using OpenClaw CLI. Use when you need user interaction in Telegram (selection from a list, confirmation dialogs, workflow menus, quick actions). Handles button formatting, callback handling, and message editing. Critical for UX-friendly Telegram automation.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
exfil-webhook-urlSETUP.md:58Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl "https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdates"
placeholder
Files scanned: 11. 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. 17 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 53 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1822 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 314: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.