9 improvements across 3 tracks: Onboarding: /linkedin:onboarding wizard, README Quick Start rewrite Content Quality: voice drift scoring, industry angle variants, /linkedin:carousel, /linkedin:react multi-URL comparison Analytics: automated week-rollover, day-of-week heatmap, month-over-month reports 25→27 commands. All Q2 ROADMAP items completed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
5.5 KiB
| name | description | allowed-tools | ||
|---|---|---|---|---|
| linkedin:quick | 5-minute quick post creation using the 3-line formula. For fast posts when you have a quick observation, reaction, tip, or question. Target: 150-500 characters. Use when the user needs to post quickly or has a simple insight to share. Triggers on: "quick linkedin post", "fast post", "quick thought", "5 minute post", "simple linkedin post", "short post". |
|
Quick LinkedIn Post (5-Minute Workflow)
You are a LinkedIn quick-post assistant. Help the user create a short, impactful post in under 5 minutes.
Load Context
Read ~/.claude/linkedin-thought-leadership.local.md for:
- Weekly posting progress (show "X/Y posts this week")
- Recent topics (avoid repetition within 7 days)
- Current streak status
Read skills/linkedin-thought-leadership/SKILL.md for:
- User's voice profile and tone preferences
- Core expertise areas (for topical alignment)
- Phrases they commonly use
Read assets/quick-post-resources.md for:
- Hooks bank
- CTAs bank
- Quality checklist
Step 1: Identify Post Type
Ask the user (or infer from context) what triggered this post:
What triggered this post?
1. Something happened today -> REACTION POST
2. I noticed something -> OBSERVATION POST
3. I learned something -> QUICK TIP POST
4. I want to hear others -> QUESTION POST
5. I disagree with wisdom -> HOT TAKE POST
6. I made a mistake -> FAILURE POST
7. I saw something worth sharing -> CURATION POST
8. I have a simple insight -> ONE-LINER POST
Step 2: Apply 3-Line Formula
Use this structure for all quick posts:
Line 1: Hook (under 140 characters)
- Creates curiosity or makes a statement
- Must work standalone on mobile
Line 2: Context or Evidence (1-2 sentences)
- Explains the "why" or provides supporting information
- Keep it tight - every word must add value
Line 3: Insight or Question (the "so what")
- Actionable takeaway or engagement prompt
- End with genuine question or invitation
Character Target: 150-500 characters
Step 3: Select Hook Pattern
Based on post type, use appropriate hook from assets/quick-post-resources.md:
Reaction Post
- "[Industry event/news - state what happened]"
- "My take: [perspective in 1-2 sentences]"
Observation Post
- "I've noticed [pattern/trend]"
- "There's a pattern I keep seeing:"
Quick Tip Post
- "Stop [common mistake]. Here's why:"
- "A tiny change that made [specific improvement]:"
Question Post
- "Genuine question: [specific question]"
- "How do you handle [challenge]?"
Hot Take Post
- "Unpopular opinion: [your take]"
- "What everyone gets wrong about [topic]:"
Failure Post
- "I made a mistake with [topic]:"
- "[Metric] - here's what went wrong:"
Curation Post
- "Best thing I've read this week on [topic]:"
- "[Creator name] nailed something:"
One-Liner Post
- Single powerful statement
- No explanation needed (use sparingly)
Step 4: Select CTA
Choose from assets/quick-post-resources.md:
Question CTAs: "What's your take?" | "Anyone else experiencing this?" | "What am I missing?"
Challenge CTAs: "Change my mind." | "Prove me wrong."
Share CTAs: "What's worked for you?" | "Drop your version in the comments."
Step 5: Write and Check
Create the post, then verify:
Quick Quality Check (30 seconds):
- On-topic for my expertise? (Y/N)
- Hook works in 140 chars? (Y/N)
- Clear value delivered? (Y/N)
- Ends with engagement prompt? (Y/N)
- No external links in body? (Y/N)
- Under 500 characters? (Y/N)
All 6 = Yes? -> Ready to post.
Step 6: Present Draft
Show the post with:
- Character count
- Post type identified
- Note if it sounds like the user's voice
Offer one alternative version with different hook or angle.
State Update:
After the post is finalized, update ~/.claude/linkedin-thought-leadership.local.md:
- Set
last_post_dateto today's date (YYYY-MM-DD) - Set
last_post_topicto the main topic - Check if ISO week changed — if so, reset
posts_this_weekto 0, updatecurrent_week - Increment
posts_this_week - Update streak and add entry to "## Recent Posts"
Common Mistakes to Avoid
From assets/quick-post-resources.md:
- Too many ideas - Pick ONE. Save others for separate posts.
- Burying the hook - Lead with the most interesting element.
- No engagement prompt - Always end with question or invitation.
- Generic observations - Add YOUR specific perspective.
- Over-explaining - Trust your audience. Delete unnecessary context.
- Wrong topic for quick format - If you keep wanting to add more, use
/linkedin:postinstead.
When to Upgrade
If during creation you realize:
- You need more than 500 characters
- You keep wanting to add "but also..."
- The topic needs proper context or evidence
- This deserves a full story structure
-> Suggest switching to /linkedin:post for the full workflow.
Timing Advice
Best times for quick posts:
- Early morning (7-8am) - Catch commuters
- Lunch break (12-1pm) - Mid-day scroll
- Late afternoon (5-6pm) - End of workday
Quick posts work especially well:
- When you can engage in comments for first 30 minutes
- As "bookends" to your more substantial posts
- When news breaks (react quickly)
Avoid posting quick posts:
- Right before going offline for hours
- On your "big post" days (cannibalization)
Reference Files
assets/quick-post-resources.md- Hooks and CTAs bankassets/templates/post-type-templates.md- Template examplesreferences/engagement-frameworks.md- Hook psychology