Claude Content Writer
Writing skill for blog posts, LinkedIn updates, and email newsletters tuned to sound human and reduce default AI-writing tells.
Overview
sociilabs/claude-content-writer targets a painful growth problem: drafts that read as generic AI. It focuses on blog, LinkedIn, and newsletter output with anti-slop framing, making it a strong pair with SEO/GEO skills that generate first drafts.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
git clone https://github.com/sociilabs/claude-content-writer.git ~/.claude/skills/claude-content-writerHow to use it
Share brand voice samples and the assignment. Ask for a humanized draft, then run an editorial pass for claims and SEO/GEO requirements.
Example prompts
- “Rewrite this SEO draft so it sounds like our brand voice (samples attached) and remove AI tells.”
- “Write a newsletter issue from these 5 product updates in a natural founder tone.”
- “Draft 7 LinkedIn posts from this launch brief; vary hooks and avoid buzzword stacking.”
Use cases and examples
- Humanized blog drafts
- LinkedIn post batches
- Newsletter copy without AI tells
- Editorial rewrite of SEO first drafts
- Content style calibration from samples
Prerequisites
- Claude Code, Claude.ai Skills, or another Agent Skills–compatible host
- Product/brand context (ICP, offer, URLs, constraints) for grounded outputs
- Optional: `.agents/product-marketing.md` or `.claude/product-marketing.md` in the repo
- Permission to install third-party skills — audit SKILL.md first
- Optional: analytics or ad-platform access when the task needs real performance data
Tips
- Keep triggers specific so Claude Content Writer only fires when relevant.
- Audit SKILL.md and any bundled scripts before production use.
- Pair with verification (analytics, QA, human edit) before shipping.
- Re-audit installed skills monthly to avoid context tax from unused packs.