Drafting Slack Posts

What it does

When you ask your agent for a Slack message, you usually get markdown: **bold**, - bullets, headings, and backticks around every file name. Pasted into Slack, it looks half-formatted. This skill makes the whole reply the post, so you can /copy it and paste it unchanged.

• Fixed shape: a title line, numbered section headings, • items and ◦ sub-items, blank lines between sections, and an optional closing line for the team.
• Zero backticks: file paths, event names, ticket IDs, commands, and URLs are written as plain text. This is the rule agents break most often, so the skill makes it explicit and ends with a final check for stray backticks.
• No extras: no intro line, no "here's your draft", no follow-up questions inside the post. The skill also overrides output-style add-ons (such as Explanatory insight boxes) for that one reply.
• Asks first: unknowns that would change the post (channel, who to mention, an uncertain date or number) are asked before drafting.

Good for

Incident follow-ups, release notes, thread replies, weekly updates, and decision requests ("Option A vs B, thoughts?").

Trigger phrases and the example post are in Korean. The formatting rules apply to any language.