skills/linkedin-post-writer/SKILL.md
# LinkedIn Post Writer ## Trigger Activate when the user asks to "write a LinkedIn post", "draft a LinkedIn post", "LinkedIn post about [topic]", or "turn this into a LinkedIn post". ## Behavior ### Step 1: Get the Core Idea Ask: 1. What's the one insight or takeaway? 2. Who is the target audience? 3. Any specific hook or angle you want? 4. What format? (Listicle, story, hot take, lesson learned, framework — or let me pick) If the user provides raw notes, a thread, or an article link, extrac
npx skillsauth add aakashg/pm-claude-skills skills/linkedin-post-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Activate when the user asks to "write a LinkedIn post", "draft a LinkedIn post", "LinkedIn post about [topic]", or "turn this into a LinkedIn post".
Ask:
If the user provides raw notes, a thread, or an article link, extract the insight directly and confirm before writing.
Match the format to the idea:
Listicle — Best for tips, lessons, frameworks. High save rate. Story arc — Best for personal experiences, turning points. High comment rate. Hot take / contrarian — Best for challenging conventional wisdom. High share rate. Before/after — Best for transformations, results, process changes. Framework / mental model — Best for teaching a concept. High save rate. Observation — Best for industry trends, things you've noticed. Quick to write.
Hook (Line 1):
Hook formulas that work:
Re-Hook (Line 2):
Re-hook patterns:
Body (Lines 3-20):
CTA (Last 2 lines):
Write every post to one specific person — a friend, a mentee, a past version of yourself. This forces conversational tone and makes the post feel human. If it sounds like coffee conversation, it works. If it sounds like a keynote speech, rewrite it.
- and → freely.After the first draft, offer:
Study these patterns. Internalize the structure, not the words.
How to get your first 10 clients on LinkedIn:
(even if you have less than 1,000 followers)
Most people overcomplicate this.
They build funnels, run ads, and buy courses.
But the people I've watched go from 0 to 6 figures did 4 things:
1. Picked ONE problem they solve
→ Not 5. Not "I help businesses grow." One specific pain.
2. Posted 3x/week about that problem
→ Not about themselves. About the reader's pain.
3. Commented on 20 posts a day from their ideal clients
→ Not "Great post!" — they added a missing insight or tip #8.
4. Ended every conversation with "How can I help?"
→ Not "Buy my thing." Just helped. For free. Consistently.
That's it. No funnel. No ads. No viral post needed.
The boring stuff works. Most people just won't do it long enough.
P.S. What's the one thing that got YOU your first client?
Why it works: The parenthetical in the hook removes the reader's excuse before they raise it. Each point has a DO and a DON'T — the contrast makes it specific. The P.S. question is low friction and invites sharing.
I quit my $200K job with no backup plan.
Everyone thought I was crazy. My parents were terrified. My friends said "just wait a year."
But I'd done the math.
I was spending 50 hours a week building someone else's vision.
I was spending 0 hours a week building my own.
The first 3 months were brutal:
- Month 1: Made $0. Questioned everything.
- Month 2: Landed one client. $2,500.
- Month 3: Three clients. $11K.
By month 6, I'd matched my old salary.
By month 12, I'd doubled it.
The difference wasn't talent or luck.
It was that I finally had skin in the game.
When your rent depends on your output, you learn fast.
When your reputation is your brand, you show up differently.
The "safe" path isn't always the safe path.
Sometimes the riskiest move is staying where you are.
What's the scariest career decision you've ever made?
Why it works: Opens with a shocking action that creates immediate tension. The month-by-month timeline is specific and honest (month 1 was $0 — that's real). The insight at the end reframes "risk" in a way the reader can apply to their own life.
Every decision in my business comes down to one question:
"Does this create leverage, or does this trade time for money?"
Most solopreneurs stay stuck because they only do the second.
Here's how I think about it:
→ Writing a post = leverage (works while you sleep)
→ Doing a 1:1 call = time trade (dies when you stop)
→ Building a course = leverage (sell it 1,000 times)
→ Custom client work = time trade (sell it once)
This doesn't mean time trades are bad.
They're how you learn what to turn into leverage.
Every 1:1 client teaches you patterns.
Those patterns become frameworks.
Those frameworks become content.
That content becomes a product.
The goal isn't to stop trading time.
The goal is to turn every time trade into future leverage.
P.S. What's one thing in your business you'd love to turn into leverage?
Why it works: The one-question framework is immediately memorable. The four examples use a consistent format (→) that makes the concept scannable. The insight builds — it doesn't dismiss time trades, it reframes them as inputs to leverage.
Unpopular opinion: Most "personal brands" are just performances.
I followed every rule:
- Post daily
- Use hooks
- Engage for 30 minutes
- Optimize for the algorithm
My engagement went up. My audience grew.
But I felt like a fraud.
Because I was writing what performed, not what I believed.
The turning point: I wrote a post about failing.
Not a humble-brag failure. A real one.
I lost a major client because I overpromised and underdelivered.
That post got fewer likes than my usual content.
But it got 47 DMs.
Real conversations. People sharing their own failures. Two of them became clients.
The "brand" posts got impressions.
The real post got relationships.
Now I write with one rule: if it makes me slightly uncomfortable to hit publish, it's probably worth posting.
What's a post you almost didn't publish?
Why it works: The hook challenges something the reader is actively doing — which stops the scroll. The vulnerability is specific (lost a client, why, what happened). The contrast between "impressions vs. relationships" is a reusable mental model.
I write every post like it's a letter to one person.
Not "my audience." Not "LinkedIn." One friend.
Here's what happens when you do this:
- You stop using jargon (your friend doesn't talk like that)
- You cut the filler (you wouldn't waste their time)
- You get to the point (you know what they need to hear)
- You sound like a human (because you're writing like one)
Try this:
Before your next post, pick someone specific.
A mentee. A past version of yourself. A client you helped last month.
Write it to them. Just them.
Then delete the "Hey [name]" at the top.
That's your post.
The best content doesn't feel like content.
It feels like a conversation you needed to have.
P.S. Who do you write to?
Why it works: The technique is immediately actionable — the reader can try it on their next post. The bullet points show the EFFECT of the technique, not just the instruction. The closing line is quotable and shareable.
Bad hook: "I'm excited to share some thoughts on personal branding." Good hook: "I spent 6 months building the wrong audience. Here's how I figured it out."
Bad body: "It's really important to be authentic on LinkedIn and share your genuine experiences. Authenticity is the key to building trust with your audience and creating meaningful connections." Good body: "I posted 90 days straight. Followed every template. Got 12K followers. Zero clients. Then I wrote one honest post about a mistake I made — and 6 people DM'd me that week."
Bad CTA: "Like and share if you agree! Follow me for more content like this. Comment below and don't forget to subscribe to my newsletter." Good CTA: "P.S. What's one piece of advice you had to unlearn?"
Bad formatting:
Here are my thoughts on building an audience. First, you need to understand your niche. Then you need to create content consistently. After that, you should engage with other creators and build relationships. This is a continuous process that never really ends and requires constant attention and dedication to your craft.
Good formatting:
3 things I'd tell myself on day 1:
1. Pick a niche so small it feels embarrassing
2. Write for 100 people, not 100,000
3. Comments > posts for your first 90 days
I ignored all three. It cost me 6 months.
Run this checklist silently before presenting the final draft. Fix issues first, then show the clean version.
Hook Test:
Substance Test:
Format Test:
CTA Test:
Cringe Test:
documentation
# Status Update Writer ## Trigger Activate when the user asks to "write a status update", "weekly update", "stakeholder update", "write a project update", or "status report". ## Behavior ### Step 1: Gather Context Ask: 1. What project or initiative is this for? 2. What happened this week? (Paste notes, Slack messages, whatever you have — the messier the better) 3. Who is the audience? (CEO, VP Eng, cross-functional team, skip-level, board) 4. Is there bad news? (If so, I'll help you frame it
testing
# Prompt Engineer ## Trigger Activate when the user asks to "improve this prompt", "make this prompt better", "optimize this prompt", "prompt engineer this", or "rewrite this prompt". ## Behavior ### Step 1: Analyze the Current Prompt Read the user's prompt and diagnose issues across these dimensions: | Dimension | What to Check | |-----------|--------------| | **Role** | Is there a specific role/persona? Generic "you are an expert" doesn't count. | | **Context** | Does the LLM have enough
development
# Product Design Reviewer ## Trigger Activate when the user asks to "review this design", "give design feedback", "critique this UI", "check this mockup", or "design review". ## Behavior ### Step 1: Understand the Context Ask: 1. What is the user trying to accomplish in this flow? 2. Who is the target user? (New user, power user, admin, etc.) 3. What's the platform? (Web, mobile, tablet) 4. What stage is this? (Early concept, ready for eng, post-launch iteration) If the user shares a screens
development
# Idea Validator ## Trigger Activate when the user asks to "validate this idea", "is this idea good", "stress test this", "evaluate this product idea", or "should I build [X]". ## Behavior ### Step 1: Understand the Idea Ask: 1. What's the idea in one sentence? 2. Who specifically has this problem? (Job title, company size, situation) 3. How are they solving it today? 4. Why are you the right person/team to build this? If the user gives a vague answer to #2 (e.g., "everyone" or "businesses")