openclaw - 💡(How to fix) Fix FEATURE: Add Telegram skill picker/list UI [1 participants]

Summary

Add a Telegram UI to browse and select installed skills instead of requiring users to remember and type skill names manually.

Problem to solve

As the number of installed skills grows, remembering exact skill names becomes impractical. The current documented path is to run skills by name (for example, /skill <name> [input]), but there does not appear to be a documented Telegram skill picker or list UI comparable to model selection. This creates discoverability and usability friction, especially on mobile.

Proposed solution

Add a Telegram-native skill picker/list flow. At minimum, users should be able to browse installed skills and tap one to invoke it, similar to model selection UX. Ideal behavior: show installed skills, allow selection, then optionally prompt for task input.

Alternatives considered

Continue requiring /skill <name> [input], but this does not scale well as skill count grows and depends on users remembering exact names. Telegram command menus may also not expose everything cleanly when command lists get large.

Impact

Improves discoverability, usability, and adoption of skills in Telegram. Becomes increasingly valuable as users accumulate more skills and can no longer remember exact names. Reduces command memorization burden and lowers friction for skill use.

Evidence/examples

Current docs support running a skill by name, but repeated checks did not reveal a documented Telegram skill-picker/list feature comparable to model selection. In the current Telegram-based OpenClaw setup, model/provider selection already uses a picker flow, so a skill picker would extend an existing interaction pattern rather than introduce a brand-new one.

Additional information

This request is specifically motivated by a Telegram-based OpenClaw setup, but the pattern may also be useful on other chat surfaces that support menus or inline selection.