buzz-social

本条目收录公开技能“buzz-social”,按来源分类归入「运营社媒账号」使用场景、「产品与运营」职业。目录标签:ai-lab、社交媒体、内容撰写、Hacker News。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "buzz-social":https://skillpi.com/zh/skills/deepskill-3ce0b2773808b35b50ea832c95fa9bddf90966fe8b8b0f49f8feb456177f8f06。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/buzz-social/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/buzz-social --skill buzz-social
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目收录公开技能“buzz-social”,按来源分类归入「运营社媒账号」使用场景、「产品与运营」职业。目录标签:ai-lab、社交媒体、内容撰写、Hacker News。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: buzz-social
description: 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".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---

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

当前收录版本

0.1.0

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值92/100
评分依据

覆盖 Hacker News、Twitter/X、LinkedIn、Reddit、GitHub 等多个开发者核心社交平台

触发精准88/100
评分依据

触发词覆盖全面,包括“撰写 HN 帖子”、“起草社交媒体帖子”等典型用户表达

结构规范94/100
评分依据

分步骤清晰(Step 0-4),每步有明确目标与执行要点

执行可靠90/100
评分依据

工具来源明确且均为通用安全工具(如 WebSearch、AskUserQuestion)

证据可验 (前四项均值)91/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。