Token导航 LogoToken导航

Agent Skill · 研究检索

content(内容)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

content 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 64,959。

总安装 291周安装 12GitHub Stars 167下载 95核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/whawkinsiv/claude-code-skills --skill content

这个 Skill 是做什么的

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

content 用于辅助文档、Markdown 和内容稿件的整理与改写。适合在 Codex、Claude、Cursor、Gemini CLI 中提炼结构或统一术语。通过 npx skills add 命令从指定仓库安装并使用。使用时应保留项目已有事实,避免把未确认信息写成确定结论。

涉及对外文案时需控制语气,避免过度营销或夸大能力。

来源仓库内路径:skills/content

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

content 怎么安装?

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

content 支持哪些 AI 工具?

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

content 需要什么权限?

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

content 是免费的吗?

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

content 用的人多吗?

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

content 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
content

内容 · 本页

291167只读未明确通过

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

SKILL.md 原文

Content Marketing & Build-in-Public

For a solo founder, content IS the marketing department. This skill helps you pick a platform, build an audience through authentic sharing, and convert followers into customers — without a marketing team or ad budget.

Core Principles

  • Content is not marketing. Content is proof of expertise, proof of work, and proof that you understand your audience's problems better than anyone else.
  • Build-in-public is the highest-ROI content strategy for a solo founder. It costs nothing, builds trust, and creates a moat of authenticity no competitor can copy.
  • One platform, deeply. A mediocre presence on 5 platforms loses to a strong presence on 1.
  • Show your work, not your product. Process > polish. Decisions > announcements. Lessons > launches.
  • The content that converts best is the content that would be useful even if your product didn't exist.
  • Consistency matters more than quality. Publish regularly at 80% quality rather than occasionally at 100%.

Platform Selection

Choose ONE based on where your ICP actually spends time:

PlatformBest ForContent StyleICP Signal
Twitter/XDevelopers, SaaS founders, tech professionalsShort-form threads, hot takes, metrics sharingYour ICP tweets about work, follows industry leaders
LinkedInB2B professionals, enterprise buyers, consultantsProfessional stories, industry insights, career contentYour ICP has detailed LinkedIn profiles, posts about industry
RedditTechnical audiences, niche communitiesHelpful answers, deep-dive posts, genuine participationActive subreddits exist for your problem space
Indie HackersSolo founders, bootstrappersRevenue updates, strategy deep-dives, lessons learnedYour buyers are themselves builders/founders
Hacker NewsDevelopers, technical decision-makersTechnical articles, Show HN launches, Ask HN questionsYour ICP reads HN, comments on technical topics
Discord/SlackCommunity-first audiences, developer toolsOngoing helpful presence, quick answersActive communities exist in your niche

How to decide: Go where your ICP already has conversations about the problem you solve. Search for your problem keywords on each platform. The one with the most active discussion is your platform.

Build-in-Public Content Framework

The 5 Content Pillars

1. Progress Updates (weekly) What you built, what moved, what the numbers say.

This week:
- Shipped [feature]. Here's why it matters: [user problem it solves].
- MRR: $X → $Y (+Z%)
- Biggest surprise: [insight]
- Next week: [what you're tackling]

2. Decision Stories (2-3x/month) The reasoning behind a product, pricing, or strategy choice.

A user asked for [feature]. I said no. Here's why:

[Explain the reasoning — what you considered, what tradeoffs exist,
what you decided and why.]

The harder question isn't "should we build it?" It's "what should
we NOT build so we can focus on what matters?"

3. Lessons & Failures (2-3x/month) What went wrong and what you learned. This is the highest-engagement content type.

I lost 12% of my users last month. Here's what happened:

[Honest explanation of what went wrong.]
[What you learned.]
[What you're changing.]

Sharing because I wish someone had told me this 6 months ago.

4. How-We-Built-It (2-4x/month) Technical or tactical deep-dives that showcase your expertise.

How I built [feature] in [timeframe]:

[Step-by-step breakdown of the approach]
[Tools/tech used]
[Result for users]

Full breakdown: [link to blog post or thread]

5. Problem Exploration (1-2x/month) Content about the problem space that's useful even without your product.

The 3 things every [ICP role] gets wrong about [problem]:

1. [Misconception] — Actually, [truth]. Here's why...
2. [Misconception] — The data says [counter-evidence]...
3. [Misconception] — I learned this the hard way when...

Content Calendar Template

Monday:    Progress update or metrics share
Tuesday:   Problem exploration or industry insight
Wednesday: How-we-built-it or tactical tip
Thursday:  Decision story or lesson learned
Friday:    Community engagement (reply to others, ask questions)

Minimum viable cadence: 3 posts per week. You can always scale up, but consistency at 3/week beats burnout at 7/week.

Platform-Specific Formats

Twitter/X

Thread format (highest engagement):

Tweet 1 (hook): [Surprising claim or specific result]
Tweet 2-6: [The substance — one idea per tweet, each stands alone]
Tweet 7 (close): [Takeaway + soft CTA]

Example hook tweets:
- "I went from 0 to $5K MRR in 90 days. Here's the exact playbook:"
- "A user asked me to build [feature]. I said no. Here's why:"
- "I tracked every hour I spent for 30 days. The results surprised me:"
- "The biggest mistake I made building [Product] (and how I fixed it):"

Single tweet format:

[Insight or observation]
[Supporting detail or data point]
[Implication or takeaway]

Keep under 240 characters for maximum reach. Or go long (up to 4,000 chars)
for nuanced takes.

LinkedIn

Post format:

[Strong opening line — pattern interrupt or bold claim]

[blank line]

[3-5 short paragraphs, each 1-2 sentences]
[Use line breaks aggressively — LinkedIn rewards readability]

[Personal anecdote or specific data point]

[Takeaway or question to drive comments]

[Optional: 3-5 relevant hashtags]

What works on LinkedIn:

  • Personal stories with professional lessons
  • Contrarian takes on industry norms
  • Specific numbers and results
  • "Here's what I learned" framing
  • Questions that invite discussion

Reddit

Post format:

Title: [Specific, descriptive, not clickbait]

Body:
- Lead with the value or question
- Be genuinely helpful first
- Share your experience, not your pitch
- Mention your product only if directly relevant AND you disclose it's yours
- Respond to every comment

Rules:

  • Never post just to promote. Reddit will destroy you.
  • Earn the right to mention your product by giving value first.
  • Each subreddit has its own culture. Lurk for a week before posting.
  • The best Reddit strategy is being the most helpful person in 2-3 relevant subreddits.

Indie Hackers

Post format:

Title: [Specific milestone, lesson, or question]

Body:
- Detailed breakdown of what happened
- Actual numbers (revenue, users, conversion rates)
- What you tried, what worked, what didn't
- Specific advice for others in similar situations

The IH community values transparency and specificity above all else.

Driving to Conversion

Every piece of content should have a path to your product, but it should never feel like an ad.

Soft CTAs (use these):

  • "I built [Product] to solve exactly this. Here's a 2-min demo: [link]"
  • "If you're dealing with this, I wrote a full breakdown at [landing page]"
  • "We're helping [X] teams with this right now. Details at [link]"

Hard CTAs (use sparingly, only on high-value posts):

  • "Try it free: [link]"
  • "We just launched [feature]. Check it out: [link]"

Link strategy:

  • Don't link to your homepage. Link to a specific page relevant to the post's topic.
  • Use case pages convert better than feature pages when linked from content.
  • "Start here" pages designed for community traffic outperform generic landing pages.

Content Repurposing

One piece of content becomes many:

Blog post (1,500 words)
  → Twitter thread (extract 7-10 key points)
  → LinkedIn post (extract personal angle)
  → Reddit comment (answer a related question, link to post)
  → Newsletter edition (add personal context)
  → Indie Hackers post (add revenue/metrics context)

Write once, distribute everywhere. But adapt the format and tone for each platform.

What NOT to Post

  • "Excited to announce..." (nobody cares about your excitement — share the value)
  • "Working on something big..." (vague teasers waste attention)
  • Retweets/reposts of industry news without your own take
  • Complaints about competitors (compete with your work, not your words)
  • AI-generated content without heavy personal editing (audiences detect this instantly)
  • Content about your product's features without connecting to user problems

Measuring Content Effectiveness

Track monthly:

| Metric                        | This Month | Last Month | Trend |
|-------------------------------|------------|------------|-------|
| Posts published               |            |            |       |
| Total impressions/views       |            |            |       |
| Engagement rate (%)           |            |            |       |
| Profile/bio link clicks       |            |            |       |
| Signups attributed to content |            |            |       |
| Followers gained              |            |            |       |
| DMs/replies about product     |            |            |       |

The only metric that truly matters: signups (or revenue) attributed to content. Everything else is a leading indicator.


Getting Started

Tell AI:

Help me plan my build-in-public content strategy:
- Product: [what it does]
- Audience: [who it's for]
- Platform I want to focus on: [Twitter/LinkedIn/Reddit/etc.]
- Current metrics: [MRR, users, or "pre-launch"]
- What I'm working on this week: [current project or feature]

Create:
1. A week's worth of posts (5 posts) using the 5 content pillars
2. Each post ready to copy-paste, formatted for [platform]
3. A mix: 1 progress update, 1 decision story, 1 lesson, 1 how-we-built-it, 1 problem exploration

Tell AI (for individual posts):

Write a [Twitter thread / LinkedIn post / Reddit post] about:
- Topic: [what happened, what you learned, what you decided]
- Key insight: [the one thing you want people to take away]
- Product mention: [include naturally / don't mention product]
- Tone: [casual and honest / professional / technical]

Make it sound like a real person sharing their experience, not a brand posting content.
Use the humanize skill patterns — no AI-sounding language.

Common Mistakes

MistakeFix
Posting on 5 platforms at oncePick ONE. Go deep. Expand after 3 months of consistency.
"Excited to announce..." openingsLead with the value, insight, or result — not your feelings
Only posting about your product80% valuable content, 20% product mentions
AI-generated posts without editingAudiences detect AI instantly. Write authentically or use humanize skill.
Giving up after 2 weeksContent compounds. Give it 3 months of 3x/week before judging.
No call-to-action anywhereEvery post should have a soft path to your product

Related Skills

  • niche-advantage — If you're an industry expert, write authority content only a practitioner can write
  • humanize — Remove AI writing patterns from generated content
  • copywriting — Write stronger headlines and hooks for posts
  • seo — Turn your best content into SEO-optimized blog posts
  • social-media — Platform-specific growth and engagement tactics
  • launch — Coordinate content with product launches

平台分布

Codex

37.13%
按下载量换算35

Claude

30.52%
按下载量换算29

Cursor

16.32%
按下载量换算16

Gemini CLI

8.22%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills