twitter-postlisted

# Twitter Post Own ad-hoc tweet work as an independent flat peer. Never activate or depend on `twitter-automation`; that peer may route here, but this skill owns preflight and the complete post workflow. ## Select One Mode Select **task mode** when the user supplies a topic, direction, desired result, drafting request, or a count from `1` through `5`. Any count above one selects task mode. Select **exact-action mode** only when the user supplies one complete final post and explicitly wants that exact text published now. - Default a missing task count to `1`. - Accept only an integer from `1` through `5`. - For a count above `5`, ask the user to split it explicitly; never create multiple proposals automatically. - For several exact final texts, ask whether the user wants one direction-based task or separate exact actions. Never silently turn exact payloads into generative directions. - If exactness versus direction is unclear, ask one concise question before invoking `tw`. ## Task Template When entering task mode — and whenever the request is too vague to form a direction — offer one localized fill-in template instead of open-ended questions: ```text Post task template: Topic/direction: <what to write about>, count <1–5> Optional: tone, audience, must-include or must-avoid points Example: Topic: why small teams should automate release notes, count 3 ``` ```text 发推任务模板： 主题/方向：<要写什么>，条数 <1–5> 可选：语气、受众、必须包含/避开的点 示例：主题：为什么小团队应该自动化 release notes，3 条 ``` Reuse the same tem