npx skills add https://github.com/jezweb/claude-skills --skill social-media-posts创建符合各平台规范、字符限制和受众期望的特定平台社交媒体帖子。生成可直接复制粘贴的内容。
用户提供主题 + 关键点。为选定的平台生成帖子。
用户提供现有内容(博客文章、新闻通讯、公告、新闻稿)。将其改写成适合平台的帖子。
为一次发布、公告或活动,在所有平台上生成一套协调的帖子。包括发布顺序和时间建议。
| 字段 | 必填 | 示例 |
|---|---|---|
| 主题或源内容 | 是 | "我们刚刚发布了一个新功能" 或博客文章路径 |
| 目标平台 | 是 | LinkedIn, Facebook, Instagram, Reddit |
| 语气 | 否 | 专业、随意、热情、教育性 |
| 行动号召 | 否 | "免费试用"、"阅读更多"、"评论分享你的想法" |
| 包含的链接 | 否 | https://example.com/blog/new-feature |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 有可用图片? | 否 | 是/否 — 影响帖子结构 |
如果用户提供了现有内容的文件路径或 URL,请先读取并提取关键信息。
受众 : 专业人士、B2B、行业同行 语气 : 权威但平易近人,思想领导力 最佳长度 : 1,200–1,500 字符(较长的帖子表现良好)
结构 :
[吸引人的开头 — 必须在"查看更多"截断前抓住注意力]
[空行]
[2-3个短段落,段落间换行]
[空行]
[行动号召或问题以驱动评论]
[空行]
[3-5个相关主题标签]
规则 :
图片规格 : 链接预览用 1200×627px (1.91:1),或独立图片用 1080×1080 (1:1)
示例 :
We just shipped something we've been building for 6 months.
It started as a "wouldn't it be nice if…" conversation and turned
into our most requested feature. Here's what we learned:
→ Users don't want more features. They want fewer clicks.
→ The prototype we almost killed became the final product.
→ Shipping weekly forced us to cut scope ruthlessly.
The full story is in our latest blog post (link in comments).
What's the hardest product decision you've made this year?
#ProductDevelopment #StartupLife #BuildInPublic
受众 : 混合 — 朋友、家人、社区、本地企业 语气 : 对话式、温暖、以社区为中心 最佳长度 : 80–150 字符以促进互动,讲故事可达 500 字符
结构 :
[开场白 — 对话式、有共鸣]
[1-2个短段落]
[链接(如适用)— Facebook 会生成预览卡片]
[互动提示 — 问题或投票]
规则 :
图片规格 : 链接预览用 1200×630px (1.91:1),照片帖子用 1080×1080 (1:1)
示例 :
6 months ago we started building something our users kept asking for.
Today it's live. 🚀
We wrote up the full story — the pivots, the almost-killed prototype,
and why "fewer clicks" won over "more features."
[link]
What feature have you shipped that surprised you?
受众 : 视觉优先、年轻人群、生活方式/品牌导向 语气 : 真实、视觉叙事、突出个性 最佳长度 : 关键信息在前 125 字符内(截断点),完整标题最多 2,200 字符
结构 :
[第一行 — 必须能独立成句(在"…更多"之前)]
[空行]
[故事或细节 — 2-4个短段落]
[空行]
[行动号召 — 保存、分享、评论、个人简介中的链接]
.
.
.
[主题标签 — 在第一条评论中或用点分隔]
规则 :
图片规格 : 信息流 1080×1080 (1:1),纵向 1080×1350 (4:5),快拍/Reels 1080×1920 (9:16)
示例 :
We shipped our most requested feature today. Here's the story 👇
Six months ago, someone on our team said "wouldn't it be nice
if users could do this in one click instead of five?"
We almost killed the prototype twice. But our users kept asking
for it. So we shipped it.
The biggest lesson? Your users don't want more features.
They want fewer clicks.
Full story → link in bio
💬 What's one feature you wish was simpler in your favourite app?
第一条评论 :
#ProductLaunch #StartupLife #BuildInPublic #TechStartup
#ProductDevelopment #UXDesign #SaaS #FeatureLaunch
[... 20-30 total hashtags]
受众 : 特定社区,重视真实性,反感营销 语气 : 真诚、价值优先、对话式、绝不推销 最佳长度 : 标题 100-150 字符,正文因版块而异
结构 :
标题: [描述性、价值导向 — 非点击诱饵]
正文:
[背景 — 为什么这对这个社区很重要]
[实质内容 — 你学到、构建或发现了什么]
[可选:更多细节的链接]
[讨论提示 — 真诚的问题]
规则 :
按主题推荐的版块 :
| 主题 | 版块 |
|---|---|
| 产品发布 | r/SideProject, r/startups, r/indiehackers |
| 网页开发 | r/webdev, r/javascript, r/reactjs |
| 设计 | r/web_design, r/UI_Design |
| 商业 | r/smallbusiness, r/Entrepreneur |
| 科技 | r/programming, r/technology |
示例 :
Title: After 6 months of building, the biggest lesson was
"users want fewer clicks, not more features"
We built a feature our users kept requesting. Halfway through
we almost killed it because the prototype felt clunky.
What saved it: we stopped adding capabilities and started
removing steps. The final version does less than the prototype
but users complete the task in 1 click instead of 5.
Three things I'd tell past-me:
1. Prototype with your heaviest users, not your most vocal ones
2. "Ship weekly" forces you to cut scope — that's a feature
3. The thing users ask for and the thing they need are different
Anyone else had a similar experience where removing features
improved the product?
为每个平台建议图片要求:
| 平台 | 格式 | 尺寸 | 备注 |
|---|---|---|---|
| PNG/JPG | 1200×627 | 可添加文字叠加,关键信息保持在中心 | |
| PNG/JPG | 1200×630 | 最少文字(旧的 20% 规则仍影响触及率) | |
| PNG/JPG | 1080×1080 | 视觉优先 — 图片无需标题也能传达信息 | |
| PNG/JPG | 各异 | 可选 — 纯文本帖子通常表现更好 |
如果 ai-image-generator 技能可用,建议使用它以正确的宽高比生成配套图片。
在每个清晰标记的区块中呈现帖子:
═══ LINKEDIN ═══
[post content]
═══ FACEBOOK ═══
[post content]
═══ INSTAGRAM (Caption) ═══
[caption content]
═══ INSTAGRAM (First Comment — Hashtags) ═══
[hashtags]
═══ REDDIT (r/subreddit) ═══
Title: [title]
Body: [body]
如果用户希望保存以便安排发布,则保存到 .jez/artifacts/social-posts-[topic].md。
针对发布或公告,生成发布序列:
| 时间 | 平台 | 帖子类型 |
|---|---|---|
| 发布前 1 天 | 预告 / 幕后花絮 | |
| 发布日(上午) | 所有平台 | 公告帖子 |
| 发布日(下午) | Instagram Stories | 快速视频/轮播 |
| 发布后 1 天 | 价值导向的讨论 | |
| 发布后 3 天 | 结果/经验总结跟进 | |
| 发布后 7 天 | 客户反馈 / 推荐 |
每周安装量
110
仓库
GitHub 星标数
643
首次出现
10 天前
安全审计
安装于
opencode107
kimi-cli106
gemini-cli106
amp106
cline106
github-copilot106
Create platform-specific social media posts that respect each platform's conventions, character limits, and audience expectations. Produces copy-paste-ready content.
User provides topic + key points. Generate posts for selected platforms.
User provides existing content (blog post, newsletter, announcement, press release). Repurpose into platform-appropriate posts.
Generate a coordinated set of posts across all platforms for a single launch, announcement, or event. Includes posting sequence and timing suggestions.
| Field | Required | Example |
|---|---|---|
| Topic or source content | Yes | "We just launched a new feature" or path to blog post |
| Target platforms | Yes | LinkedIn, Facebook, Instagram, Reddit |
| Tone | No | Professional, casual, enthusiastic, educational |
| CTA | No | "Try it free", "Read more", "Comment your thoughts" |
| Link to include | No | https://example.com/blog/new-feature |
| Image available? | No | Yes/no — affects post structure |
If the user provides a file path or URL to existing content, read it first and extract the key messages.
Audience : Professionals, B2B, industry peers Tone : Authoritative but approachable, thought-leadership Optimal length : 1,200–1,500 characters (longer posts perform well)
Structure :
[Hook line — must grab attention before "see more" truncation]
[blank line]
[2-3 short paragraphs with line breaks between]
[blank line]
[CTA or question to drive comments]
[blank line]
[3-5 relevant hashtags]
Rules :
Image specs : 1200×627px (1.91:1) for link preview, or 1080×1080 (1:1) for standalone
Example :
We just shipped something we've been building for 6 months.
It started as a "wouldn't it be nice if…" conversation and turned
into our most requested feature. Here's what we learned:
→ Users don't want more features. They want fewer clicks.
→ The prototype we almost killed became the final product.
→ Shipping weekly forced us to cut scope ruthlessly.
The full story is in our latest blog post (link in comments).
What's the hardest product decision you've made this year?
#ProductDevelopment #StartupLife #BuildInPublic
Audience : Mixed — friends, family, community, local businesses Tone : Conversational, warm, community-focused Optimal length : 80–150 characters for engagement, up to 500 for storytelling
Structure :
[Opening hook — conversational, relatable]
[1-2 short paragraphs]
[Link (if applicable) — Facebook generates preview cards]
[Engagement prompt — question or poll]
Rules :
Image specs : 1200×630px (1.91:1) for link preview, 1080×1080 (1:1) for photo posts
Example :
6 months ago we started building something our users kept asking for.
Today it's live. 🚀
We wrote up the full story — the pivots, the almost-killed prototype,
and why "fewer clicks" won over "more features."
[link]
What feature have you shipped that surprised you?
Audience : Visual-first, younger demographic, lifestyle/brand-focused Tone : Authentic, visual storytelling, personality-forward Optimal length : Key message in first 125 chars (truncation point), full caption up to 2,200
Structure :
[First line — must work as standalone (before "…more")]
[blank line]
[Story or detail — 2-4 short paragraphs]
[blank line]
[CTA — save, share, comment, link in bio]
.
.
.
[Hashtags — in first comment OR separated by dots]
Rules :
Image specs : 1080×1080 (1:1) feed, 1080×1350 (4:5) portrait, 1080×1920 (9:16) stories/reels
Example :
We shipped our most requested feature today. Here's the story 👇
Six months ago, someone on our team said "wouldn't it be nice
if users could do this in one click instead of five?"
We almost killed the prototype twice. But our users kept asking
for it. So we shipped it.
The biggest lesson? Your users don't want more features.
They want fewer clicks.
Full story → link in bio
💬 What's one feature you wish was simpler in your favourite app?
First comment :
#ProductLaunch #StartupLife #BuildInPublic #TechStartup
#ProductDevelopment #UXDesign #SaaS #FeatureLaunch
[... 20-30 total hashtags]
Audience : Community-specific, values authenticity, allergic to marketing Tone : Genuine, value-first, conversational, never salesy Optimal length : Title 100-150 chars, body varies by subreddit
Structure :
Title: [Descriptive, value-focused — NOT clickbait]
Body:
[Context — why this matters to this community]
[The substance — what you learned, built, or discovered]
[Optional: link to more detail]
[Discussion prompt — genuine question]
Rules :
Subreddit suggestions by topic :
| Topic | Subreddits |
|---|---|
| Product launch | r/SideProject, r/startups, r/indiehackers |
| Web dev | r/webdev, r/javascript, r/reactjs |
| Design | r/web_design, r/UI_Design |
| Business | r/smallbusiness, r/Entrepreneur |
| Tech | r/programming, r/technology |
Example :
Title: After 6 months of building, the biggest lesson was
"users want fewer clicks, not more features"
We built a feature our users kept requesting. Halfway through
we almost killed it because the prototype felt clunky.
What saved it: we stopped adding capabilities and started
removing steps. The final version does less than the prototype
but users complete the task in 1 click instead of 5.
Three things I'd tell past-me:
1. Prototype with your heaviest users, not your most vocal ones
2. "Ship weekly" forces you to cut scope — that's a feature
3. The thing users ask for and the thing they need are different
Anyone else had a similar experience where removing features
improved the product?
For each platform, suggest image requirements:
| Platform | Format | Dimensions | Notes |
|---|---|---|---|
| PNG/JPG | 1200×627 | Text overlay OK, keep key message in centre | |
| PNG/JPG | 1200×630 | Minimal text (old 20% rule still affects reach) | |
| PNG/JPG | 1080×1080 | Visual-first — image must work without caption | |
| PNG/JPG | Varies | Optional — text posts often perform better |
If the ai-image-generator skill is available, suggest using it to generate companion images with the right aspect ratios.
Present each post in a clearly labelled block:
═══ LINKEDIN ═══
[post content]
═══ FACEBOOK ═══
[post content]
═══ INSTAGRAM (Caption) ═══
[caption content]
═══ INSTAGRAM (First Comment — Hashtags) ═══
[hashtags]
═══ REDDIT (r/subreddit) ═══
Title: [title]
Body: [body]
Save to .jez/artifacts/social-posts-[topic].md if the user wants to keep them for scheduling.
For launches or announcements, generate a posting sequence:
| Timing | Platform | Post type |
|---|---|---|
| Day -1 | Teaser / behind-the-scenes | |
| Day 0 (morning) | All platforms | Announcement post |
| Day 0 (afternoon) | Instagram Stories | Quick video/carousel |
| Day +1 | Value-focused discussion | |
| Day +3 | Results/learnings follow-up | |
| Day +7 | Customer reaction / testimonial |
Weekly Installs
110
Repository
GitHub Stars
643
First Seen
10 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
opencode107
kimi-cli106
gemini-cli106
amp106
cline106
github-copilot106
社交媒体内容策略指南:创建、优化与互动全流程 | 营销技能
39,000 周安装