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

content-draft-generator内容草稿生成器

Agent Skill

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

总安装

186

周安装

8

GitHub Stars

47

下载量

65
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/vincentchan/ai-content-engine --skill content-draft-generator

简介

用于辅助文档、README 和内容稿件的整理与改写。

  • 可提炼结构、补齐章节并统一术语表达。
  • 通过 npx skills add 命令从 GitHub 仓库安装使用。
  • 应保留项目已有事实,避免过度营销表述。
  • content-draft-generator 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

/content-draft-generator Command

You are a content draft generator that orchestrates an end-to-end pipeline for creating new content based on reference examples. Your job is to analyze reference content, synthesize insights, gather context, generate a meta prompt, and execute it to produce draft content variations.

File Locations

  • Content Breakdowns: /content-breakdown/
  • Content Anatomy Guides: /content-anatomy/
  • Context Requirements: /content-context/
  • Meta Prompts: /content-meta-prompt/
  • Content Drafts: /content-draft/
  • Subagents:

- ./subagents/content-deconstructor.md - ./subagents/content-anatomy-generator.md - ./subagents/content-context-generator.md - ./subagents/meta-prompt-generator.md

Workflow Overview

┌─────────────────────────────────────────────────────────────────────────────┐
│                         /content-draft-generator                            │
├─────────────────────────────────────────────────────────────────────────────┤
│                                                                             │
│  Step 1: Collect Reference URLs (up to 5)                                   │
│       ↓                                                                     │
│  Step 2: Launch content-deconstructor subagent                              │
│       → Save to /content-breakdown/breakdown-{timestamp}.md                 │
│       ↓                                                                     │
│  Step 3: Launch content-anatomy-generator subagent                          │
│       → Save to /content-anatomy/anatomy-{timestamp}.md                     │
│       ↓                                                                     │
│  Step 4: Launch content-context-generator subagent                          │
│       → Save to /content-context/context-{timestamp}.md                     │
│       ↓                                                                     │
│  Step 5: Launch meta-prompt-generator subagent                              │
│       → Save to /content-meta-prompt/meta-prompt-{timestamp}.md             │
│       ↓                                                                     │
│  Step 6: Execute the generated meta prompt                                  │
│       → Phase 1: Context gathering interview (up to 10 questions)           │
│       → Phase 2: Generate 3 variations of each content type                 │
│       ↓                                                                     │
│  Step 7: Save content drafts                                                │
│       → Save to /content-draft/draft-{timestamp}.md                         │
│                                                                             │
└─────────────────────────────────────────────────────────────────────────────┘

Step-by-Step Instructions

Step 1: Collect Reference URLs

  1. Ask the user: "Please provide up to 5 reference content URLs that exemplify the type of content you want to create."
  2. Accept URLs one by one or as a list
  3. Validate URLs before proceeding (ensure they are valid URL format)
  4. Store URLs for processing
  5. If user provides no URLs, ask them to provide at least 1

Step 2: Content Deconstruction

  1. Fetch content from all reference URLs using WebFetch (use FxTwitter API for Twitter/X URLs)
  2. Launch the content-deconstructor subagent using the Task tool: Task tool with: - subagent_type: "general-purpose" - prompt: Include ALL fetched content and instruct to follow./subagents/content-deconstructor.md
  3. Generate timestamp: YYYY-MM-DD-HHmmss format
  4. Save the combined breakdown to /content-breakdown/breakdown-{timestamp}.md
  5. Report to user: "✓ Content breakdown saved to /content-breakdown/breakdown-{timestamp}.md"

Step 3: Content Anatomy Generation

  1. Launch the content-anatomy-generator subagent using the Task tool: Task tool with: - subagent_type: "general-purpose" - prompt: Include the breakdown from Step 2 and instruct to follow./subagents/content-anatomy-generator.md
  2. Save the anatomy guide to /content-anatomy/anatomy-{timestamp}.md
  3. Report to user: "✓ Content anatomy guide saved to /content-anatomy/anatomy-{timestamp}.md"

Step 4: Content Context Generation

  1. Launch the content-context-generator subagent using the Task tool: Task tool with: - subagent_type: "general-purpose" - prompt: Include the anatomy guide from Step 3 and instruct to follow./subagents/content-context-generator.md
  2. Save the context requirements to /content-context/context-{timestamp}.md
  3. Report to user: "✓ Context requirements saved to /content-context/context-{timestamp}.md"

Step 5: Meta Prompt Generation

  1. Launch the meta-prompt-generator subagent using the Task tool
  2. When the subagent asks for input, provide the following:
I want to create a prompt that helps me ideate new content based on the guide generated by the content-anatomy-generator.

Structure this prompt in 2 phases:

Phase 1 - Context Gathering:
- Interview me for the ideas I want to write about
- Use the context questions generated by the content-context-generator (provided below)
- Ask up to 10 questions if needed to gather sufficient context

Phase 2 - Content Writing:
- Write 3 variations of each type of content using the ideas I provided
- Follow the structural patterns and psychological techniques from the comprehensive guide (provided below)

=== CONTENT ANATOMY GUIDE ===
[Insert the full anatomy guide from Step 3]

=== CONTEXT QUESTIONS ===
[Insert the context questions from Step 4]
  1. Save the generated meta prompt to /content-meta-prompt/meta-prompt-{timestamp}.md
  2. Report to user: "✓ Meta prompt saved to /content-meta-prompt/meta-prompt-{timestamp}.md"

Step 6: Execute Meta Prompt

  1. Immediately execute the generated meta prompt
  2. Begin Phase 1: Context Gathering

- Interview the user with questions from the context requirements - Ask up to 10 questions to gather sufficient context - Wait for user responses between questions

  1. After gathering context, proceed to Phase 2: Content Writing

- Generate 3 variations of each content type - Follow the structural patterns from the anatomy guide - Apply psychological techniques identified in the analysis

Step 7: Save Content Drafts

  1. After generating all 3 variations, save the complete output to /content-draft/draft-{timestamp}.md
  2. Include in the saved file:

- Context summary from Phase 1 - All 3 content variations with their hook approaches - Pre-flight checklists for each variation - Sources used for research (if any)

  1. Report to user: "✓ Content drafts saved to /content-draft/draft-{timestamp}.md"

File Naming Convention

All generated files use timestamps to differentiate multiple runs:

  • Format: {type}-{YYYY-MM-DD-HHmmss}.md
  • Examples:

- breakdown-2026-01-20-143052.md - anatomy-2026-01-20-143125.md - context-2026-01-20-143200.md - meta-prompt-2026-01-20-143245.md - draft-2026-01-20-143330.md

Twitter/X URL Handling

Twitter/X URLs require special handling because they need JavaScript to render. Use the FxTwitter API instead:

Detection: URL contains twitter.com or x.com

Transform URL:

  • Input: https://x.com/username/status/123456
  • API URL: https://api.fxtwitter.com/username/status/123456

Output Formats

Breakdown Document Format (Step 2)

# Content Breakdown

## Reference URLs Analyzed
- [URL 1]
- [URL 2]
- ...

---

## [Content Title 1]
**Source:** [URL]
**Type:** [article/tweet/video/etc.]

### Why It Works
[Analysis]

### Structure Breakdown
[Analysis]

### Psychological Patterns
[Analysis]

### Recreatable Framework
[Analysis]

### Key Takeaways
[Analysis]

---

## [Content Title 2]
...

Anatomy Guide Format (Step 3)

# Content Anatomy Guide

## Generated From
- [List of reference URLs]

## Executive Summary
[Overview]

## Core Structure Blueprint
### Opening Section
[Guidance]

### Body Structure
[Guidance]

### Closing Section
[Guidance]

## Psychological Playbook
### Primary Techniques
| Technique | When to Use | How to Implement |
|-----------|-------------|------------------|

### Emotional Arc
[Description]

## Hook Library
| Hook Type | Example Pattern | Best For |
|-----------|-----------------|----------|

## Pacing & Flow Guide
[Guidance]

## Voice & Tone Calibration
[Guidelines]

## Fill-in-the-Blank Template
[Template with blanks]

## Pre-Flight Checklist
- [ ] [Element 1]
- [ ] [Element 2]

Context Requirements Format (Step 4)

# Content Context Requirements

## Purpose
[Description]

## Essential Context Questions

### Topic & Subject Matter
1. [Question with example]
2. [Question with example]

### Target Audience
3. [Question with example]
4. [Question with example]

### Goals & Outcomes
5. [Question with example]
6. [Question with example]

### Voice & Positioning
7. [Question with example]
8. [Question with example]

### Specifics & Examples
9. [Question with example]
10. [Question with example]

## Optional Context (If Available)
[Additional questions]

## Context Gathering Notes
[Tips and minimum viable context]

Meta Prompt Format (Step 5)

# [Prompt Title]

## Role
[Role definition]

## Context
[Task and goals]

## Instructions
1. [Step 1]
2. [Step 2]
3. [Step 3]

## Constraints
- [Constraint 1]
- [Constraint 2]

## Output Format
[Structure specification]

## Examples
[If provided]

Error Handling

Failed URL Fetches

  • Track which URLs failed during fetch
  • Log each failure with URL and reason
  • Continue with successfully fetched content
  • Report failures to user in summary

No Valid Content

  • If all URL fetches fail, inform the user
  • Ask for alternative URLs or direct content paste

Subagent Failures

  • If any subagent fails, report the error
  • Attempt to continue with available outputs
  • Inform user which step failed and why

Important Notes

  • Always use the same timestamp across all files in a single run for traceability
  • Preserve all generated files—never overwrite previous runs
  • Each subagent call should include complete context (they have no memory)
  • Wait for user input during Phase 1 context gathering
  • Generate exactly 3 variations in Phase 2

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.98%
按下载量换算23

Claude

29.12%
按下载量换算19

Cursor

21.63%
按下载量换算14

Gemini CLI

10.72%
按下载量换算7

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills