Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

social-media-posts社交媒体帖子

Agent Skill

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

总安装

11,948

周安装

508

GitHub Stars

750

下载量

4,186
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于社交媒体帖子内容分析、关键词匹配或发布策略研究等场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围、维护状态,以及是否涉及联网或文件操作。
  • social-media-posts 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

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 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills