Post strategist
πͺ Claude skills that capture your writing voice and ghostwrite social media posts that sound exactly like you.
npx -y skills add slayerman420/mimiq --skill post-strategistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Ghostwrites complete, ready-to-publish social media posts in the user's exact voice with optimal timing recommendations. ALWAYS trigger for any request to write or draft a social post on any platform. Trigger on: "write me a post", "draft a LinkedIn post", "write a tweet", "write my Instagram caption", "I need to post about X", "help me write content", "create a post about my launch / job / article", "write a week of posts", "I have an idea β write it up", "when should I post this", "what's the best time to post today", "write this in my voice", "turn this into a post", or any request ending in publishable social content. Check for a Style Fingerprint first β if none exists, run voice-capture before writing. Always offer both personal timing data and platform-research timing. Do NOT trigger for content performance analysis (content-audit) or style-capture with no writing request (voice-capture).
SKILL.md
7.3 KB, ~1.5k tokens by cl100k_base, as published. Nobody here has run it
Post Strategist Skill
Ghostwrite posts that sound exactly like the user and tell them the best time to publish them.
Prerequisites Check
Before writing, verify what context you have:
| Context Needed | If Available | If Missing |
|---|---|---|
| Style Fingerprint | Use it directly | Ask user to run voice-capture first (required) |
| Content Audit Report | Use it for topics | Ask if they want to run content-audit, or proceed without |
| Target platform | Use platform rules | Ask user which platform(s) to write for |
| Topic / brief | Use it | Ask: "What do you want this post to be about?" |
Never ghostwrite without a style fingerprint. Everything else is optional but improves output.
Step 1 β Get the Brief
Ask the user (or infer from context):
- Platform β LinkedIn / X / Instagram / Facebook / Reddit / Medium / Substack?
- Topic β What is the post about? (Can be a vague idea β "something about leadership" is fine)
- Goal β Inform / inspire / promote / entertain / spark debate?
- Length preference β Short (under 100 words) / medium / long-form? Or match their typical style?
- Any must-include elements? β A specific link, CTA, event, announcement?
If they're vague, suggest topics from their top-performing clusters in the audit report.
Step 2 β Ghostwrite the Post
Apply the style fingerprint strictly. Checklist before writing:
- Tone matches their fingerprint (casual/formal/witty/warm/etc.)
- Sentence length matches their pattern
- Opens the way they typically open (hook, question, story, bold claim)
- Closes the way they typically close (CTA, reflection, one-liner)
- Vocabulary matches β their words, not generic words
- Emoji usage matches their pattern (frequency + which ones)
- No phrases or patterns in their "NEVER DO" list
- Platform-appropriate format (e.g., LinkedIn β Twitter β Instagram)
Platform-specific formatting rules:
- Optimal length: 150β300 words for engagement; long-form (600β1200w) for thought leadership
- Line breaks after every 1β2 sentences (LinkedIn compresses walls of text)
- Open with a hook line that stands alone (visible before "see more")
- Hashtags: 3β5 max, at the end
- CTAs work well ("What do you think?" / "Drop your experience below")
X / Twitter
- Single tweet: under 280 chars
- Thread: number tweets (1/ 2/ 3/) if multi-part
- Hook tweet must be punchy β no fluff
- No hashtags unless trending/niche; 0β2 max
- Conversational, not corporate
- Caption length: 125β150 chars for casual; up to 2,200 for storytelling
- First line must hook before truncation
- Hashtags: 5β15 in first comment or end of caption
- Emojis used as line breaks or accents (if their fingerprint supports this)
- CTA: "Save this", "Tag someone", "Comment below"
- Conversational, personal tone performs best
- Medium length: 40β80 words for engagement; longer for personal stories
- Questions drive comments
- Avoid links in the post body (reduces reach); put in comments
- Match subreddit culture precisely (ask which subreddit if relevant)
- Title is critical β front-load the value
- Body: be genuine, don't sound promotional
- No self-promotion unless in designated threads
Medium / Substack
- Long-form: 800β2,500 words typical
- Headline is everything β make it specific and compelling
- Use subheadings every 200β300 words
- End with a clear takeaway or reflection
Step 3 β Provide Two Timing Options
Always offer both options. Present them clearly:
Option A: Your Personal Best Times
(From content audit β only available if audit was run)
Based on your past posts, your best engagement times are:
- [Platform]: [Day] at [Time] β your posts average [x]% more engagement
- [etc.]
If no audit data is available: "Run content-audit to unlock your personal timing data."
Option B: Platform Research Best Times
(Use web_search to fetch current platform-specific best time data if needed)
General research-backed guidelines (always search for latest data before presenting):
| Platform | Best Days | Best Times (local) |
|---|---|---|
| Tue, Wed, Thu | 8β10am, 12pm, 5β6pm | |
| X/Twitter | MonβThu | 8am, 12pm, 5pm |
| Mon, Wed, Fri | 11amβ1pm, 7β9pm | |
| TueβThu | 1β4pm | |
| MonβFri | 9amβ12pm (varies by sub) |
Always note: "These are averages across millions of accounts. Your personal data (Option A) is more reliable for your specific audience."
Step 4 β Deliver Output
Present the ghostwritten post clearly, then the timing recommendations:
---
βοΈ YOUR POST ([Platform])
---
[Full post text, formatted for the platform]
---
π
WHEN TO POST
---
Option A β Your Data: [Timing from audit]
Option B β Platform Research: [Day] at [Time] ([source/rationale])
π‘ Recommendation: [Which option to choose and why, given their situation]
---
Step 5 β Iterate
Ask: "How does this feel? Too formal / too casual / not quite your voice?"
Apply fingerprint corrections dynamically. If they say it's off, ask:
- "Which part doesn't sound like you?"
- "Can you show me a sentence you'd rewrite?"
Update the style fingerprint notes if a consistent pattern emerges from corrections.
Batch Mode
If the user wants multiple posts at once (e.g., "write a week of content"):
- Confirm platforms, topics, and posting frequency
- Suggest a content mix based on their top-performing clusters
- Draft all posts
- Provide a full posting calendar with timing for each
Format as a table:
| Day | Platform | Topic/Angle | Post Snippet | Recommended Time |
|---|---|---|---|---|
| Monday | [topic] | [first line...] | 8:30am | |
| Tuesday | X | [topic] | [first line...] | 12:00pm |
| ... | ... | ... | ... | ... |