banger-threads

星标2

分支0

更新时间2026年7月13日 00:01

Write posts and threads for X/Twitter and Bluesky. Use whenever the user asks to "write a thread", "tweet about X", "write an X post", "twitter thread", "bluesky post", "turn this into a thread", "a hot take about Y", or wants short-form text posts, teaching threads, or single bangers for X or Bluesky. Part of the BANGERS suite; applies Matt Pocock's one-concept teaching threads and Theo/ThePrimeagen's defensible hot-take framing, adaptable to any creator's niche. Reach for this any time the deliverable is text posts for X or Bluesky.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

Jeff-Kazzee

Jeff-Kazzee/bangers

打开 GitHub 仓库查看创作者相关仓库

下载

Banger Threads — X / Bluesky posts that get replied to and reposted

On X, replies are weighted ~13–27× a like and reposts ~20×; the first 15 minutes decide virality; links in the main post cut reach 50–90%. On Bluesky, conversation momentum (replies/quotes) drives the Discover feed. So: write for conversation, front-load the hook, keep links out of the lead post.

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/creators/matt-pocock.md (one-concept posts, curiosity-gap hooks, show-don't-tell, the evergreen mega-thread) — the primary model for teaching threads.
${CLAUDE_PLUGIN_ROOT}/references/creators/theo.md (controversial-but-defensible hot takes, steelman + verdict) — for opinion posts.
${CLAUDE_PLUGIN_ROOT}/references/frameworks/hooks-bank.md (text-post hooks) + ${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/platforms/platform-playbook.md §5 (X) and §8 (Bluesky) — limits, weights, link rules, cadence.

Two core formats

A. The teaching thread / single tip (Pocock). Isolate ONE insight. Post 1 = a curiosity-gap hook (a number + a promise; the answer NOT given away). Middle posts = one step/point each, each with the actual proof shown (a screenshot of the real result, a before/after). Final post = the payoff + a question or soft CTA. If it's evergreen, frame it as a living thread you'll keep adding to.

B. The hot take / reaction (Theo). Lead with the claim. Back it with real experience/reasoning. Steelman the other side, then land a clear verdict. Stay on the "controversial but defensible" line — attack the idea, not people; be correctable. Defensibility test: could a smart person agree after hearing your reasoning? If it only works on people who don't know the topic, it's ragebait — cut it.

Writing rules

First line is the whole hook — only ~280 chars render before "Show more" (X) and Bluesky posts are 300 chars hard. Front-load the payoff.
One idea per post. If a post needs "and also," split it.
Invite replies — end on a genuine question; be ready to reply to your own thread in the first 15–30 min (replies are the top signal).
Links go in a reply, never the lead post. State this explicitly in the output.
0–1 hashtag on X (3+ trips spam filters); 2–3 on Bluesky (they route into topic feeds).
Bluesky ≠ X — don't hand over a verbatim cross-post; conversational reframes perform better. Note this if producing for both.
Write to the audience's level (per voice-and-audience.md): define in plain English any term they wouldn't know; make the reader feel capable.

Output format

For a thread: number each post (1/, 2/…), keep each within the character limit, mark where a [screenshot/image] or [attached clip] goes, and put any [link → in a reply] at the end.
For single posts: give 3–5 variants (mix teaching + hot-take + curiosity engines).
Add a one-line note on best posting time / that the first-15-min reply push matters.
If adapting for both X and Bluesky, provide a distinct version for each.

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: post 1 stops the scroll on its own, exactly one idea per post, a real reason to reply, no link in the lead, and (for hot takes) it passes the defensibility test.

同仓库更多 Skills

同仓库

bangers

Jeff-Kazzee/bangers

Social-media content system. Use whenever the request is about making content: what to post, content ideas, hooks, titles, thumbnails, YouTube or short-form video scripts, X/Bluesky threads, LinkedIn or Substack or newsletter posts, Facebook Group posts, Instagram or LinkedIn carousels, technical explainers and tutorials, video edit plans and captions, repurposing one source across platforms, or checking whether a draft reads as AI-written and how to disclose AI use. Studies public creator and platform mechanics and adapts them to the author's own audience and voice.

2026-07-272

bangers

Jeff-Kazzee/bangers

Route social-media research, ideas, packaging, writing, scripts, editing, and platform-native repurposing through the BANGERS skill suite.

2026-07-272

banger-detector

Jeff-Kazzee/bangers

Verify that a draft is authentically the author's work and decide how to disclose AI assistance. Use whenever the user asks to "run an AI detector", "check if this passes AI detection", "does this sound AI-written", "will this get flagged", "check my AI score", "humanize this", or wants to state honestly how AI was used in a piece. Part of the BANGERS suite. Runs detectors as one weak diagnostic inside a provenance and voice check, records receipts, and refuses the moves that damage true writing to chase a score.

2026-07-272

banger-explainer

Jeff-Kazzee/bangers

Write technical explainers and teaching content: how-it-works posts, tutorials, build logs, architecture walkthroughs, "why this breaks" pieces, and developer or practitioner threads and essays. Use whenever the user asks to "explain how X works", "write a tutorial", "technical thread", "write up this build", "teach this", "explainer post", "walk through my architecture", or wants content where the reader must understand a mechanism well enough to repeat it. Part of the BANGERS suite. Applies the frame/payload split: the author's voice carries the frame, technical clarity carries the explanation. Reach for this whenever the reader has to learn something mechanical, not just agree with an opinion.

2026-07-272

banger-carousels

Jeff-Kazzee/bangers

Design slide carousels and slide decks for social: Instagram carousels, LinkedIn document/PDF carousels, and short explainer slide decks. Use whenever the user asks to "make a carousel", "instagram carousel", "linkedin carousel", "carousel about X", "slides for a post", "swipe post", "turn this into slides", or a "slide deck" for social. Part of the BANGERS suite; applies one-idea-per-slide clarity and strong-first-slide packaging. Reach for this any time the deliverable is a multi-slide swipeable/scrollable visual post.

2026-07-252

banger-edit

Jeff-Kazzee/bangers

Produce editing and recording assets for any editor — DaVinci Resolve, Adobe Premiere, CapCut, Descript — plus OBS for recording: cut sheets / edit decision lists, burned-in caption scripts and SRT subtitle files, marker/chapter CSVs, B-roll and text-overlay cue sheets, vertical reframe plans, and OBS scene/recording setups. Use whenever the user asks to "edit this video", "davinci", "resolve", "premiere", "capcut", "descript", "obs setup", "how should I cut this", "cut sheet", "edit decision list", "captions for my video", "make an SRT", "add markers", "reframe to vertical", or wants a recording/editing plan. Part of the BANGERS suite. This skill outputs instructions and files the user feeds into their editor and OBS (it does not drive an NLE directly).

2026-07-252

name	banger-threads
description	Write posts and threads for X/Twitter and Bluesky. Use whenever the user asks to "write a thread", "tweet about X", "write an X post", "twitter thread", "bluesky post", "turn this into a thread", "a hot take about Y", or wants short-form text posts, teaching threads, or single bangers for X or Bluesky. Part of the BANGERS suite; applies Matt Pocock's one-concept teaching threads and Theo/ThePrimeagen's defensible hot-take framing, adaptable to any creator's niche. Reach for this any time the deliverable is text posts for X or Bluesky.
metadata	{"version":"0.2.0","suite":"bangers"}

Banger Threads — X / Bluesky posts that get replied to and reposted

Freshness gate

Load first

${CLAUDE_PLUGIN_ROOT}/references/creators/matt-pocock.md (one-concept posts, curiosity-gap hooks, show-don't-tell, the evergreen mega-thread) — the primary model for teaching threads.
${CLAUDE_PLUGIN_ROOT}/references/creators/theo.md (controversial-but-defensible hot takes, steelman + verdict) — for opinion posts.
${CLAUDE_PLUGIN_ROOT}/references/frameworks/hooks-bank.md (text-post hooks) + ${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/platforms/platform-playbook.md §5 (X) and §8 (Bluesky) — limits, weights, link rules, cadence.

Two core formats

Writing rules

First line is the whole hook — only ~280 chars render before "Show more" (X) and Bluesky posts are 300 chars hard. Front-load the payoff.
One idea per post. If a post needs "and also," split it.
Invite replies — end on a genuine question; be ready to reply to your own thread in the first 15–30 min (replies are the top signal).
Links go in a reply, never the lead post. State this explicitly in the output.
0–1 hashtag on X (3+ trips spam filters); 2–3 on Bluesky (they route into topic feeds).
Bluesky ≠ X — don't hand over a verbatim cross-post; conversational reframes perform better. Note this if producing for both.
Write to the audience's level (per voice-and-audience.md): define in plain English any term they wouldn't know; make the reader feel capable.

Output format

For a thread: number each post (1/, 2/…), keep each within the character limit, mark where a [screenshot/image] or [attached clip] goes, and put any [link → in a reply] at the end.
For single posts: give 3–5 variants (mix teaching + hot-take + curiosity engines).
Add a one-line note on best posting time / that the first-15-min reply push matters.
If adapting for both X and Bluesky, provide a distinct version for each.

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: post 1 stops the scroll on its own, exactly one idea per post, a real reason to reply, no link in the lead, and (for hot takes) it passes the defensibility test.