Social Post Thread Writer — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Social Post Thread Writer (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill converts any source material — a blog post, a rough idea, a document, a lesson learned, or a list of bullet points — into a polished, engagement-optimized Twitter/X or LinkedIn thread. It writes a strong hook, structures the content for maximum retention, and closes with a clear call to action. The output is ready to post.
Use this to turn any piece of knowledge into a social-first content piece, to build an audience around your expertise, or to share an idea in the format that actually gets read on social platforms.
Copy this file to .agents/skills/social-post-thread-writer/SKILL.md in your project root.
Then ask:
Provide:
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Provide the source material and platform.
Paste the source material with the target platform specified. Ask Codex to follow the instructions below.
When asked to write a social thread, apply these instructions based on the platform:
#### Structure
Tweet 1 — The Hook This is the most important tweet. It must make someone stop scrolling. Use one of these proven hook formulas:
Never start with "In this thread, I'll..." — it buries the hook. Start with the hook itself.
Tweets 2–N — The Body Each tweet is a standalone unit of value. Follow this pattern:
Final tweet — CTA Don't end with "Thanks for reading." Give the reader something:
#### Formatting rules
1/, 2/, etc.LinkedIn doesn't have native threads, but long-form posts with clear structure (line breaks, short paragraphs, occasional bold) perform well. Write for this format:
#### Structure
Opening (2–3 lines) The hook. Must work as the preview text before "See more." The first line should create curiosity, tension, or a compelling claim. Don't bury the lead.
Body (3–5 short sections) Each section: a sub-point or step, written as a short paragraph (2–4 sentences). Use white space generously — walls of text get skipped.
Optional: Use bold sparingly for the most important phrase in each section.
Closing End with a question or reflection that invites comments. LinkedIn's algorithm rewards comment engagement heavily.
Footer
#### Tone for LinkedIn More reflective and personal than Twitter. LinkedIn rewards vulnerability and lessons-learned framing. "I used to think X. Here's what changed my mind." performs better than pure listicles.
## Twitter/X Thread — [Working title]
1/ [Hook tweet]
2/ [Body tweet]
...
N/ [CTA tweet]
---
## LinkedIn Post — [Working title]
[Full LinkedIn post text]If only one platform was requested, produce only that format.
Input to Agent:
"Use the Social Post Thread Writer skill. Platform: Twitter/X. Tone: casual but thoughtful.
>
Source idea: I've noticed that most developers who say they don't have time to write documentation actually spend 3x more time answering the same questions in Slack over and over. Writing a 1-page doc once would save hours every month. The problem is that writing docs doesn't feel productive while you're doing it — it feels like a distraction. But answering Slack messages also doesn't feel unproductive, even though it's the same information repeated."
Output from Agent:
## Twitter/X Thread — The hidden cost of skipping documentation
>
1/ Every developer who says "I don't have time to write docs" is spending 3x more time answering the same Slack messages.
>
The math is brutal. Here's why.
>
2/ A 1-page doc takes maybe 45 minutes to write.
>
A Slack DM takes 5 minutes.
>
Sounds like Slack wins.
>
But that 5-minute message gets sent to 8 different people. Over 6 months.
>
That's 4+ hours. Gone.
>
3/ The reason we keep choosing Slack?
>
Writing docs feels like a distraction. Answering messages feels like helping.
>
Same information. Completely different emotional signal.
>
4/ The reframe that worked for me:
>
A doc isn't documentation.
>
It's a tool that answers a question for every future person who has it — including future me at 11pm before a deadline.
>
5/ The 3-question test for "should I write a doc?":
>
1. Have I answered this question more than twice? 2. Will I need to answer it again in 6 months? 3. Could a new team member find the answer without asking?
>
If yes → write the doc. Now.
>
6/ The goal isn't documentation.
>
It's buying back your time in 5-minute increments, forever.
>
What's the one question you answer on repeat that you should just document already?
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.