twitter-automationlisted

# Twitter Automation Act only as the optional high-level router for the flat ThreadWave Twitter skill suite. Never contain, copy, proxy, or execute the workflows owned by `twitter-post`, `twitter-reply`, or `twitter-agent`. ## Flat Peer Contract Treat these as independent installed siblings: ```text twitter-automation -> routes to twitter-post -> routes to twitter-reply -> routes to twitter-agent ``` Every destination skill can activate directly. None depends on this skill. Route by skill name only; never use a relative path, nested skill folder, import, or copied procedure. ## Language Respond in English or Simplified Chinese from explicit preference, latest message, conversation language, then English. Preserve the original request and exact user content without translation or normalization. ## Starter Menu For a request such as `start ThreadWave`, `open ThreadWave`, or `启动 ThreadWave`, or when the entire trimmed request is exactly `threadwave` or `tw` (case-insensitive), activate `threadwave-preflight` once in `greeting-balance` mode, then show the starter menu and wait. Do not treat `tw` followed by a CLI subcommand or other text as a starter alias. Greeting-balance is a read-only balance lookup, not a readiness check, and authorizes no workflow or X mutation. Render this approved setup panda exactly once in a preformatted block above the menu. Preserve every space and line break; do not replace it with an image, emoji, or n