Questions Form
v1.0.0Present multiple clarifying questions as an interactive Telegram form using inline buttons. Use when the agent needs to ask the user 2 or more clarifying questions before proceeding with a task, and wants to present them all at once in a structured form layout with selectable options and an "Other" free-text escape hatch. Triggers when: gathering multi-faceted requirements, onboarding flows, preference collection, or any scenario requiring structured multi-question input from the user via Telegram.
⭐ 0· 1.2k·3 current·3 all-time
byEmrick Donadei@edonadei
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (present a multi-question Telegram form) matches the SKILL.md: all instructions relate to sending messages, inline buttons, and handling Telegram callback_data. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
The SKILL.md stays within the stated purpose: it defines form structure, callback_data conventions, free-text handling, submit/cancel logic, timeouts and recovery. It does not instruct the agent to read arbitrary files, access unrelated credentials, or send data to external endpoints.
Install Mechanism
No install spec and no code files are present (instruction-only). This is the lowest-risk model and there is nothing written to disk or fetched at install time.
Credentials
The skill declares no required environment variables or credentials. The SKILL.md assumes a Telegram-capable channel integration provided by the host platform; that assumption is reasonable and proportional for a Telegram form helper.
Persistence & Privilege
always is false and the skill documents keeping form state in conversation context (non-persistent). It does not request elevated or persistent privileges, nor does it modify other skills or system-wide settings.
Assessment
This skill is internally coherent and low-risk, but before installing check these practical points: ensure your agent platform already provides the Telegram integration (bot token/webhook) since the skill assumes it and declares no credentials; confirm the agent will keep per-conversation state so forms work as documented (the skill expects transient in-memory state and re-sends forms if context is lost); be mindful that free-text answers may contain PII or secrets — decide whether the agent should redact or treat such text as sensitive before storing or forwarding; verify callback_data handling respects Telegram's 64-byte limit as noted; and ensure your agent does not forward collected answers to external services unless you expect that. If you need stricter guarantees (audit logs, encrypted storage, or persistence across restarts), request or add those capabilities explicitly before using this in production.Like a lobster shell, security has layers — review code before you run it.
latestvk97eg9d1b6thbts2c38ybhfnd580ppkb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.