anthropics/knowledge-work-plugins

draft-content

Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill draft-content

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Draft Content

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Generate marketing content drafts tailored to a specific content type, audience, and brand voice.

Trigger

User runs /draft-content or asks to draft, write, or create marketing content.

Inputs

Gather the following from the user. If not provided, ask before proceeding:

  1. Content type — one of:
  • Blog post
  • Social media post (specify platform: LinkedIn, Twitter/X, Instagram, Facebook)
  • Email newsletter
  • Landing page copy
  • Press release
  • Case study
  1. Topic — the subject or theme of the content
  1. Target audience — who this content is for (role, industry, seniority, pain points)
  1. Key messages — 2-4 main points or takeaways to communicate
  1. Tone — e.g., authoritative, conversational, inspirational, technical, witty (optional if brand voice is configured)
  1. Length — target word count or format constraint (e.g., "1000 words", "280 characters", "3 paragraphs")

Brand Voice

  • If the user has a brand voice configured in their local settings file, apply it automatically. Inform the user that brand voice settings are being applied.
  • If no brand voice is configured, ask: "Do you have brand voice guidelines you'd like me to follow? If not, I'll use a neutral professional tone."
  • Apply the specified or default tone consistently throughout the draft.

Content Generation by Type

Blog Post

  • Engaging headline (provide 2-3 options)
  • Introduction with a hook (question, statistic, bold statement, or story)
  • 3-5 organized sections with descriptive subheadings
  • Supporting points, examples, or data references in each section
  • Conclusion with a clear call to action
  • SEO considerations: suggest a primary keyword, include it in the headline and first paragraph, use related keywords in subheadings

Social Media Post

  • Platform-appropriate format and length
  • Hook in the first line
  • Hashtag suggestions (3-5 relevant hashtags)
  • Call to action or engagement prompt
  • Emoji usage appropriate to brand and platform
  • If LinkedIn: professional framing, paragraph breaks for readability
  • If Twitter/X: concise, punchy, within character limit
  • If Instagram: visual-first language, story-driven, hashtag block

Email Newsletter

  • Subject line (provide 2-3 options with open-rate considerations)
  • Preview text
  • Greeting
  • Body sections with clear hierarchy
  • Call to action button text
  • Sign-off
  • Unsubscribe note reminder

Landing Page Copy

  • Headline and subheadline
  • Hero section copy
  • Value propositions (3-4 benefit-driven bullets or sections)
  • Social proof placeholder (suggest testimonial or stat placement)
  • Primary and secondary CTAs
  • FAQ section suggestions
  • SEO: meta title and meta description suggestions

Press Release

  • Headline following press release conventions
  • Dateline and location
  • Lead paragraph (who, what, when, where, why)
  • Supporting quotes (provide placeholder guidance)
  • Company boilerplate placeholder
  • Media contact placeholder
  • Standard press release formatting

Case Study

  • Title emphasizing the result
  • Customer overview (industry, size, challenge)
  • Challenge section
  • Solution section (what was implemented)
  • Results section with metrics (prompt user for data)
  • Customer quote placeholder
  • Call to action

SEO Considerations (for web content)

For blog posts, landing pages, and other web-facing content:

  • Suggest a primary keyword based on the topic
  • Recommend keyword placement: headline, first paragraph, subheadings, meta description
  • Suggest internal and external linking opportunities
  • Recommend a meta description (under 160 characters)
  • Note image alt text opportunities

Output

Present the draft with clear formatting. After the draft, include:

  • A brief note on what brand voice and tone were applied
  • Any SEO recommendations (for web content)
  • Suggestions for next steps (e.g., "Review with your team", "Add customer quotes", "Pair with a visual")

Ask: "Would you like me to revise any section, adjust the tone, or create a variation for a different channel?"

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
anthropics
公式

process-doc

Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.

1時間の導入数
1
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

data-visualization

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

1時間の導入数
5
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

accessibility-review

Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.

1時間の導入数
4
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

sql-queries

Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.). Use when writing queries, optimizing slow SQL, translating between dialects, or building complex analytical queries with CTEs, window functions, or aggregations.

1時間の導入数
4
GitHub Stars
3.7万
更新日
11月20日