Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计通过

social-writer社会作家

Agent Skill

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

总安装

5,340

周安装

216

GitHub Stars

14

下载量

1,676
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/itechmeat/llm-code --skill social-writer

简介

social-writer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。

  • 它支持多源信息聚合、关键词匹配和结果排序,适用于需要高效搜索和筛选内容的场景。
  • 通过 GitHub 仓库安装,使用 npx skills add 命令添加指定技能,具体用法可参考原始 README 文档。
  • 安装前需确认权限范围、维护状态,并注意可能触发的联网、命令执行或文件读写操作。
  • 建议结合来源仓库进一步核验功能细节,确保符合实际使用环境和安全要求。

SKILL.md

Social Writer

Create platform-optimized social media content that sounds human, drives engagement, and builds audience.

Quick Navigation

TopicReference
X Single Postsx-posts.md
X Threadsx-threads.md
X Content Strategyx-strategy.md
Hook Patternshooks.md
LinkedInlinkedin.md
Threads & Instagramthreads-instagram.md
Facebookfacebook.md
AI Writing Avoidanceai-avoidance.md
Style Guidestyle-guide.md
Technical Blog Stylestechnical-styles.md

Platform Quick Reference

PlatformLimitBest LengthHashtagsKey Rule
X280 chars230-2801-2 maxHook in first line, use full space
LinkedIn3,000 chars1,3003-5Hook before "see more"
Threads500 chars400-500NoneConversational, no hashtags
Instagram2,200 charsVaries5-15Visual-first, line breaks
FacebookUnlimited<2502-3Community, engagement

Content Type Router

What are you creating?
│
├─ X?
│   ├─ Single insight/observation → x-posts.md
│   ├─ Multi-part story/tutorial → x-threads.md
│   └─ Content planning → x-strategy.md
│
├─ LinkedIn → linkedin.md
│   └─ Professional, B2B, thought leadership
│
├─ Threads/Instagram → threads-instagram.md
│   └─ Conversational, authentic, visual
│
├─ Facebook → facebook.md
│   └─ Community, engagement, events
│
└─ Technical blog → technical-styles.md
    ├─ Karpathy style (conversational, personal)
    └─ Deep technical (opinion-forward, contrarian)

Writing Workflow

1. Select Platform & Format

Choose based on:

  • Audience: Where do they spend time?
  • Content depth: Quick insight vs deep dive
  • Goal: Engagement, education, announcement

2. Load Style Reference

Before writing:

  1. Read platform-specific guide
  2. Read ai-avoidance.md — critical for human voice
  3. Read style-guide.md for tone

3. Draft Content

Apply platform constraints from start. Style informs structure.

4. Quality Check

Run through checklist below before posting.

Universal Quality Checklist

Voice

  • Sounds like a person, not AI?
  • Zero banned words (delve, unleash, harness, leverage)?
  • Zero em-dashes (—)?
  • Contractions used naturally?

Specificity

  • Includes names, numbers, tools, dates?
  • Concrete examples, not hypotheticals?
  • Would I bookmark this if someone else wrote?

Structure

  • Hook in first line?
  • Sentence lengths vary (5-40 words)?
  • Each paragraph/tweet can stand alone?

Value

  • Teaches something specific?
  • Actionable today?
  • From real experience?

X Quick Start

Single Post Pattern

[Hook - stop the scroll]

[Context or specific detail]

[Insight or learning]

[Optional: engagement question]

Example:

Shipped curation v1 for agents.foo today.

Discovery is way harder than app stores. Agents are conversations, not static features.

Had to rebuild around context matching instead of keyword search.

Thread Pattern

1/N [Bold hook - main insight] 👇

2/N [Context or setup]

3-N/N [Key points, one per tweet]

N/N [Summary + CTA]

Rules:

  • First tweet MUST end with 👇 or 🧵 to signal thread
  • Use N/M numbering (1/7, 2/7... 7/7)
  • Each tweet must stand alone
  • Max 5-7 tweets (longer = blog post)

High-Engagement Content Patterns

PatternStructureBest For
Shipped X, Learned YWhat shipped + key learning + why it mattersProject updates
How to XProblem + steps + key insightTutorials
Problem → SolutionProblem + failed attempts + what workedCase studies
ContrarianPopular belief + why wrong + your evidenceThought leadership
Tool RecommendationTool + specific benefit + real exampleResources

Content Selection: What to Share

Always Share ✓

  • Shipped work + learnings
  • Non-obvious insights
  • Tool recommendations with specifics
  • Solutions to common problems

Skip ✗

  • Generic progress updates
  • Plans before execution
  • Obvious observations
  • Engagement bait ("RT if you agree")
  • Vague hype

Critical Prohibitions

  • Do not use words: delve, unleash, harness, leverage, robust, seamless, game-changer, unlock
  • Do not use em-dashes (—) anywhere
  • Do not use "It's not X, it's Y" pattern
  • Do not ask for engagement ("RT if you agree", "What do you think?")
  • Do not use formal transitions (Furthermore, Moreover, Additionally)
  • Do not write uniform sentence lengths
  • Do not skip the hook

Links

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

github-copilot

27.62%
按下载量换算463

OpenCode

25.73%
按下载量换算431

Claude Code

19.12%
按下载量换算320

kilo

13.07%
按下载量换算219

Gemini CLI

8.63%
按下载量换算145

windsurf

3.2%
按下载量换算54

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills