| name | banger-longform-written |
| description | Write long-form written posts: LinkedIn posts, Substack newsletter issues, and Facebook Group posts. Use whenever the user asks to "write a LinkedIn post", "write my newsletter", "substack post", "newsletter issue", "facebook group post", "a post for my community", "turn this into a LinkedIn post", or wants professional/newsletter/community written content with a hook, body, and CTA. Part of the BANGERS suite; applies the teaching clarity and story-led hooks of the reference creators, adaptable to any creator's niche. Reach for this for any written post destined for LinkedIn, Substack, or a Facebook Group.
|
| metadata | {"version":"0.2.0","suite":"bangers"} |
Banger Long-Form Written — LinkedIn, Substack & Facebook Group posts
Each of these platforms rewards something different: LinkedIn rewards dwell time + saves/shares on a narrow topic; Substack rewards restack-worthy standalone ideas + a consistent owned-audience relationship; Facebook Groups reward early comments and native, un-linked content. Write to the surface.
Freshness gate
Before applying a platform benchmark, algorithm claim, policy, feature-availability statement, or numeric performance claim from this skill or the platform playbook, check references/research/source-ledger.md for non-expired support. If support is missing or past its review date, run banger-research, qualify the claim as unverified, or omit it. Never present a legacy value as current truth.
Load first
${CLAUDE_PLUGIN_ROOT}/references/frameworks/voice-and-audience.md (the creator's own defined audience — ask once if it isn't set) + ${CLAUDE_PLUGIN_ROOT}/references/creators/matt-pocock.md (one clear idea, warm/low-ego, cast the reader as capable) + ${CLAUDE_PLUGIN_ROOT}/references/creators/_synthesis.md.${CLAUDE_PLUGIN_ROOT}/references/platforms/platform-playbook.md §6 (LinkedIn), §7 (Substack), §9 (Facebook Groups). Confirm the target platform — the rules diverge sharply.
LinkedIn post
- Hook in the first ~150 chars (that's all that shows before "see more"); open with a question or a contrarian/data line (a question in line 1 lifts comments ~32%).
- Engineer dwell time — short 3–4-line paragraphs, white space, one narrow idea, a story or concrete example. 800–1,600 chars is the sweet spot.
- Win the golden hour — end with a specific question; plan to reply to every comment in the first 60–120 min.
- No links in the body (~60% reach cut) — and the link-in-first-comment trick is now penalized too; tell the user to add any link after the post gains traction, or in a DM/follow-up.
- Optimize the CTA toward saves and shares ("save this for the next time you…"). 0–3 niche hashtags, optional. Keep to a consistent topic so the interest-graph model locks your "topic DNA."
Substack newsletter issue
- Subject line ≤100 chars, front-load the value (specific/curiosity beats clickbait) — it's the email subject AND the Notes title.
- Structure: a strong opening that earns the open, one core idea developed with headers/pull-quotes/white space, a clear takeaway, and a light CTA (reply, restack, share). Suggest a 1200×630 cover concept.
- Design for restacks — pull out 1–3 standalone lines/ideas that work as Notes (the restack is now a top distribution signal). Provide those Notes.
- Don't hard-paywall early; grow the free list. Recommend turning on Recommendations.
Facebook Group post
- Short and question-led (≤~20 words gets ~40% more engagement). Open with a pain-point question that triggers early comments (comments in the first 30–60 min multiply reach).
- Native only — never a bare external link (links rank lowest); if there's a video, upload it natively with captions and a 3-sec hook. Consider a poll.
- Warm, community tone; reply fast to every comment.
Output format
Deliver the finished post ready to paste, formatted for the target platform (line breaks and all). Include: the hook line called out, a note on where any link goes, the suggested first-comment/reply to seed the golden hour, and (Substack) the pull-out Notes + cover concept. If the user drafts these as themselves and a my-writing-style profile exists, draft from it; if they then correct the voice, offer once to save the change to their profile.
Living writing gate
Read ${CLAUDE_PLUGIN_ROOT}/references/frameworks/writing-quality.md before drafting. Apply creator-specific constraints and treat detector results as weak evidence.
Quality bar
Confirm the hook lands in the visible-before-cutoff zone, the post holds ONE idea, links are placed correctly for the platform, and there's a concrete reason to comment/restack/share.
