Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计通过

content-strategy内容策略

Agent Skill

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

总安装

461

周安装

19

GitHub Stars

8

下载量

150
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/vamseeachanta/workspace-hub --skill content-strategy

简介

为 B2B 技术企业提供品牌声音制定、编辑日历与多平台内容规划。

  • 聚焦工程决策者受众,强调逻辑严谨与技术深度表达。
  • 提供漏斗阶段映射、SEO 评分与跨平台分发策略建议。
  • 需输入品牌背景与目标客户画像以定制专属内容框架。
  • content-strategy 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Content Strategy Skill

Overview

This skill provides comprehensive content marketing capabilities including brand voice development, editorial calendar management, and multi-platform content creation. Designed for B2B technical companies targeting engineering decision-makers.

Quick Start

  1. Define brand voice - Analyze existing content, establish guidelines
  2. Plan content calendar - Map topics to funnel stages
  3. Create content - Use templates and frameworks
  4. Optimize for SEO - Apply SEO scoring
  5. Distribute - Repurpose across platforms

When to Use

  • Establishing brand voice guidelines
  • Planning editorial calendars
  • Creating blog posts and articles
  • Developing case studies
  • Building content pipelines
  • Repurposing content across channels

Brand Voice Framework

Voice Attributes

Define 3-5 core attributes:

AttributeDescriptionExample
AuthoritativeExpert, confident, knowledgeable"Our analysis shows..."
TechnicalPrecise, accurate, detailed"Using DNV-RP-C203 methodology..."
ApproachableClear, helpful, accessible"Let's break this down..."
InnovativeForward-thinking, modern"AI-native engineering enables..."

Voice Consistency Checklist

  • Consistent terminology across pages
  • Same level of technical depth
  • Unified tone (professional but approachable)
  • Consistent formatting patterns
  • Aligned messaging themes

Brand Voice Analysis

## Voice Analysis Template

### Content Analyzed
- [List of pages/posts analyzed]

### Current Voice Profile
- Formality: [1-10 scale]
- Technical depth: [1-10 scale]
- Personality: [descriptors]
- Tone: [descriptors]

### Recommendations
- Strengthen: [aspects to emphasize]
- Reduce: [aspects to minimize]
- Add: [missing elements]

Content Pillar Strategy

40/25/25/10 Content Mix

TypePercentagePurposeExamples
Educational40%Build authorityTutorials, guides, how-tos
Thought Leadership25%Establish expertiseIndustry insights, trends
Case Studies25%Prove capabilityProject showcases, results
Company News10%Build connectionUpdates, announcements

Content Pillars for AceEngineer

Pillar 1: AI-Native Engineering
├── Machine learning in structural analysis
├── Automation with Python
├── Digital twins and simulation

Pillar 2: Offshore Engineering Excellence
├── Fatigue analysis methodologies
├── Subsea structural design
├── Platform engineering

Pillar 3: Open Source & Transparency
├── Code repositories
├── Methodology documentation
├── Tool tutorials

Pillar 4: Industry Standards
├── DNV compliance
├── API standards
├── Best practices

Editorial Calendar

Monthly Planning Template

## Month: [Month Year]

### Theme: [Monthly Focus]

### Week 1
- Blog: [Title] - [Pillar] - [Funnel Stage]
- Social: [Distribution plan]

### Week 2
- Case Study: [Title] - [Client/Project]
- Social: [Distribution plan]

### Week 3
- Blog: [Title] - [Pillar] - [Funnel Stage]
- Calculator/Tool: [If applicable]

### Week 4
- Thought Leadership: [Title]
- Newsletter: [Monthly roundup]

### Metrics to Track
- [ ] Published on schedule
- [ ] SEO scores >75
- [ ] Social engagement
- [ ] Traffic attribution

Content Cadence Targets

Content TypeFrequencyOwner
Blog posts2-4/monthMarketing
Case studies1-2/monthTechnical + Marketing
Calculators1/quarterEngineering
Videos1/monthMarketing
Newsletter1/monthMarketing

Content Templates

Blog Post Structure

# [Title with Primary Keyword]

**Reading time:** X minutes
**Published:** [Date]
**Author:** [Name]

## Introduction (100-150 words)
- Hook with problem/question
- Why this matters
- What reader will learn

## Section 1: [H2 with Keyword]
[300-500 words]
- Key point 1
- Key point 2
- Supporting evidence

## Section 2: [H2 with Related Keyword]
[300-500 words]
[Include visual: diagram, chart, or image]

## Section 3: [H2 - Practical Application]
[300-500 words]
- Step-by-step guidance
- Code examples if relevant
- Real-world application

## Conclusion (100-150 words)
- Summary of key points
- Call to action
- Related resources

---
**Related Posts:**
- [Link 1]
- [Link 2]

**Tags:** [tag1], [tag2], [tag3]

Case Study Structure

# [Project Name]: [Result/Outcome]

## Challenge
- Client context
- Problem statement
- Constraints and requirements

## Solution
- Approach taken
- Technologies/methods used
- Key innovations

## Implementation
- Process overview
- Technical details
- Challenges overcome

## Results
- Quantified outcomes
- Client testimonial
- Business impact

## Key Takeaways
- Lessons learned
- Applicable insights
- Related services

---
**Project Details:**
- Industry: [sector]
- Duration: [timeframe]
- Technologies: [tools/methods]

Content Repurposing Matrix

Original ContentLinkedInTwitterNewsletterVideo
Blog PostKey insights (3-5 bullets)Thread (5-10 tweets)Summary + linkExplainer
Case StudyResults highlightBefore/after visualFeatured storyWalkthrough
CalculatorTutorial postTips threadHow-to guideDemo
WhitepaperChapter summariesQuote graphicsSerializedWebinar

Content Quality Checklist

Before Publishing

  • Primary keyword in title, H1, first 100 words
  • Meta description written (150-160 chars)
  • All images have alt text
  • Internal links added (2-5 per post)
  • External links to authoritative sources
  • Proofread for grammar/spelling
  • Mobile preview checked
  • SEO score >75

Technical Content Specific

  • Code examples tested and working
  • Technical accuracy verified
  • Industry standards cited correctly
  • Assumptions clearly stated
  • Limitations acknowledged

Best Practices

Do

  1. Start with keyword research
  2. Match content to funnel stage
  3. Maintain consistent publishing schedule
  4. Repurpose across channels
  5. Update old content regularly
  6. Include clear CTAs

Don't

  1. Publish without SEO optimization
  2. Ignore analytics and feedback
  3. Create content without strategy
  4. Forget mobile readers
  5. Skip the editing process
  6. Neglect content promotion

Error Handling

IssueCauseSolution
Low engagementWrong audience/topicReview keyword research, adjust
Inconsistent voiceMultiple writersCreate style guide, templates
Missed deadlinesOvercommitmentReduce cadence, batch create
Poor SEO performanceTechnical issuesAudit and fix on-page SEO

Metrics

MetricTargetFrequency
Publishing cadence100% on scheduleWeekly
SEO score>75/100Per piece
Time on page>3 minutesMonthly
Social shares>20 per postMonthly
Conversion rate>2%Monthly

Content Type Templates (Additional)

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
  • 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

Writing Best Practices by Channel

Blog

  • Write at an 8th-grade reading level for broad audiences
  • Use short paragraphs (2-4 sentences)
  • Include subheadings every 200-300 words
  • Use bullet points and numbered lists
  • Write in active voice
  • Front-load key information in each section

Social Media

  • LinkedIn: professional but human, personal stories perform well, 1,300 characters sweet spot
  • Twitter/X: concise and punchy, strong opening words, threads for longer narratives
  • Instagram: visual-first captions, storytelling hooks, hashtags in first comment
  • Facebook: conversational tone, questions drive comments

Email

  • One primary CTA per email
  • Keep body copy scannable
  • Mobile-first design
  • Test everything: subject lines, send times, CTA copy, layout

Web (Landing Pages, Product Pages)

  • Lead with benefits, not features
  • Use "you" language
  • Every section should answer "so what?"
  • Reduce friction near CTAs

Headline and Hook Formulas

Headline Formulas

  • How to [achieve result] [without common obstacle]
  • [Number] [adjective] ways to [achieve result]
  • Why [common belief] is wrong (and what to do instead)
  • The [adjective] guide to [topic]
  • [Do this], not [that]

Hook Formulas (Opening Lines)

  • Surprising statistic
  • Contrarian statement
  • Question
  • Scenario
  • Bold claim
  • Story opening

Call-to-Action Best Practices

CTA Principles

  • Use action verbs: "Get", "Start", "Download", "Join", "Try", "See"
  • Be specific about what happens next
  • Create urgency when genuine
  • Reduce risk: "No credit card required", "Cancel anytime"
  • One primary CTA per page or email

SEO Fundamentals for Content

Keyword Strategy

  • One primary keyword and 2-3 secondary keywords per piece
  • Use the primary keyword in: headline, first paragraph, one subheading, meta description, URL slug
  • 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
  • URL slug: short, descriptive, includes primary keyword
  • H1: one per page
  • Image alt text: descriptive, includes keyword where relevant
  • Internal links: 2-3 links to related content
  • External links: 1-2 links to authoritative sources

Voice Attributes

Common Voice Attribute Pairs

SpectrumOne EndOther End
FormalityFormal, institutionalCasual, conversational
AuthorityExpert, authoritativePeer-level, collaborative
EmotionWarm, empatheticDirect, matter-of-fact
ComplexityTechnical, preciseSimple, accessible
EnergyBold, energeticCalm, measured
HumorPlayful, wittySerious, earnest
InnovationCutting-edge, forward-lookingEstablished, proven

Defining an Attribute

[Attribute name]

  • We are: [what this means in practice]
  • We are not: [common misinterpretation to avoid]
  • This sounds like: [example sentence demonstrating the attribute]
  • This does NOT sound like: [example sentence violating the attribute]

Tone Adaptation Across Channels and Contexts

The brand voice stays consistent, but tone adapts to context.

Tone by Channel

ChannelTone Adaptation
BlogInformative, conversational, educational
Social media (LinkedIn)Professional, thought-provoking, concise
Social media (Twitter/X)Punchy, direct, sometimes witty
Email marketingPersonal, helpful, action-oriented
Sales collateralConfident, benefit-driven, specific
Support/Help docsClear, patient, step-by-step
Press releaseFormal, factual, newsworthy
Error messagesEmpathetic, helpful, blame-free

Tone by Situation

SituationTone Adaptation
Product launchExcited, confident, forward-looking
Incident or outageTransparent, empathetic, accountable
Customer success storyCelebratory, specific, crediting the customer
Thought leadershipAuthoritative, nuanced, evidence-based
Bad newsHonest, respectful, solution-oriented

Tone Adaptation Rule

The voice attributes remain fixed. Tone dials them up or down based on context.

Terminology Management

Preferred Terms

Use ThisNot ThisNotes
sign up (verb)signup (verb)"signup" is the noun form
log in (verb)login (verb)"login" is the noun/adjective form
set up (verb)setup (verb)"setup" is the noun/adjective form
emaile-mailNo hyphen
websiteweb siteOne word

Inclusive Language

  • Use gender-neutral language
  • Avoid ableist language
  • Use person-first language where appropriate
  • Avoid culturally specific idioms that may not translate
  • Use "simple" or "straightforward" instead of "easy"

Industry Jargon Management

  • Define which technical terms the audience understands without explanation
  • List jargon that should always be defined or replaced
  • Specify which acronyms need to be spelled out on first use

Related Skills

Sources


Version History

  • 1.1.0 (2026-02-03): Merged content type templates, writing best practices, headline formulas, CTA best practices, SEO fundamentals, voice attributes, tone adaptation, and terminology management from anthropics/knowledge-work-plugins
  • 1.0.0 (2026-01-19): Initial release adapted from alirezarezvani/claude-skills

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

Claude Code

31.1%
按下载量换算47

windsurf

25.59%
按下载量换算38

trae

19.92%
按下载量换算30

OpenCode

11.19%
按下载量换算17

Cursor

7.39%
按下载量换算11

Codex

3.14%
按下载量换算5

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills