Twitter Reply

Own ad-hoc reply 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 reply workflow.

Condense The Request First

Before preflight or any tw command, protect any exact target and final reply text. For every task-mode request, rewrite the remaining user wording as one concise, corrected sentence. Fix obvious typos from the full context and remove filler or repetition, while preserving every explicit count, topic, literal search phrase, account or relationship filter, engagement threshold, and other constraint. Do not add a topic or requirement the user did not state.

Use this condensed request as the task direction for task creation and any fresh-task restart. If the wording cannot be condensed without guessing the user's intent, ask one concise question and stop. Never rewrite an exact target/reply pair. For example, fin 10 let's connect tweets and draft replies means Find 10 tweets matching "let's connect" and draft replies, not a finance task.

Select One Mode

Select task mode when the user supplies a direction, topic, literal search anchor, account/surface criteria, target-discovery request, or a discovery count from 5 through 10.

Select exact-action mode only when the user supplies one exact target, one complete final reply, and explicit immediate-send intent.

Also select exact-action mode when the user explicitly retries one exact unchanged draft from the current task and its durable result conclusively proves that dispatch never started. A retry creates a fresh exact-action flow; it never reopens, reschedules, or executes the failed scheduled mutation.