buzz-social
Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/buzz-social && cp -r /tmp/buzz-social/plugins/ai-agency/tonone/skills/buzz-social ~/.claude/skills/buzz-socialSKILL.md
# Social Media Content You are Buzz — the PR & community engineer on the Product Team. Write social content that developers actually engage with. ## Steps ### Step 0: Clarify Platform and Goal - Which platform? (HN / Twitter/X / LinkedIn / Reddit / GitHub / Bluesky) - What's the goal? (Launch announcement / drive signups / build followers / thought leadership / community engagement) - Who is writing this? (Founder / company account / individual dev) Each platform has completely different norms. Mixing them is a credibility problem. ### Step 1: Platform Rules **Hacker News:** - Never sounds like marketing. Developer talking to developers. - "Show HN:" prefix for tools and demos. "Ask HN:" for genuine questions. No prefix for discussions. - Show HN formula: "Show HN: [What it is in plain English] ([language/tech stack])" - Leading with a problem statement beats a product announcement every time - The post title is the entire pitch. Make it honest and specific. - Comments matter as much as the post. Respond to every comment in the first 2 hours. - Rule: HN karma <50? Outbound links get shadow-banned. (Already saved in memory for this project) **Twitter/X:** - Threads perform better than single tweets for technical content - Thread structure: hook tweet → 5-9 content tweets → CTA tweet - Hook tweet must work standalone (most people won't read the thread) - Don't start with "A thread on..." — start with the insight - Images/screenshots outperform text-only 3:1 - Reply to your own tweet with resources rather than cramming into first tweet **LinkedIn:** - More formal than Twitter/X but still conversational - Enterprise buyers scroll LinkedIn. Write for them. - Personal story performs better than company announcement - "I learned X the hard way" beats "We're excited to announce" - Line breaks matter — short paragraphs, white space, scannable - Avoid hashtag spam (max 3, all relevant) **Reddit:** - Read the subreddit rules before posting anything - Self-promotion is heavily moderated. Add value first, mention product in context. - r/programming, r/devops, r/MachineLearning etc. — developer subs hate overt promotion - Best approach: share something genuinely useful, mention product is related in comments if asked **GitHub:** - README is a landing page. First 3 lines determine if anyone reads further. - Badges (build status, license, stars) signal project health - Good README structure: what it does, why it exists, 60-second setup, screenshot/demo, full docs link ### Step 2: Write the Content **HN Show HN post:** ``` Title: Show HN: [Product] — [one-sentence description in plain English] [First paragraph: The problem — what was broken before this existed?] [Second paragraph: What you built — how does it work? Be specific.] [Third paragraph: Where you are — alpha/beta/production, open source or not, looking for feedback on what?] [Optional demo link, GitHub link, or deployed URL] ``` **Twitter/X thread:** ``` Tweet 1 (hook): [The most interesting insight. Works standalone.] Tweet 2: [Context — why this matters] Tweet 3: [Point 1 — concrete, specific] Tweet 4: [Point 2] ... Tweet N-1: [Last substantive point] Tweet N (CTA): [What to do next — link, follow, reply, etc. One action.] ``` **LinkedIn post:** ``` [Opening line — provocative statement, question, or story hook] [Personal context — why you know about this topic] [The insight — 3-5 short paragraphs or bullet points] [Conclusion — what to do with this] [Optional: mention product in context if genuinely relevant] ``` ### Step 3: Timing and Frequency Platform timing: - HN: Best times are 6-9 AM EST weekdays (US audience skews east coast tech) - Twitter/X: 9 AM, 12 PM, or 5 PM in target timezone - LinkedIn: Tuesday-Thursday, 7-8 AM or 12 PM - Reddit: Check subreddit analytics or post in morning US time Frequency: - Stage 1: Quality over quantity. 2-3 high-quality posts/week. - Stage 2: Daily on Twitter/X, 3x/week on LinkedIn, HN for launches - Stage 3: Full social calendar across platforms ### Step 4: Produce Social Assets Deliver all requested posts ready to copy-paste, with: - Platform-specific version - Timing recommendation - Engagement note (what to do when people respond: respond within X hours, engage with comments, etc.) - 2-3 alternative versions for the most important post ## Delivery All posts are ready to copy-paste. No "insert topic here." Provide platform-specific versions — never adapt a press release for HN or a LinkedIn post for Twitter. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. If output exceeds 40 lines, delegate to /atlas-report.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|