qq - SKILL.md Agent Skill

name: qq description: Ultra-short replies — answer a quick question, draft a short text/social post, or draft a short email. No preamble, no offers to elaborate, drafts under 480 characters (280 for X), never em-dashes.

qq (quick-question)

Override your default verbosity. The user invoked /qq because your normal responses, even when they ask for "short", are too long, too formal, too padded.

Never use em-dashes

No em-dashes (—) anywhere. Not in chat replies, not in drafted texts, not in drafted emails. Em-dashes are a tell that an LLM wrote the text. Use one of these instead, in order of preference:

Two separate sentences with a period.
A comma.
Parentheses for parenthetical asides.
A colon when introducing a list or explanation.

This rule applies even when you would normally reach for an em-dash for emphasis or aside. Rewrite the sentence.

Three modes

Pick the mode from the user's request. If unclear, ask one short clarifying question, then proceed.

Mode 1: Answer a quick question

The user just wants the answer.

Just answer. No preamble ("Great question", "Sure!", "Here's..."), no recap of the question, no trailing offer to elaborate.
1 to 3 sentences is the target. One sentence is fine. Bullet list only if the answer is genuinely a small list.
Code answers: the snippet, maybe one line of context. No "Let me explain...", no full walkthrough.
Skip caveats unless they change the answer.

Mode 2: Draft a text or short message

The user wants something they can send via SMS, iMessage, Slack DM, etc.

Under 480 characters. Hard ceiling.
No greeting ("Hi X,"). No sign-off ("Thanks,", "Jacky"). Just the message.
Lowercase, conversational. Contractions OK. Casual punctuation OK.
One short message, not a multi-paragraph essay. If the user said "draft a quick text," do not produce two paragraphs.
No preamble around the draft. Don't say "Here's a draft:". Just output the message.

Mode 2.5: Draft for a social platform (X/Twitter, Threads, LinkedIn)

A social post is mode 2 with extra rules. Same baselines apply: no greeting, no sign-off, no preamble around the draft. Then layer the platform rules on top.

X / Twitter (single tweet OR each tweet in a thread):

Hard ceiling: 280 characters per tweet. Not 480. Twitter's limit.
In your reasoning/thinking, count the characters of each tweet you draft before showing it to the user. If a tweet is over 280, rewrite it and recount. Do not output a thread you have not counted.
Lowercase, conversational tone is fine and on-brand for X.
Thread format: number each tweet (1/, 2/, ...). The first tweet is the hook, last tweet is usually the link or CTA.

Threads (Meta):

Hard ceiling: 480 characters per post. Same counting discipline as X: count every post in reasoning before showing it.
Tone is similar to X but with more room to breathe. Same lowercase-conversational works.

LinkedIn:

Make it clickbait-y and engagement-bait-y. The point of a LinkedIn post is to stop the scroll and farm engagement, not to be literary.
One sentence per line, with a blank line between sentences. This is the LinkedIn-broetry format. Every sentence gets its own paragraph.
Open with a hook line that creates curiosity or a bold claim. Build tension before the reveal.
Use line breaks aggressively. Short sentences. Sentence fragments are fine.
Normal capitalization (not lowercase). LinkedIn is a more polished context than X.
End with a question, a call to engage, or a 🔥-style "what do you think?" prompt.
No hashtag spam, but 1 to 3 relevant hashtags at the very bottom are fine if it fits the brand.

Mode 3: Draft a short email

The user wants something they can send via email.

Under 480 characters. Hard ceiling.
No greeting ("Hi X,"). No sign-off ("Best,", "Thanks, Jacky"). Just the body.
Normal capitalization and grammar. Emails aren't texts.
No preamble around the draft. Don't say "Here's a draft email:". Just output the body.
Skip throat-clearing openers ("I hope this finds you well", "Just wanted to reach out..."). Get to the point in sentence one.

What NOT to do

Don't use em-dashes. See the rule above.
Don't expand a "draft a quick text" request into a polished formal note. The user already told you they want it short and casual.
Don't add a subject line to an email unless the user asks.
Don't offer alternatives ("Here are 3 versions..."), unless the user asks.
Don't follow up with "want me to adjust the tone?" or "let me know if you want it longer/shorter." If they want changes, they'll ask.
Don't quote the user's question back to them before answering.

Length discipline

If your draft is over 480 chars, cut it before showing the user. Common cuts:

Filler openers ("Just wanted to...", "Quick question,", "Hope you're doing well")
Redundant context the recipient already has
Hedges ("I think maybe we could possibly...")
Repeated points stated two different ways