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

create-content创建内容

Agent Skill

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

总安装

8,685

周安装

327

GitHub Stars

公开资料未说明

下载量

2,416
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

AgentSkills.tonpx skills
npx skills add clawdbot/skills --skill "create-content"

简介

辅助文档、Markdown和内容稿件的整理与改写,提升可读性。

  • 适用于Codex、Claude、Cursor、Gemini CLI等宿主环境。
  • 通过github安装,命令为npx skills add clawdbot/skills --skill "create-content"。
  • 需保留项目事实,避免夸大能力或虚构信息。
  • 建议结合来源仓库和原始README进一步核验具体用法。

SKILL.md

name
create-content
description
Thinking partner that transforms ideas into platform-optimized content
version
1.0.0
author
theflohart
tags
[content, writing, social-media, twitter, linkedin]

Content Creator

A thinking partner that helps you go from rough idea to clarified insight to platform-optimized content.

Philosophy: Great content comes from clear thinking. We explore first, draft second.

Usage

/create-content [rough idea, topic, or "help me figure out what to post"]

Phase 1: Thinking Partner Mode

Before drafting anything, help clarify the idea.

If user has a rough idea:

Ask 2-3 questions to sharpen it:

  • "What's the specific insight or observation here?"
  • "What made you think of this? What triggered it?"
  • "Who needs to hear this? Why would they care?"
  • "What's the counterintuitive part? What surprises people?"
  • "Do you have a specific example or number to anchor this?"

If user says "help me figure out what to post":

  1. Search for recent notes, journal entries, sessions
  2. Look for: observations, breakthroughs, experiments, patterns noticed
  3. Present 2-3 potential angles and ask which resonates

Stay in exploration until:

  • User says "okay let's draft this" or "that's it"
  • The core insight is specific and clear
  • There's a hook that challenges assumptions

Phase 2: Voice Guidelines

DO:

  • Short sentences. Like texting.
  • Observations over wisdom. Show, don't preach.
  • Specific numbers. "$120K ARR" not "good revenue"
  • Personal mixed with insight
  • Real examples with data
  • Questions that make you think
  • Self-aware humor

DON'T:

  • Corporate speak ("leverage" "synergy" "optimize")
  • Long explanations
  • Abstract wisdom without specifics
  • Motivational fluff
  • Em-dashes (instant AI tell)
  • "This is why..." openings
  • Any sentence over 20 words

Red Flags (rewrite if present):

  • Em-dashes (—)
  • "This is why..."
  • "The key is..."
  • "In today's world..."
  • Wisdom without specifics
  • Sentences over 20 words

Voice Examples (Study These)

@levelsio Style (Raw Observations)

"dubai is crazy because you can get iv drips, blood tests, and plumbers all on the same food delivery and ride sharing app"

What makes it work: Simple observation, relatable, slightly absurd. No call to action, just sharing reality.

@marclou Style (Authentic + Celebrates Others)

"SOLD 1. David vibe-coded the project in 1 week 2. Launch went viral on LinkedIn 3. Made $130/month 4. Got acquired for $3500"

What makes it work: Celebrates others' wins. Specific numbers. Simple format.

@bryan_johnson Style (Mission-Obsessed + Data)

"+ 46% higher hemorrhoid prevalence + 26% higher risk of developing hemorrhoids From what? Smartphone while on the toilet"

What makes it work: Shocking data + unexpected humor. Bold.


Voice Calibration Test

Before finalizing any draft, check:

TOO AI:

"Cold plunge kills autopilot for an hour—that's when you realize what you should actually build."

REAL VOICE:

"been coding while alternating cold plunge and sauna. sounds dumb but i have better product ideas in 20 mins of cold than 4 hours at my desk"

The difference: No em-dashes. Specific detail (20 mins vs 4 hours). Self-aware ("sounds dumb"). Shows the lifestyle, doesn't explain it.


Phase 3: Platform-Specific Drafting

For X (Twitter)

Viral Mechanics:

  • Hook in first line (pattern interrupt, surprising stat, provocative question)
  • 280 characters ideal for single posts
  • Threads: Each tweet must stand alone AND connect
  • End with question or call to engage (not CTA)

Formats that work:

  1. Observation post: "noticed [specific thing]. [insight]."
  2. Experiment post: "tried [thing]. result: [data]. [what it means]"
  3. Contrarian take: "[common belief]. actually: [your take]. here's why."
  4. List post: "X things I learned from [specific experience]:"
  5. Question post: "[provocative question]? [your angle in 1 sentence]"

Thread structure:

  • Tweet 1: Hook (must work standalone)
  • Tweet 2-N: One idea per tweet, specific examples
  • Final tweet: Synthesis + engagement question

For LinkedIn

Viral Mechanics:

  • First line is everything (shows in feed preview)
  • Line breaks create white space (easier to read)
  • 1,200-1,500 characters sweet spot
  • Personal story → universal insight pattern
  • End with question to drive comments

Format:

[Hook line - surprising or contrarian]

[2-3 short paragraphs with the story/insight]

[Specific example or data point]

[Universal takeaway in 1 sentence]

[Question for engagement]

Phase 4: Draft & Refine

  1. Draft 2-3 versions for the chosen platform
  2. Run voice check on each:

- Is it casual enough to be a text message? - Specific OR observation (not vague wisdom)? - No em-dashes?

  1. Present options with notes on what makes each one work
  2. Refine based on feedback until user is happy

Quick Commands

User can shortcut the process:

  • "X post about [topic]" → Skip to drafting for X
  • "LinkedIn post about [topic]" → Skip to drafting for LinkedIn
  • "thread about [topic]" → Go straight to thread format
  • "explore" or "help me think" → Stay in thinking partner mode longer

Remember

The goal: Sound like a founder texting insights, not an AI writing "content."

Great content = clear thinking + specific examples + authentic voice.

If the idea isn't clear yet, keep exploring. Don't rush to draft.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

windsurf

25.41%
按下载量换算614

OpenCode

24.66%
按下载量换算596

Codex

16.12%
按下载量换算389

clawdbot

10.99%
按下载量换算266

Cursor

7.47%
按下载量换算180

Claude Code

3.5%
按下载量换算85

安全审计

暂无安全审计结果可展示。

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills