feat: update content creator and marketing pro workflows with new skills, enhanced README files, and improved SEO content strategies

This commit is contained in:
jinmingyang
2026-01-17 06:00:32 +08:00
parent 3fa593349f
commit dc2b44f70f
17 changed files with 1308 additions and 31 deletions
+4 -2
View File
@@ -8,8 +8,8 @@ Ready-to-use Claude Code workflow collections with multi-AI tool support.
| Workflow | Target Users | Skills |
|----------|-------------|--------|
| [content-creator-workflow](./content-creator-workflow/) | Bloggers, Content Creators | 7 |
| [marketing-pro-workflow](./marketing-pro-workflow/) | Digital Marketers, Social Media Managers | 5 |
| [content-creator-workflow](./content-creator-workflow/) | Bloggers, Content Creators | 9 |
| [marketing-pro-workflow](./marketing-pro-workflow/) | Digital Marketers, Social Media Managers | 10 |
## Quick Start
@@ -59,6 +59,8 @@ ai-workflow/
- [gked2121/claude-skills](https://github.com/gked2121/claude-skills)
- [ComposioHQ/awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills)
- [kkoppenhaver/cc-nano-banana](https://github.com/kkoppenhaver/cc-nano-banana)
- [MadAppGang/claude-code](https://github.com/MadAppGang/claude-code) - SEO/content skills
- [nicknisi/dotfiles](https://github.com/nicknisi/dotfiles) - Blog writing skills
- [skillhub.club](https://www.skillhub.club) - 1000+ skills collection
## License
+4 -2
View File
@@ -6,8 +6,8 @@
| Workflow | 适合人群 | Skills数量 |
|----------|---------|-----------|
| [content-creator-workflow](./content-creator-workflow/) | 自媒体博主、内容创作者 | 7 |
| [marketing-pro-workflow](./marketing-pro-workflow/) | 数字营销、社交媒体经理 | 5 |
| [content-creator-workflow](./content-creator-workflow/) | 自媒体博主、内容创作者 | 9 |
| [marketing-pro-workflow](./marketing-pro-workflow/) | 数字营销、社交媒体经理 | 10 |
## 快速使用
@@ -57,6 +57,8 @@ ai-workflow/
- [gked2121/claude-skills](https://github.com/gked2121/claude-skills)
- [ComposioHQ/awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills)
- [kkoppenhaver/cc-nano-banana](https://github.com/kkoppenhaver/cc-nano-banana)
- [MadAppGang/claude-code](https://github.com/MadAppGang/claude-code) - SEO/内容skills
- [nicknisi/dotfiles](https://github.com/nicknisi/dotfiles) - 博客写作skills
- [skillhub.club](https://www.skillhub.club) - 1000+ skills集合
## License
@@ -0,0 +1,194 @@
---
name: blog-post-writer
description: Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.
---
# Nick Nisi Blog Writer
Transform unstructured brain dumps into polished blog posts that sound like Nick Nisi.
## Process
### 1. Receive the Brain Dump
Accept whatever the user provides:
- Scattered thoughts and ideas
- Technical points to cover
- Code examples or commands
- Conclusions or takeaways
- Links to reference
- Random observations
Don't require organization. The mess is the input.
### 2. Read Voice and Tone
Load `references/voice-tone.md` to understand Nick's writing style.
Key characteristics:
- Conversational yet substantive
- Vulnerable and authentic
- Journey-based narrative
- Mix of short and long sentences
- Specific examples and real details
- Self-aware humor
### 3. Check for Story Potential
Read `references/story-circle.md` to understand the narrative framework.
Determine if the content fits a story structure:
- Is there a journey from one understanding to another?
- Can you identify a problem and resolution?
- Does it follow: comfort → disruption → return changed?
Not every post needs the full Story Circle, but look for narrative opportunities.
### 4. Organize Content
Structure the material into sections:
**Common structures:**
- Problem/experience → Journey → Results → Lessons
- Setup → Challenge → Discovery → Application
- Philosophy → How-to → Reflection
- Current state → Past → Learning → Future
Choose the structure that fits the content.
### 5. Write in Nick's Voice
Apply voice characteristics:
**Opening:**
- Hook with current position or recent event
- Set up tension or question
- Be direct and honest
**Body:**
- Vary paragraph length
- Use short paragraphs for emphasis
- Include specific details (tool names, commands, numbers)
- Show vulnerability where appropriate
- Use inline code formatting naturally
- Break up text with headers
**Technical content:**
- Assume reader knowledge but explain when needed
- Show actual commands and examples
- Be honest about limitations
- Use casual tool references
**Tone modulation:**
- Technical sections: clear, instructional
- Personal sections: vulnerable, reflective
- Be conversational throughout
**Ending:**
- Tie back to opening
- Forward-looking perspective
- Actionable advice
- Optimistic or thought-provoking
### 6. Review and Refine
Check the post:
- Does it sound conversational?
- Is there a clear narrative arc?
- Are technical details specific and accurate?
- Does it show vulnerability appropriately?
- Are paragraphs varied in length?
- Is humor self-aware, not forced?
- Does it end with momentum?
Show the post to the user for feedback and iterate.
## Voice Guidelines
### Do:
- Write like talking to a peer over coffee
- Admit uncertainty or being wrong
- Use specific examples with details
- Vary sentence and paragraph length
- Include inline code naturally
- Show the journey, not just the destination
- Use humor sparingly and self-aware
- End with forward momentum
### Don't:
- Use corporate or marketing speak
- Pretend to have all answers
- Be preachy or condescending
- Over-explain basic concepts
- Force humor or emojis
- Hide mistakes or uncertainty
- Write without specific examples
## Example Patterns
### Opening hooks:
```markdown
"AI is going to replace developers."
I must have heard that phrase a hundred times in the last year.
```
```markdown
I've been thinking a lot about how we use AI in our daily work.
```
### Emphasis through structure:
```markdown
Then something clicked.
I watched it use rg to search through codebases, just like I would.
```
### Vulnerability:
```markdown
I won't lie – joining Meta was intimidating.
```
### Technical details:
```markdown
I watched it use `rg` to search through codebases, just like I would.
It ran `npm test` to verify its changes weren't breaking anything.
```
### Conclusions:
```markdown
You're not being replaced; you're being amplified.
```
## Bundled Resources
### References
- `references/voice-tone.md` - Complete voice and tone guide. Read this first to capture Nick's style.
- `references/story-circle.md` - Story Circle narrative framework. Check if content fits a story structure.
## Workflow Example
User provides brain dump:
```
thoughts on using cursor vs claude code
- cursor is in IDE, feels familiar
- but claude code is in terminal, my natural environment
- tried cursor first, felt weird leaving vim
- claude code met me where I was
- not about which is better, about workflow fit
- some devs love IDE integration
- I need terminal access
- conclusion: use what fits YOUR workflow
```
Process:
1. Read voice-tone.md
2. Check story-circle.md - yes, there's a journey here
3. Identify structure: Current tools → Trying Cursor → Finding Claude Code → Realization
4. Write opening hook about tool debates
5. Show vulnerability about trying new things
6. Include specific terminal commands naturally
7. Conclude with "meet yourself where you are" message
8. Review for conversational tone and specific details
@@ -0,0 +1,99 @@
# Tech Talk Story Circle Framework
The Story Circle is an eight-step framework adapted from Dan Harmon's storytelling technique. It structures tech talks to create engaging narratives.
## The Eight Steps
### 1. Introduction (You)
**Top half - Order**
Introduce yourself and the current status quo of your project.
- Set the scene with the existing workflow or technology stack
- Establish the baseline before disruption
- Make the audience understand the familiar ground
### 2. Problem Statement (Need)
**Top half - Order**
Identify and explain the problem you're trying to solve.
- Clearly articulate what's not working
- Help the audience feel the pain point
- Create the motivation for change
### 3. Exploration (Go)
**Crossing to bottom half - Chaos**
Describe the steps taken to address the problem.
- What did you try?
- What worked?
- What didn't work?
- Show the journey into the unknown
### 4. Experimentation (Search)
**Bottom half - Chaos**
Detail the process of digging into the actual problem.
- What did you learn?
- What experiments did you run?
- What discoveries did you make?
- Share the messy middle of problem-solving
### 5. Solution (Find)
**Bottom half - Chaos**
Explain how you found the solution or made progress.
- Present the breakthrough moment
- Show what finally clicked
- Explain the technical approach that worked
### 6. Challenges (Take)
**Bottom half - Chaos**
Discuss the actual implementation of the project.
- Emphasize the disruption to the status quo
- Share the difficulties and tradeoffs
- Be honest about the cost of change
### 7. Apply Knowledge (Return)
**Crossing to top half - Order**
Describe the results and how the solution was integrated.
- Show how you brought the solution back to your project
- Demonstrate the practical application
- Return to the familiar with new tools
### 8. Results & Insights (Change)
**Top half - Order**
Conclude with lessons learned and how things changed.
- Share metrics or outcomes
- Explain what changed in your workflow or perspective
- Leave the audience with actionable insights
## Structure Notes
**Top half (steps 1, 2, 7, 8)**: Represents established practices and order
**Bottom half (steps 3, 4, 5, 6)**: Represents disruption and experimentation
The character (you) starts in the top half, enters the bottom half to experiment and disrupt, then returns to the top half with new knowledge, changing the status quo.
## Example
From "Unleashing the TypeScript Compiler":
1. Status quo of a TypeScript/React project using Material-UI
2. Challenges faced with the project
3. Solutions tried to work around issues
4. Exploring the TypeScript compiler and codemods
5. Using new knowledge to solve problems
6. Challenges implementing the solution for every scenario
7. Applying knowledge to the project
8. Results and changed team perspective on codemods
@@ -0,0 +1,150 @@
# Nick Nisi's Voice and Tone
Captured from analyzing posts at nicknisi.com
## Core Writing Characteristics
### Voice
Personal, authentic, conversational yet thoughtful. Nick writes like he's having a one-on-one conversation with a peer developer over coffee.
### Vulnerability
Nick isn't afraid to admit uncertainty, fear, or being wrong. He shares his journey from skepticism to understanding.
Examples:
- "I was wrong, but not in the way I feared."
- "I won't lie – joining Meta was intimidating."
- "That night in my hotel room, I couldn't sleep."
- "Looking at my interviewers' backgrounds... it was hard not to feel like an outsider."
### Narrative Structure
Posts often follow a journey: initial position → experience/challenge → realization → new understanding. He builds tension and resolves it.
### Sentence Style
- Mix of short punchy sentences and longer explanatory ones
- Uses fragments for emphasis
- Varies paragraph length for rhythm
- Short paragraphs for key moments: "🤯" stands alone, "That changed everything." gets its own paragraph
### Specific Phrases and Patterns
**Opening hooks:**
- Sets up expectations then challenges them
- Often starts with current position or recent event
- "I've been thinking a lot about..."
- "Want to dive in? [Links]" (practical calls to action upfront)
**Transitions:**
- "Here's what I've learned..."
- "The strange part?"
- "Let's talk about..."
- "But beneath the apprehension..."
**Emphasis techniques:**
- Single-line paragraphs for impact
- Emojis used sparingly but effectively (🤯, 😂)
- Italics for internal thoughts or emphasis
- Bold for key concepts
**Metaphors and analogies:**
- Technical concepts explained through relatable comparisons
- "Like cooking with your eyes closed"
- "The developers who insist on writing every line by hand are like accountants refusing to use spreadsheets"
- "It was a pair programmer who spoke fluent bash"
### Technical Writing Style
**Code and tools:**
- Mentions specific tools naturally (vim, tmux, rg, npm)
- Shows actual commands and code when relevant
- Explains technical decisions without over-explaining
- Assumes reader has technical knowledge but explains when needed
**Examples:**
- Inline code formatting: `CLAUDE.md`, `git`, `npm test`
- Commands shown naturally in prose
- Tool names used casually: "I watched it use rg to search through codebases"
### Honesty About Limitations
Nick admits when things aren't perfect:
- "The PRs it generated weren't perfect. But they worked. Somewhat."
- "Would I ship our vibe-coded GitHub Action to production? No way."
- "Not perfect, not production-ready, but working."
### Self-Awareness and Humor
Light self-deprecation and humor:
- "(except maybe 'Why doesn't Nick use VS Code?' 😉)"
- "One of my favorite memories? Getting texts from friends asking why my face kept showing up in their Instagram feeds."
- "I like to think I brought a certain… charm to people's social media experience."
- Acknowledging his tooling preferences with humor
### Structure Patterns
**Sections often use:**
- Clear headers that are descriptive
- Lists with explanations
- Tables when comparing options
- Code examples with context
- Pull quotes or emphasized text
**Common section patterns:**
- The Setup/Problem → The Journey → The Results → Lessons Learned
- Philosophy sections: "Here's what I've learned..."
- How-to sections with practical steps
- Reflection sections: "Looking back..."
### Conclusions
Endings often:
- Tie back to opening tension or question
- Offer forward-looking perspective
- Include actionable advice
- End on optimistic or thought-provoking note
Examples:
- "The party isn't over – we're just changing the runtime!"
- "That week, I learned to code with my eyes wide shut. The strange part? I've never seen more clearly where we're headed."
- "You're not being replaced; you're being amplified."
### Authenticity Markers
**Real examples:**
- Specific projects and PRs with links
- Actual teammates mentioned by name
- Real events (MCP Night, onsite meetings)
- Concrete details (5,000 lines of TypeScript, two hours, 600 developers)
**Acknowledges help:**
- "Thanks to John Christopher for reviewing this post."
- Credits teammates and collaborators
### Tone Shifts
Nick modulates tone based on content:
- **Technical tutorials**: Clear, instructional, still conversational
- **Personal reflections**: Vulnerable, thoughtful
- **Tool reviews**: Enthusiastic but honest
- **Career stories**: Reflective, self-aware
### What to Avoid
- Corporate speak or marketing language
- Overly formal academic tone
- Pretending to have all the answers
- Dismissing reader concerns
- Being preachy or condescending
- Hiding uncertainty or mistakes
### Key Principles
1. Be conversational but substantive
2. Share the journey, not just the destination
3. Admit when you're uncertain or learning
4. Use specific details and real examples
5. Balance technical depth with accessibility
6. End with forward momentum
7. Write for a peer, not a student
8. Show vulnerability builds credibility
9. Humor works when it's self-aware
10. Practical value matters
@@ -0,0 +1,124 @@
---
name: content-brief
description: Content brief template and creation methodology for SEO-optimized content. Use when preparing briefs for writers or planning new content pieces.
---
# Content Brief
## When to Use
- Preparing briefs for content writers
- Planning new content pieces
- Documenting SEO requirements for articles
- Aligning content with keyword research
## Brief Creation Methodology
### Step 1: Keyword Research
1. Identify primary keyword (highest priority)
2. Identify 3-5 secondary keywords
3. Extract People Also Ask questions
4. Note search intent (informational/commercial/transactional)
### Step 2: SERP Analysis
1. Analyze top 10 ranking pages
2. Note average word count
3. Identify common content format (listicle, guide, etc.)
4. Find content gaps (topics competitors miss)
### Step 3: Outline Creation
1. Create H1 with primary keyword
2. Plan H2s to cover required topics
3. Plan H3s for detailed sections
4. Map keywords to specific sections
### Step 4: Requirements Definition
1. Set word count target (based on competitors + 20%)
2. Define E-E-A-T requirements
3. Specify internal linking targets
4. Set readability target (Flesch 60-70)
## Brief Template
```markdown
---
type: content-brief
created_by: {agent_or_command}
created_at: {timestamp}
keyword: "{keyword}"
session_id: {session_id}
session_path: {session_path}
status: complete
---
# Content Brief: {Title}
## Target Keyword
- **Primary**: {keyword}
- **Secondary**: {keyword2}, {keyword3}, {keyword4}
- **Questions to Answer**:
1. {PAA question 1}
2. {PAA question 2}
3. {PAA question 3}
## Search Intent
- **Type**: Informational | Commercial | Transactional
- **User Goal**: {what user wants to accomplish}
## Content Specifications
- **Word Count**: {min}-{max} words
- **Format**: {article, listicle, guide, comparison}
- **Tone**: {professional, conversational, technical}
- **Target Audience**: {description}
## Required Sections
1. **{H2: Section topic}** - {brief description of what to cover}
2. **{H2: Section topic}** - {brief description}
3. **{H2: Section topic}** - {brief description}
4. **{H2: Section topic}** - {brief description}
## Featured Snippet Opportunity
- **Type**: {paragraph, list, table}
- **Target Query**: {question to answer}
- **Format**: {how to structure the answer}
## Competitor Analysis
| Competitor | Word Count | Unique Angle | Gap |
|------------|------------|--------------|-----|
| {site1} | {count} | {angle} | {what they miss} |
| {site2} | {count} | {angle} | {what they miss} |
| {site3} | {count} | {angle} | {what they miss} |
## E-E-A-T Requirements
- **Experience**: {specific examples to include from first-hand experience}
- **Expertise**: {depth of coverage required, technical accuracy needs}
- **Authority**: {sources to cite, data to include}
- **Trust**: {claims to verify, transparency requirements}
## Internal Linking
- Link to: {list of existing content to link}
- Anchor text suggestions: {list}
## SEO Requirements Checklist
- [ ] Keyword in title and H1
- [ ] Keyword in first 100 words
- [ ] 1-2% keyword density
- [ ] Minimum 3 internal links
- [ ] At least 1 external authoritative link
- [ ] Meta title: 50-60 characters
- [ ] Meta description: 150-160 characters with CTA
- [ ] Flesch Reading Ease: 60-70
```
## Quality Checklist
Before finalizing a brief, verify:
- [ ] Primary keyword clearly defined
- [ ] Search intent identified and explained
- [ ] Word count based on competitor analysis
- [ ] All PAA questions captured
- [ ] Required sections cover all topics
- [ ] E-E-A-T requirements specific and actionable
- [ ] Internal linking targets identified
- [ ] Featured snippet opportunity noted (if any)
+9 -5
View File
@@ -8,6 +8,8 @@ AI execution guide for content creator workflow.
|-------|---------|
| nano-banana | generate image, AI image, cover image, thumbnail, illustration |
| canvas-design | design, image, cover, visual |
| blog-post-writer | blog post, write article, transform notes |
| content-brief | content brief, content plan, SEO brief |
| docx | Word, document, export docx |
| pdf | PDF, export pdf |
| social-repurposer | Twitter thread, LinkedIn, social media conversion |
@@ -19,10 +21,11 @@ AI execution guide for content creator workflow.
### Content Creation Flow
1. **Research Phase** - Gather materials and information
2. **Writing Phase** - Create long-form content
3. **Design Phase** - Use nano-banana or canvas-design for visuals
4. **Conversion Phase** - Use social-repurposer for multi-platform versions
5. **Export Phase** - Use docx/pdf for document export
2. **Planning Phase** - Use content-brief to create SEO-optimized content plan
3. **Writing Phase** - Use blog-post-writer to transform notes into polished articles
4. **Design Phase** - Use nano-banana or canvas-design for visuals
5. **Conversion Phase** - Use social-repurposer for multi-platform versions
6. **Export Phase** - Use docx/pdf for document export
### Podcast Flow
@@ -32,7 +35,7 @@ AI execution guide for content creator workflow.
## Skill Combinations
- **Long-form + Multi-platform**: Writing → nano-banana (cover) → social-repurposer → multi-platform content
- **Blog + Multi-platform**: content-brief → blog-post-writer → nano-banana (cover) → social-repurposer
- **Podcast + Article**: podcast-content-suite → content-repurposer → blog article
- **Visual Content**: nano-banana (AI generation) or canvas-design (design editing) → cover/illustration
@@ -42,3 +45,4 @@ AI execution guide for content creator workflow.
- Twitter thread: 8-12 tweets, <280 characters each
- LinkedIn: Professional tone, under 1300 characters
- Podcast outline: Clear segments, timestamp suggestions
- Content brief: SEO requirements, competitor analysis, E-E-A-T guidelines
+7 -4
View File
@@ -17,6 +17,8 @@ Claude Code workflow for bloggers, content creators, and personal brand builders
|-------|----------|-----------------|
| nano-banana | AI image generation (Gemini) | "Generate a blog cover image" |
| canvas-design | AI visual design, PNG/PDF export | "Design a cover image" |
| blog-post-writer | Transform notes into blog posts | "Write a blog post from my notes" |
| content-brief | SEO content planning briefs | "Create a content brief for [topic]" |
| docx | Word document creation/editing | "Export to Word document" |
| pdf | PDF processing and generation | "Generate PDF" |
| social-repurposer | Cross-platform content conversion | "Convert to Twitter thread" |
@@ -38,10 +40,11 @@ cd content-creator-workflow
```
1. "Research the latest trends on [topic]"
2. "Write an in-depth article based on the research"
3. "Use nano-banana to generate a blog cover image"
4. "Use social-repurposer to convert to Twitter thread and LinkedIn post"
5. "Export to Word document"
2. "Create a content brief for [topic]"
3. "Write a blog post from my research notes"
4. "Use nano-banana to generate a blog cover image"
5. "Use social-repurposer to convert to Twitter thread and LinkedIn post"
6. "Export to Word document"
```
### Podcast Creation
+7 -4
View File
@@ -15,6 +15,8 @@
|-------|------|---------|
| nano-banana | AI图片生成 (Gemini) | "生成一张博客封面图" |
| canvas-design | AI视觉设计,生成PNG/PDF | "设计一张封面图" |
| blog-post-writer | 将笔记转化为博客文章 | "根据我的笔记写一篇博客" |
| content-brief | SEO内容规划简报 | "为[主题]创建内容规划" |
| docx | Word文档创建和编辑 | "导出为Word文档" |
| pdf | PDF处理和生成 | "生成PDF" |
| social-repurposer | 跨平台内容转换 | "转换为Twitter thread" |
@@ -36,10 +38,11 @@ cd content-creator-workflow
```
1. "帮我研究一下 [话题] 的最新趋势"
2. "根据研究写一篇深度文章"
3. "用 nano-banana 生成一张博客封面图"
4. "用 social-repurposer 转换为 Twitter thread 和 LinkedIn post"
5. "导出为 Word 文档"
2. "为 [话题] 创建内容规划简报"
3. "根据我的研究笔记写一篇博客文章"
4. "用 nano-banana 生成一张博客封面图"
5. "用 social-repurposer 转换为 Twitter thread 和 LinkedIn post"
6. "导出为 Word 文档"
```
### 播客创作
@@ -0,0 +1,199 @@
---
name: analytics-interpretation
description: Interpret GA4 and GSC data with benchmarks, status indicators, and actionable insights
---
# Analytics Interpretation
## When to Use
- Analyzing content performance reports
- Understanding traffic patterns
- Interpreting search console data
- Making data-driven content decisions
- Explaining metrics to stakeholders
## Metric Benchmarks
### Google Analytics 4 (GA4)
| Metric | Good | Warning | Poor | Action When Poor |
|--------|------|---------|------|------------------|
| Avg Time on Page | >3 min | 1-3 min | <1 min | Improve content depth, add multimedia |
| Bounce Rate | <40% | 40-70% | >70% | Add internal links, improve intro hook |
| Engagement Rate | >60% | 30-60% | <30% | Review content quality, add CTAs |
| Scroll Depth | >75% | 50-75% | <50% | Add visual breaks, improve structure |
| Pages/Session | >2.5 | 1.5-2.5 | <1.5 | Improve internal linking |
### Google Search Console (GSC)
| Metric | Good | Warning | Poor | Action When Poor |
|--------|------|---------|------|------------------|
| CTR | >5% | 2-5% | <2% | Improve title/meta description |
| Avg Position | 1-3 | 4-10 | >10 | Strengthen content, build links |
| Impressions Trend | Growing | Stable | Declining | Refresh content, target new keywords |
| Mobile Usability | PASS | - | FAIL | Fix mobile issues immediately |
| Core Web Vitals | GOOD | NEEDS_IMPROVEMENT | POOR | Optimize performance |
## Interpreting Combined Signals
### Traffic Quality Matrix
```
High Engagement
│
┌──────────────┼──────────────┐
│ HIDDEN GEM │ STAR │
│ Low traffic │ High traffic│
│ High quality│ High quality│
│ → Promote │ → Maintain │
Low ───────┼──────────────┼──────────────┼─── High
Traffic │ │ │ Traffic
│ UNDERPERFORM│ LEAKY │
│ Low traffic │ High traffic│
│ Low quality │ Low quality │
│ → Rework │ → Optimize │
└──────────────┼──────────────┘
│
Low Engagement
```
### Search Intent Alignment
| GSC Signal | GA4 Signal | Interpretation |
|------------|------------|----------------|
| High impressions | Low clicks | Title/meta mismatch with intent |
| High CTR | High bounce | Content doesn't deliver on promise |
| Low CTR | High engagement (when clicked) | Hidden gem, improve snippet |
| Growing impressions | Stable clicks | Ranking improving, CTR opportunity |
## Score Calculation Methodology
### Content Health Score (0-100)
```
health_score = (
engagement_score × 0.30 +
seo_score × 0.30 +
ranking_score × 0.20 +
trend_score × 0.20
)
```
**Component Calculations:**
```
engagement_score = normalize(
time_on_page_score × 0.4 +
bounce_rate_score × 0.3 +
scroll_depth_score × 0.3
)
seo_score = normalize(
ctr_score × 0.4 +
position_score × 0.4 +
impressions_growth × 0.2
)
ranking_score = normalize(
avg_position × 0.5 +
visibility_score × 0.3 +
keyword_coverage × 0.2
)
trend_score = normalize(
traffic_trend × 0.4 +
ranking_trend × 0.3 +
engagement_trend × 0.3
)
```
### Score Interpretation
| Score | Rating | Status | Action |
|-------|--------|--------|--------|
| 90-100 | Excellent | Performing optimally | Maintain, minor tweaks |
| 75-89 | Good | Solid performance | Optimize weak areas |
| 60-74 | Fair | Room for improvement | Address key issues |
| 40-59 | Poor | Underperforming | Major revision needed |
| 0-39 | Critical | Failing | Complete overhaul |
## Trend Analysis
### Week-over-Week Comparison
```markdown
| Metric | This Week | Last Week | Change | Status |
|--------|-----------|-----------|--------|--------|
| Sessions | 1,245 | 1,180 | +5.5% | ↑ GROWING |
| Avg Position | 4.2 | 4.8 | +0.6 | ↑ IMPROVING |
| CTR | 2.8% | 2.6% | +0.2pp | ↑ IMPROVING |
| Bounce Rate | 42% | 38% | +4pp | ↓ DECLINING |
```
### Interpreting Trends
| Trend Pattern | Interpretation | Recommended Action |
|---------------|----------------|-------------------|
| ↑↑↑ All metrics up | Content gaining momentum | Double down, create related content |
| ↑↓↑ Mixed signals | Transition period | Monitor closely, identify cause |
| ↓↓↓ All metrics down | Content declining | Urgent refresh needed |
| →→→ All flat | Plateau reached | Experiment with new angles |
## Anomaly Detection
### Significant Change Thresholds
| Metric | Significant Change | Alert Level |
|--------|-------------------|-------------|
| Traffic | ±30% WoW | HIGH |
| CTR | ±1pp WoW | MEDIUM |
| Position | ±5 positions | HIGH |
| Bounce Rate | ±10pp WoW | MEDIUM |
### Common Anomaly Causes
| Anomaly | Possible Causes |
|---------|-----------------|
| Sudden traffic drop | Algorithm update, technical issue, competitor |
| CTR spike | SERP feature win, seasonal interest |
| Position fluctuation | Google testing, competitor changes |
| Engagement drop | Content staleness, UX issue |
## Output Templates
### Metric Summary Card
```markdown
## {Metric Name}
**Current Value**: {value}
**Benchmark**: {benchmark}
**Status**: {GOOD|WARNING|POOR}
**Trend**: {↑|→|↓} ({change}% vs last period)
**Interpretation**: {1-2 sentence explanation}
**Recommended Action**: {specific action if needed}
```
### Executive Summary
```markdown
## Content Performance Summary
**Overall Health**: {score}/100 ({rating})
### Key Wins
- {positive finding 1}
- {positive finding 2}
### Concerns
- {issue 1}
- {issue 2}
### Priority Actions
1. {highest priority action}
2. {second priority action}
3. {third priority action}
```
@@ -0,0 +1,124 @@
---
name: content-brief
description: Content brief template and creation methodology for SEO-optimized content. Use when preparing briefs for writers or planning new content pieces.
---
# Content Brief
## When to Use
- Preparing briefs for content writers
- Planning new content pieces
- Documenting SEO requirements for articles
- Aligning content with keyword research
## Brief Creation Methodology
### Step 1: Keyword Research
1. Identify primary keyword (highest priority)
2. Identify 3-5 secondary keywords
3. Extract People Also Ask questions
4. Note search intent (informational/commercial/transactional)
### Step 2: SERP Analysis
1. Analyze top 10 ranking pages
2. Note average word count
3. Identify common content format (listicle, guide, etc.)
4. Find content gaps (topics competitors miss)
### Step 3: Outline Creation
1. Create H1 with primary keyword
2. Plan H2s to cover required topics
3. Plan H3s for detailed sections
4. Map keywords to specific sections
### Step 4: Requirements Definition
1. Set word count target (based on competitors + 20%)
2. Define E-E-A-T requirements
3. Specify internal linking targets
4. Set readability target (Flesch 60-70)
## Brief Template
```markdown
---
type: content-brief
created_by: {agent_or_command}
created_at: {timestamp}
keyword: "{keyword}"
session_id: {session_id}
session_path: {session_path}
status: complete
---
# Content Brief: {Title}
## Target Keyword
- **Primary**: {keyword}
- **Secondary**: {keyword2}, {keyword3}, {keyword4}
- **Questions to Answer**:
1. {PAA question 1}
2. {PAA question 2}
3. {PAA question 3}
## Search Intent
- **Type**: Informational | Commercial | Transactional
- **User Goal**: {what user wants to accomplish}
## Content Specifications
- **Word Count**: {min}-{max} words
- **Format**: {article, listicle, guide, comparison}
- **Tone**: {professional, conversational, technical}
- **Target Audience**: {description}
## Required Sections
1. **{H2: Section topic}** - {brief description of what to cover}
2. **{H2: Section topic}** - {brief description}
3. **{H2: Section topic}** - {brief description}
4. **{H2: Section topic}** - {brief description}
## Featured Snippet Opportunity
- **Type**: {paragraph, list, table}
- **Target Query**: {question to answer}
- **Format**: {how to structure the answer}
## Competitor Analysis
| Competitor | Word Count | Unique Angle | Gap |
|------------|------------|--------------|-----|
| {site1} | {count} | {angle} | {what they miss} |
| {site2} | {count} | {angle} | {what they miss} |
| {site3} | {count} | {angle} | {what they miss} |
## E-E-A-T Requirements
- **Experience**: {specific examples to include from first-hand experience}
- **Expertise**: {depth of coverage required, technical accuracy needs}
- **Authority**: {sources to cite, data to include}
- **Trust**: {claims to verify, transparency requirements}
## Internal Linking
- Link to: {list of existing content to link}
- Anchor text suggestions: {list}
## SEO Requirements Checklist
- [ ] Keyword in title and H1
- [ ] Keyword in first 100 words
- [ ] 1-2% keyword density
- [ ] Minimum 3 internal links
- [ ] At least 1 external authoritative link
- [ ] Meta title: 50-60 characters
- [ ] Meta description: 150-160 characters with CTA
- [ ] Flesch Reading Ease: 60-70
```
## Quality Checklist
Before finalizing a brief, verify:
- [ ] Primary keyword clearly defined
- [ ] Search intent identified and explained
- [ ] Word count based on competitor analysis
- [ ] All PAA questions captured
- [ ] Required sections cover all topics
- [ ] E-E-A-T requirements specific and actionable
- [ ] Internal linking targets identified
- [ ] Featured snippet opportunity noted (if any)
@@ -0,0 +1,112 @@
---
name: content-optimizer
description: On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability. Use when optimizing existing content or validating new content against SEO requirements.
---
# Content Optimizer
## When to Use
- Optimizing existing content for better rankings
- Validating new content against SEO requirements
- Checking keyword density and placement
- Improving readability scores
- Creating meta tags
## Keyword Density
**Target:** 1-2% for primary keyword
**Calculation:**
```
Density = (Keyword Count / Total Words) x 100
```
**Placement Priorities:**
1. Title/H1 (required)
2. First 100 words (required)
3. At least one H2 (recommended)
4. Conclusion (recommended)
5. Distributed in body (natural)
**Warning Signs:**
- >3% = Keyword stuffing risk
- <0.5% = Under-optimized
- Exact match every paragraph = Unnatural
## Meta Tag Optimization
### Title Tag
- Length: 50-60 characters
- Keyword: Near the beginning
- Format: `{Keyword} - {Benefit} | {Brand}`
- Unique per page
### Meta Description
- Length: 150-160 characters
- Keyword: Include naturally
- CTA: End with action verb
- Unique per page
### URL Slug
- Short: 3-5 words
- Keyword: Include primary
- Readable: Use hyphens
- Lowercase only
## Heading Structure
**Valid Hierarchy:**
```
H1: Page Title (exactly 1)
+-- H2: Main Section
| +-- H3: Subsection
| +-- H3: Subsection
+-- H2: Main Section
| +-- H3: Subsection
+-- H2: Conclusion
```
**Common Errors:**
- Multiple H1 tags
- Skipping levels (H1 -> H3)
- Using headings for styling only
- No keyword in H1
## Readability Optimization
**Flesch Reading Ease Target: 60-70**
| Score | Level | Audience |
|-------|-------|----------|
| 90-100 | Very Easy | 5th grade |
| 80-89 | Easy | 6th grade |
| 70-79 | Fairly Easy | 7th grade |
| 60-69 | Standard | 8th-9th grade |
| 50-59 | Fairly Difficult | 10th-12th grade |
| 30-49 | Difficult | College |
| 0-29 | Very Difficult | College graduate |
**Improvement Techniques:**
- Shorten sentences (<20 words avg)
- Shorten paragraphs (2-3 sentences)
- Replace jargon with plain language
- Use active voice
- Add subheadings every 200-300 words
- Use bullet points for lists
## Optimization Checklist
Use this checklist when optimizing content:
- [ ] Primary keyword in title/H1
- [ ] Primary keyword in first 100 words
- [ ] Keyword density 1-2%
- [ ] Meta title 50-60 characters
- [ ] Meta description 150-160 characters with CTA
- [ ] Heading hierarchy valid (H1 -> H2 -> H3)
- [ ] At least 3 internal links
- [ ] At least 1 external authoritative link
- [ ] Flesch score 60-70
- [ ] No paragraphs > 3 sentences
- [ ] Subheadings every 200-300 words
@@ -0,0 +1,100 @@
---
name: keyword-cluster-builder
description: Techniques for expanding seed keywords and clustering by topic and intent. Use when building keyword lists, planning content calendars, or identifying topic clusters for pillar content strategy.
---
# Keyword Cluster Builder
## When to Use
- Expanding seed keywords to comprehensive lists (50-100+)
- Grouping keywords by topic for pillar content strategy
- Mapping keywords to funnel stages
- Identifying content gaps in keyword coverage
## Expansion Techniques
### Question Modifiers
- What is {keyword}
- How to {keyword}
- Why {keyword}
- When to {keyword}
- Where to {keyword}
### Comparative Modifiers
- {keyword} vs {competitor}
- {keyword} alternatives
- best {keyword}
- {keyword} comparison
### Intent Modifiers
- {keyword} guide
- {keyword} tutorial
- {keyword} examples
- {keyword} template
- buy {keyword}
- {keyword} pricing
### Audience Modifiers
- {keyword} for beginners
- {keyword} for {industry}
- {keyword} for small business
- {keyword} for enterprise
## Clustering Algorithm
1. **Extract Seed Topics**: Identify main themes from expanded list
2. **Group by Semantic Similarity**: Keywords with overlapping meaning
3. **Map Intent**: Assign I/C/T/N to each cluster
4. **Identify Pillar**: Highest-volume, broadest term = pillar
5. **Map Supporting**: Lower-volume terms support pillar
## Cluster Structure
```
PILLAR: "content marketing" (highest volume)
+-- CLUSTER: "content marketing strategy" (commercial)
| +-- content marketing plan template
| +-- content marketing framework
| +-- how to create content marketing strategy
+-- CLUSTER: "content marketing examples" (informational)
| +-- B2B content marketing examples
| +-- content marketing case studies
| +-- content marketing success stories
+-- CLUSTER: "content marketing tools" (commercial)
+-- best content marketing tools
+-- content marketing software
+-- content marketing platforms
```
## Intent Classification Rules
| Signal | Intent |
|--------|--------|
| "what is", "how to", "guide" | Informational |
| "best", "vs", "review", "compare" | Commercial |
| "buy", "price", "discount", brand | Transactional |
| Brand name, specific product | Navigational |
## Output Format
When generating keyword clusters, use this format:
```markdown
## Keyword Cluster Report
**Seed Keyword**: {seed}
**Total Keywords**: {count}
**Clusters**: {cluster_count}
### Cluster 1: {cluster_name}
**Intent**: {intent}
**Funnel Stage**: {stage}
**Keywords**:
1. {keyword1} - {estimated_volume}
2. {keyword2} - {estimated_volume}
...
### Cluster 2: {cluster_name}
...
```
@@ -0,0 +1,115 @@
---
name: serp-analysis
description: SERP analysis techniques for intent classification, feature identification, and competitive intelligence. Use when analyzing search results for content strategy.
---
# SERP Analysis
## When to Use
- Analyzing search results for a keyword
- Classifying search intent
- Identifying SERP feature opportunities
- Competitive intelligence gathering
## Intent Classification
### Intent Types
| Intent | SERP Signals | User Goal | Content Format |
|--------|--------------|-----------|----------------|
| **Informational** | Wikipedia, knowledge panels, "what is" queries | Learn something | Guide, tutorial, explainer |
| **Commercial** | Reviews, comparisons, "best X" queries | Compare options | Comparison, listicle, review |
| **Transactional** | Product pages, shopping results, "buy X" | Purchase something | Product page, pricing |
| **Navigational** | Brand homepage, login pages | Find specific site | Homepage, login page |
### Classification Process
1. **Search the keyword** using WebSearch
2. **Analyze result types**:
- All informational = Informational intent
- Mix of reviews/comparisons = Commercial intent
- Product pages dominant = Transactional intent
- Single brand dominant = Navigational intent
3. **Check for mixed intent** (common for broad keywords)
4. **Note confidence level** (% of results supporting classification)
## SERP Features
### Feature Identification
| Feature | How to Identify | Optimization Strategy |
|---------|-----------------|----------------------|
| **Featured Snippet** | Box at top with answer | Direct answer in first 100 words |
| **People Also Ask** | Expandable question boxes | FAQ section, answer common questions |
| **Image Pack** | Row of images | High-quality images with alt text |
| **Video Results** | YouTube thumbnails | Create video content |
| **Local Pack** | Map with business listings | GMB optimization, location pages |
| **Knowledge Panel** | Right sidebar info box | Schema markup, Wikipedia presence |
| **Sitelinks** | Sub-links under main result | Clear site structure, internal linking |
### Featured Snippet Types
| Type | Format | How to Optimize |
|------|--------|-----------------|
| Paragraph | Text block | 40-60 word direct answer |
| List | Numbered/bulleted list | Use ordered/unordered lists |
| Table | Data table | Use HTML tables |
| Video | YouTube embed | Create relevant video content |
## Competitive Analysis
### Competitor Data to Collect
For each top 10 result, note:
1. **Domain authority** (relative, not exact)
2. **Content format** (guide, listicle, comparison, etc.)
3. **Word count** (approximate)
4. **Heading structure** (H2 topics covered)
5. **Unique angle** (what makes them different)
6. **Content gaps** (what they miss)
### Competitor Matrix Template
| Rank | Domain | Format | Words | Unique Angle | Gap |
|------|--------|--------|-------|--------------|-----|
| 1 | {domain} | {format} | {count} | {angle} | {gap} |
| 2 | {domain} | {format} | {count} | {angle} | {gap} |
| ... | | | | | |
## Output Format
```markdown
## SERP Analysis: {keyword}
### Search Intent
- **Primary Intent**: {Informational | Commercial | Transactional | Navigational}
- **Confidence**: {percentage}%
- **Secondary Intent**: {if mixed}
### SERP Features Present
- [ ] Featured Snippet ({type})
- [ ] People Also Ask
- [ ] Image Pack
- [ ] Video Results
- [ ] Local Pack
- [ ] Knowledge Panel
- [ ] Sitelinks
### Competitor Analysis
| Rank | Domain | Format | Words | Unique Angle |
|------|--------|--------|-------|--------------|
| 1 | {domain} | {format} | {count} | {angle} |
...
### Content Gaps Identified
1. {gap} - {which competitors miss this}
2. {gap} - {which competitors miss this}
### Recommendations
1. **Content Format**: {recommended format based on SERP}
2. **Word Count**: {recommended based on competitors + 20%}
3. **Featured Snippet**: {opportunity and how to capture}
4. **Differentiator**: {unique angle to stand out}
```
+23 -7
View File
@@ -7,6 +7,11 @@ AI execution guide for marketing professional workflow.
| Skill | Trigger |
|-------|---------|
| seo-optimizer | SEO, optimize keywords, search ranking |
| content-optimizer | keyword density, meta tags, heading structure, readability |
| serp-analysis | SERP analysis, search results, competitor analysis |
| keyword-cluster-builder | keyword research, keyword expansion, topic clusters |
| analytics-interpretation | GA4, GSC, analytics, metrics, traffic analysis |
| content-brief | content brief, content plan, SEO brief |
| linkedin-post-optimizer | LinkedIn, professional post optimization |
| social-repurposer | social media conversion, multi-platform |
| landing-page-copywriter | landing page, conversion copy |
@@ -14,6 +19,14 @@ AI execution guide for marketing professional workflow.
## Recommended Workflow
### SEO Content Strategy
1. **Keyword Research** - Use keyword-cluster-builder to expand and cluster keywords
2. **SERP Analysis** - Use serp-analysis to understand search intent and competition
3. **Content Planning** - Use content-brief to create detailed content requirements
4. **Content Creation** - Write content following the brief
5. **Optimization** - Use content-optimizer to verify SEO requirements
### Marketing Campaign Flow
1. **Copywriting** - Use landing-page-copywriter to create core copy
@@ -22,18 +35,18 @@ AI execution guide for marketing professional workflow.
4. **Social Distribution** - Use social-repurposer to convert formats
5. **LinkedIn Optimization** - Use linkedin-post-optimizer for professional optimization
### Content Marketing Flow
### Analytics Review
1. Create core content
2. SEO optimization
3. Multi-platform conversion
4. Platform-specific optimization
1. **Data Collection** - Gather GA4/GSC data
2. **Interpretation** - Use analytics-interpretation to understand metrics
3. **Action Planning** - Generate recommendations based on data
## Skill Combinations
- **SEO Campaign**: keyword-cluster-builder → serp-analysis → content-brief → content-optimizer
- **Product Launch**: landing-page-copywriter → email-template-generator → social-repurposer
- **Content Marketing**: Writing → seo-optimizer → social-repurposer → linkedin-post-optimizer
- **Email Marketing**: email-template-generator → landing-page-copywriter
- **Content Marketing**: content-brief → seo-optimizer → social-repurposer → linkedin-post-optimizer
- **Performance Review**: analytics-interpretation → content-optimizer (for underperforming content)
## Output Standards
@@ -41,3 +54,6 @@ AI execution guide for marketing professional workflow.
- Email Sequence: 3-5 emails, progressive engagement
- LinkedIn: Professional tone, under 1300 characters
- SEO: Include meta tags, keyword suggestions
- Content Brief: E-E-A-T requirements, competitor analysis
- SERP Analysis: Intent classification, feature opportunities, competitor matrix
- Keyword Clusters: Grouped by topic and intent, funnel stage mapping
+18 -3
View File
@@ -8,14 +8,19 @@ Claude Code workflow for digital marketers and social media managers.
- Digital Marketers
- Social Media Managers
- SEO Specialists
- Marketing Teams
- Brand Operators
## Installed Skills
| Skill | Function | Trigger Example |
|-------|----------|-----------------|
| seo-optimizer | SEO content optimization | "Optimize this article for SEO" |
| content-optimizer | On-page SEO, keyword density, meta tags | "Check keyword density" |
| serp-analysis | SERP analysis and competitor intelligence | "Analyze SERP for [keyword]" |
| keyword-cluster-builder | Keyword expansion and clustering | "Build keyword cluster for [topic]" |
| analytics-interpretation | GA4/GSC data interpretation | "Interpret this analytics data" |
| content-brief | SEO content planning briefs | "Create a content brief" |
| linkedin-post-optimizer | LinkedIn post optimization | "Optimize LinkedIn post" |
| social-repurposer | Cross-platform content conversion | "Convert to all platform formats" |
| landing-page-copywriter | Landing page copy | "Write landing page copy" |
@@ -32,6 +37,16 @@ cd marketing-pro-workflow
## Usage Examples
### SEO Content Strategy
```
1. "Build keyword cluster for [topic]"
2. "Analyze SERP for [primary keyword]"
3. "Create a content brief based on the analysis"
4. "Write the content"
5. "Use content-optimizer to check SEO requirements"
```
### Marketing Campaign Flow
```
@@ -42,10 +57,10 @@ cd marketing-pro-workflow
5. "Optimize LinkedIn version"
```
### SEO Content Optimization
### Analytics Review
```
"Use seo-optimizer to optimize this article, target keywords are [keywords]"
"Interpret this GA4 report and provide actionable insights"
```
## Multi-AI Tool Support
+19 -4
View File
@@ -6,14 +6,19 @@
- 数字营销人员
- 社交媒体经理
- 企业营销团队
- 品牌运营专员
- SEO专家
- 营销团队
## 已安装Skills
| Skill | 功能 | 触发示例 |
|-------|------|---------|
| seo-optimizer | SEO内容优化 | "优化这篇文章的SEO" |
| content-optimizer | 页面SEO、关键词密度、meta标签 | "检查关键词密度" |
| serp-analysis | SERP分析和竞争情报 | "分析[关键词]的搜索结果" |
| keyword-cluster-builder | 关键词扩展和聚类 | "为[主题]构建关键词聚类" |
| analytics-interpretation | GA4/GSC数据解读 | "解读这份分析数据" |
| content-brief | SEO内容规划简报 | "创建内容规划简报" |
| linkedin-post-optimizer | LinkedIn帖子优化 | "优化LinkedIn帖子" |
| social-repurposer | 跨平台内容转换 | "转换为各平台格式" |
| landing-page-copywriter | 落地页文案 | "写落地页文案" |
@@ -30,6 +35,16 @@ cd marketing-pro-workflow
## 使用示例
### SEO内容策略
```
1. "为[主题]构建关键词聚类"
2. "分析[主要关键词]的搜索结果"
3. "根据分析创建内容规划简报"
4. "撰写内容"
5. "使用content-optimizer检查SEO要求"
```
### 营销活动流程
```
@@ -40,10 +55,10 @@ cd marketing-pro-workflow
5. "优化LinkedIn版本"
```
### SEO内容优化
### 数据分析
```
"用 seo-optimizer 优化这篇文章,目标关键词是 [keywords]"
"解读这份GA4报告并提供可执行的建议"
```
## 多AI工具支持