Buzz Social

Q: Why use Buzz Social on TypingMind?

Because you install it once and use it with any model. Buzz Social is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

Q: How do I install Buzz Social in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-social. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Q: Which AI models can use Buzz Social?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

Q: How many AI models can I use with Buzz Social?

As many as you like. As long as a model supports skills, you can use Buzz Social with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Q: Is the Buzz Social AI skill free?

Yes. It is published on GitHub by jeremylongshore under the MIT license. You only pay your own AI provider for the tokens you use.

Q: What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

Q: How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

CommunityPopular

jeremylongshore

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".

Overview

Publisher	jeremylongshore
Repository	`tons-of-skills-marketplace`
Skill name	`buzz-social`
Stars	2.8K
Forks	409
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by jeremylongshore on GitHub. Read the source before you install it.

Installation

Install the Buzz Social AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-social
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-social

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git /tmp/tons-of-skills-marketplace
mkdir -p .claude/skills
cp -r /tmp/tons-of-skills-marketplace/plugins/ai-agency/tonone/skills/buzz-social .claude/skills/buzz-social

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Buzz Social in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Buzz Social on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Buzz Social is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Buzz Social AI skill do?

Why use Buzz Social on TypingMind?

Because you install it once and use it with any model. Buzz Social is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Buzz Social in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/buzz-social. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Buzz Social?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Buzz Social?

As many as you like. As long as a model supports skills, you can use Buzz Social with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Buzz Social AI skill free?

Yes. It is published on GitHub by jeremylongshore under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Brand Voice

affaan-m

CommunityPopular

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants…

Crosspost

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user…

Social Media Content Calendar

NousResearch

OrganizationPopular

Plan multi-platform social campaigns: briefs to posting.

Design Taste Frontend

Leonxlnx

CommunityPopular

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions…

103.1K

37 files

View

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Social Media Content

Steps

Step 0: Clarify Platform and Goal

Step 1: Platform Rules

Step 2: Write the Content

Step 3: Timing and Frequency

Step 4: Produce Social Assets

Delivery

Frequently asked questions

Related AI Skills

Set up your own AI workspace now