图像写作
- 作者仓库星标 19,014
- 作者更新于 实时读取
- 作者仓库 knowledge-work-plugins
- 领域
- 写作
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @anthropics · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: content-creation
description: Draft marketing content across channels — blog posts, social media, email newsletters, landing p…
category: 写作
runtime: 无特殊运行时
---
# content-creation 输出预览
## PART A: 任务判断
- 适用问题:文章、文案、发言稿、润色或结构化表达。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Content Type Templates / Blog Post Structure / Social Media Post Structure”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于文章、文案、发言稿、润色或结构化表达,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Content Type Templates / Blog Post Structure / Social Media Post Structure”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 先确认触发方式
原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
给清楚输入和边界
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
小样例验证后再放大
先用一个小任务确认它会围绕“Content Type Templates / Blog Post Structure / Social Media Post Structure”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
复核后再交付
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: content-creation
description: Draft marketing content across channels — blog posts, social media, email newsletters, landing p…
category: 写作
source: anthropics/knowledge-work-plugins
---
# content-creation
## 什么时候使用
- 把写作方向的常用动作沉淀成 Agent 可调用的技能 适合处理文章、文案、润色、翻译、总结和结构化表达,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常…
- 面向文章、文案、发言稿、润色或结构化表达,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Content Type Templates / Blog Post Structure / Social Media Post Structure」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 证据边界与执行链路
作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "content-creation" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Content Type Templates / Blog Post Structure / Social Media Post Structure
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Content Creation Skill
Guidelines and frameworks for creating effective marketing content across channels.
Content Type Templates
Blog Post Structure
- Headline — clear, benefit-driven, includes primary keyword (aim for 60 characters or less for SEO)
- Introduction (100-150 words) — hook the reader with a question, statistic, bold claim, or relatable scenario. State what the post will cover. Include primary keyword.
- Body sections (3-5 sections) — each with a descriptive subheading (H2). Use H3 for subsections. One core idea per section with supporting evidence, examples, or data.
- Conclusion (75-100 words) — summarize key takeaways, reinforce the main message, include a call to action.
- Meta description — under 160 characters, includes primary keyword, compels the click.
Social Media Post Structure
- Hook — first line grabs attention (question, bold statement, number)
- Body — 2-4 concise points or a short narrative
- CTA — what should the reader do next (comment, click, share, tag)
- Hashtags — 3-5 relevant hashtags (platform-dependent)
Email Newsletter Structure
- Subject line — under 50 characters, creates curiosity or states clear value
- Preview text — complements the subject line, does not repeat it
- Header/hero — visual anchor and one-line value statement
- Body sections — 2-3 content blocks, each scannable with a bold intro sentence
- Primary CTA — one clear action per email
- Footer — unsubscribe link, company info, social links
Landing Page Structure
- Headline — primary benefit in under 10 words
- Subheadline — elaborates on the headline with supporting context
- Hero section — headline, subheadline, primary CTA, supporting image or video
- Value propositions — 3-4 benefit-driven sections with icons or images
- Social proof — testimonials, logos, stats, case study snippets
- Objection handling — FAQ or trust signals
- Final CTA — repeat the primary call to action
Press Release Structure
- Headline — factual, newsworthy, under 80 characters
- Subheadline — optional, adds context
- Dateline — city, state, date
- Lead paragraph — who, what, when, where, why in 2-3 sentences
- Body paragraphs — supporting details, quotes, context
- Boilerplate — company description (standardized)
- Media contact — name, email, phone
Case Study Structure
- Title — "[Customer] achieves [result] with [product]"
- Snapshot — customer name, industry, company size, product used, key result (sidebar or callout box)
- Challenge — what problem the customer faced
- Solution — what was implemented and how
- Results — quantified outcomes with specific metrics
- Quote — customer testimonial
- CTA — learn more, get a demo, read more case studies
Writing Best Practices by Channel
Blog
- Write at an 8th-grade reading level for broad audiences; adjust up for technical audiences
- Use short paragraphs (2-4 sentences)
- Include subheadings every 200-300 words
- Use bullet points and numbered lists to break up text
- Include at least one data point, example, or quote per section
- Write in active voice
- Front-load key information in each section
Social Media
- LinkedIn: professional but human, paragraph breaks for readability, personal stories and lessons perform well, 1,300 characters is the sweet spot before "see more"
- Twitter/X: concise and punchy, strong opening words, threads for longer narratives, engage with replies
- Instagram: visual-first captions, storytelling hooks, line breaks for readability, hashtags in first comment or at end
- Facebook: conversational tone, questions drive comments, shorter posts (under 80 characters) get more engagement for links
- Write subject lines that create urgency, curiosity, or state clear value
- Personalize where possible (name, company, behavior)
- One primary CTA per email — make it visually distinct
- Keep body copy scannable: bold key phrases, short paragraphs, bullet points
- Test everything: subject lines, send times, CTA copy, layout
- Mobile-first: most email is read on mobile
Web (Landing Pages, Product Pages)
- Lead with benefits, not features
- Use "you" language — speak to the reader directly
- Minimize jargon unless the audience expects it
- Every section should answer "so what?" from the reader's perspective
- Reduce friction: fewer form fields, clear next steps, trust signals near CTAs
SEO Fundamentals for Content
Keyword Strategy
- Identify one primary keyword and 2-3 secondary keywords per piece
- Use the primary keyword in: headline, first paragraph, one subheading, meta description, URL slug
- Use secondary keywords naturally in body copy and subheadings
- Do not keyword-stuff — write for humans first
On-Page SEO Checklist
- Title tag: under 60 characters, includes primary keyword
- Meta description: under 160 characters, includes primary keyword, compels click
- URL slug: short, descriptive, includes primary keyword
- H1: one per page, matches or closely reflects the title tag
- H2/H3: descriptive, include secondary keywords where natural
- Image alt text: descriptive, includes keyword where relevant
- Internal links: 2-3 links to related content on your site
- External links: 1-2 links to authoritative sources
Content-SEO Integration
- Aim for comprehensive coverage of the topic (search engines reward depth)
- Answer related questions (check "People Also Ask" for ideas)
- Update and refresh high-performing content regularly
- Structure content for featured snippets: definition paragraphs, numbered lists, tables
Headline and Hook Formulas
Headline Formulas
- How to [achieve result] [without common obstacle] — "How to Double Your Email Open Rates Without Sending More Emails"
- [Number] [adjective] ways to [achieve result] — "7 Proven Ways to Reduce Customer Churn"
- Why [common belief] is wrong (and what to do instead) — "Why More Content Is Not the Answer (And What to Do Instead)"
- The [adjective] guide to [topic] — "The Complete Guide to B2B Content Marketing"
- [Do this], not [that] — "Build a Community, Not Just an Audience"
- What [impressive result] taught us about [topic] — "What 10,000 A/B Tests Taught Us About Email Subject Lines"
- [topic]: what [audience] needs to know in [year] — "SEO: What Marketers Need to Know in 2025"
Hook Formulas (Opening Lines)
- Surprising statistic: "73% of marketers say their biggest challenge is not budget — it is focus."
- Contrarian statement: "The best marketing campaigns start with saying no to most channels."
- Question: "When was the last time a marketing email actually changed what you bought?"
- Scenario: "Imagine launching a campaign and knowing, before it goes live, which messages will land."
- Bold claim: "Most landing pages lose half their visitors in the first three seconds."
- Story opening: "Last quarter, our team was spending 20 hours a week on reporting. Here is what we did about it."
Call-to-Action Best Practices
CTA Principles
- Use action verbs: "Get", "Start", "Download", "Join", "Try", "See"
- Be specific about what happens next: "Start your free trial" is better than "Submit"
- Create urgency when genuine: "Join 500 teams already using this" or "Limited spots available"
- Reduce risk: "No credit card required", "Cancel anytime", "Free for 14 days"
- One primary CTA per page or email — too many choices reduce conversions
CTA Examples by Context
- Blog post: "Read our complete guide to [topic]" / "Subscribe for weekly insights"
- Landing page: "Start free trial" / "Get a demo" / "See pricing"
- Email: "Read the full story" / "Claim your spot" / "Reply and tell us"
- Social media: "Drop a comment if you agree" / "Save this for later" / "Link in bio"
- Case study: "See how [product] can work for your team" / "Talk to our team"
CTA Placement
- Above the fold on landing pages (do not make users scroll to act)
- After establishing value in emails (not in the first sentence)
- At the end of blog posts (after you have earned the reader's trust)
- In-line within content when contextually relevant (e.g., a related guide mention)
- Repeat the primary CTA at the bottom of long-form pages
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核