Token导航 LogoToken导航

Agent Skill · 研究检索

social-media-posts(社交媒体帖子)

social-media-posts 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

social-media-posts 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 10,912。

总安装 11,948周安装 508GitHub Stars 750下载 4,186核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:social-media-posts(社交媒体帖子)
来源仓库:https://github.com/jezweb/claude-skills
仓库路径:skills/social-media-posts
安装命令:
npx skills add https://github.com/jezweb/claude-skills --skill social-media-posts
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jezweb/claude-skills --skill social-media-posts

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于社交媒体帖子内容分析、关键词匹配或发布策略研究等场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。安装前需确认权限范围、维护状态,以及是否涉及联网或文件操作。

social-media-posts 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/social-media-posts

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jezweb/claude-skills --skill social-media-post…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

social-media-posts 怎么安装?

在终端执行 npx skills add https://github.com/jezweb/claude-skills --skill social-media-posts。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

social-media-posts 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

social-media-posts 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

social-media-posts 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

social-media-posts 用的人多吗?

公开数据是累计安装 11,948 次,近一周安装 508 次,下载 4,186 次,GitHub 750 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

social-media-posts 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
social-media-posts

社交媒体帖子 · 本页

11,948750需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Social Media Post Generator

Create platform-specific social media posts that respect each platform's conventions, character limits, and audience expectations. Produces copy-paste-ready content.

Modes

From Scratch

User provides topic + key points. Generate posts for selected platforms.

From Content

User provides existing content (blog post, newsletter, announcement, press release). Repurpose into platform-appropriate posts.

Campaign

Generate a coordinated set of posts across all platforms for a single launch, announcement, or event. Includes posting sequence and timing suggestions.

Workflow

1. Gather Input

FieldRequiredExample
Topic or source contentYes"We just launched a new feature" or path to blog post
Target platformsYesLinkedIn, Facebook, Instagram, Reddit
ToneNoProfessional, casual, enthusiastic, educational
CTANo"Try it free", "Read more", "Comment your thoughts"
Link to includeNohttps://example.com/blog/new-feature
Image available?NoYes/no — affects post structure

If the user provides a file path or URL to existing content, read it first and extract the key messages.

2. Generate Per-Platform Posts


LinkedIn

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:

  • Hook must work in first 2 lines (before "…see more" at ~210 chars)
  • Use line breaks liberally — wall-of-text kills engagement
  • Ask a question at the end to drive comments
  • Hashtags: 3-5 max, mix broad (#Marketing) and niche (#CloudflareWorkers)
  • Links in comments perform better than in post body (algorithm penalty)
  • No emoji overload — 1-2 max, or none for serious topics

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

Facebook

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:

  • Link posts: Facebook auto-generates a preview card — don't repeat the headline in your text
  • Short posts (under 130 chars) get larger text rendering in feed
  • Questions and polls drive highest engagement
  • Tag relevant pages when mentioning partners/clients
  • Hashtags: 1-3 or none — Facebook hashtags are less effective than other platforms
  • Emojis are welcome but don't overdo (2-3 max)

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?

Instagram

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:

  • First 125 characters must carry the message (everything after is hidden behind "…more")
  • No clickable links in captions — direct to "link in bio"
  • Hashtags: 20-30 in first comment (not in caption) for discoverability
  • Mix hashtag sizes: 5 large (1M+ posts), 10 medium (100K-1M), 10 niche (<100K)
  • Emojis are part of the language — use them naturally
  • Carousel posts: include a swipe CTA ("Swipe for the full breakdown →")
  • Stories: prompt action ("Reply with 🔥 if you relate")

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]

Reddit

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:

  • Title is everything — Reddit lives and dies by titles
  • NO self-promotion feel — lead with value, not product
  • Each subreddit has different norms — check the rules before posting
  • Don't use hashtags (not a Reddit convention)
  • Don't use emojis in titles (feels out of place on most subreddits)
  • Share the insight, not the product. "Here's what we learned" > "Check out our new feature"
  • Cross-posting: adapt tone per subreddit (r/startups vs r/webdev vs r/smallbusiness)

Subreddit suggestions by topic:

TopicSubreddits
Product launchr/SideProject, r/startups, r/indiehackers
Web devr/webdev, r/javascript, r/reactjs
Designr/web_design, r/UI_Design
Businessr/smallbusiness, r/Entrepreneur
Techr/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?

3. Image Recommendations

For each platform, suggest image requirements:

PlatformFormatDimensionsNotes
LinkedInPNG/JPG1200×627Text overlay OK, keep key message in centre
FacebookPNG/JPG1200×630Minimal text (old 20% rule still affects reach)
InstagramPNG/JPG1080×1080Visual-first — image must work without caption
RedditPNG/JPGVariesOptional — 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.

4. Output Format

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.

Campaign Mode

For launches or announcements, generate a posting sequence:

TimingPlatformPost type
Day -1LinkedInTeaser / behind-the-scenes
Day 0 (morning)All platformsAnnouncement post
Day 0 (afternoon)Instagram StoriesQuick video/carousel
Day +1RedditValue-focused discussion
Day +3LinkedInResults/learnings follow-up
Day +7FacebookCustomer reaction / testimonial

Quality Rules

  1. Never copy-paste the same text across platforms — each platform has different conventions
  2. No corporate jargon — "leverage our synergies" belongs nowhere
  3. Front-load the value — every platform truncates. The first line must work standalone.
  4. Match the platform culture — LinkedIn is not Instagram is not Reddit
  5. Include a reason to engage — question, poll, or genuine discussion prompt
  6. Check character limits — LinkedIn (3,000), Facebook (63,206), Instagram caption (2,200), Reddit title (300)
  7. Never fake engagement — no "Drop a 🔥 if you agree" on LinkedIn, no hashtag spam on Reddit

平台分布

Codex

39.28%
按下载量换算1,644

Claude

27.96%
按下载量换算1,170

Cursor

19.06%
按下载量换算798

Gemini CLI

9.27%
按下载量换算388

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills