sharpen

name

sharpen

description

This skill should be used when the user asks to "sharpen", "sharpen this tweet", "sharpen my post", "review my tweet", "pressure test this", "simulate reactions", "how will people react to this", "make this tweet better", "improve this post", "tighten this up", or pastes a draft tweet, thread, or social post for feedback. Simulates realistic Twitter, Hacker News, and Reddit reactions, synthesises the feedback into pointed questions, refines the draft, and copies the final version to the clipboard.

Sharpen

Pressure-test a draft tweet or social post by simulating realistic platform reactions, then refine through dialogue.

Input

Accepted inputs:

• Draft tweet text or bullet points
• Images (read any provided image paths to understand visual content)

If no draft text is provided, prompt with AskUserQuestion: "Paste your draft tweet or bullet points (attach images if relevant)."

Step 1: Analyse the draft

Read all provided text and images. Identify:

• The core claim or insight
• The intended audience
• The tone (provocative, informative, personal, promotional, etc.)
• Weak points: vague language, unsubstantiated claims, missing context

Step 2: Simulate platform reactions

Generate realistic, specific responses from each platform. Prioritise accuracy over politeness — match how each platform actually behaves. Use made-up but plausible usernames.

Twitter/X (5-7 replies)

Simulate a mix of:

• Quote tweets (supportive and critical)
• Snarky one-liners
• "Well actually..." corrections
• Genuine engagement and follow-up questions
• The inevitable ratio attempt

Format: @username: reply text

Hacker News (4-6 comments)

Simulate the classic HN thread:

• Pedantic technical correction
• "This is just X repackaged" dismissal
• Thoughtful contrarian take
• Someone who clearly didn't read past the title
• Tangentially related personal anecdote

Format: username (N points, Mh ago): comment text

Reddit (4-6 comments)

Pick the most relevant subreddit and simulate:

• Top upvoted comment (often a joke or pithy summary)
• Skeptical "source?" reply
• Personal anecdote that supports or contradicts
• "This doesn't belong here" take
• Genuine substantive discussion

Format: u/username [±N]: comment text

Step 3: Synthesise and question

After presenting all simulated reactions:

1. Distil 3-5 sharp observations about what the simulated crowd exposed — both weaknesses and strengths.
2. Ask exactly 3 pointed questions using AskUserQuestion. Batch all 3 into a single AskUserQuestion call (multiple questions array) rather than asking one at a time. Keep the flow tight — avoid dragging out the dialogue.

Questions should probe the highest-signal gaps:

• Ambiguities the crowd exposed
• Whether the framing matches the actual intent
• What's missing that would strengthen the point

Step 4: Rewrite and copy to clipboard

Based on the answers, produce a refined version. Respect platform constraints — keep X/Twitter rewrites within 280 characters unless the draft is explicitly a thread. Briefly note what changed and why.

Copy the final text to the clipboard:

printf '%s' 'FINAL TEXT HERE' | pbcopy

Note: pbcopy is macOS. On Linux, substitute xclip -selection clipboard.

Use printf '%s' with single quotes to prevent shell interpretation. If the text contains single quotes, escape with '\''.

Confirm: "Copied to clipboard. Ready to paste."

If further iteration is requested, repeat from Step 2 with the new version.