blog-post-ideation

Category: Content & Multimedia | Uploader: CoolAssPuppy | Downloads: 0 | Version: v1.0（Latest）

Generates data-driven blog post ideas for developer products based on market research and community insights. Use when planning content calendars, identifying content gaps, finding topics that resonate with developers, differentiating from competitor content, or building SEO-driven strategies.

Changelog: Source: GitHub https://github.com/CoolAssPuppy/dotfiles

Directory Structure

Current level: claude/skills/blog-post-ideation/

📄 SKILL.md 4.8 KB

SKILL.md

---
user-invocable: true
name: blog-post-ideation
description: Generates data-driven blog post ideas for developer products based on market research and community insights. Use when planning content calendars, identifying content gaps, finding topics that resonate with developers, differentiating from competitor content, or building SEO-driven strategies.
metadata:
  author: prashant-sridharan
  version: "1.0"
  source: "Picks and Shovels by Prashant Sridharan"
---

# Developer blog post ideation

You are an expert in developer content marketing. Use this skill to generate data-driven blog post ideas based on market research and developer community insights.

## When to use this skill

Use this skill when:
- Planning content calendars and editorial schedules
- Identifying content gaps in your strategy
- Finding topics that resonate with developer audiences
- Differentiating from competitor content
- Building SEO-driven content strategies

## The prompt

Use this to generate data-driven content ideas based on market research:

```markdown
Generate 10 blog post ideas for [PRODUCT/COMPANY NAME] targeting [TARGET DEVELOPER AUDIENCE].

CONTEXT:
- Product: [WHAT IT DOES AND WHO IT'S FOR]
- Target audience: [ROLE, SENIORITY, TECH STACK]
- Current content gaps: [WHAT'S MISSING FROM YOUR BLOG]
- Business goals: [AWARENESS / LEADS / EDUCATION]
- Competitor blogs to differentiate from: [LIST 2-3]

RESEARCH METHODOLOGY:

First, search for recent discussions across these sources:
- Reddit: r/programming, r/webdev, r/devrel, relevant tech subreddits
- Hacker News: discussions about your space, competitors, related technologies
- Dev.to, Hashnode: trending posts in your category
- Twitter/X: conversations in relevant hashtags
- Stack Overflow: common questions and pain points
- Company blogs: What are Stripe, Vercel, Supabase writing about?

Look for:
- Pain points: What are developers struggling with?
- Controversies: What debates are happening?
- Knowledge gaps: What confuses people?
- Trends: What's emerging or gaining traction?
- Frustrations: What tools/processes are causing problems?
- Success stories: What's working well?

DELIVER THE FOLLOWING:

For each of the 10 blog post proposals:

1. TITLE (sentence case)
Clear, specific, compelling

2. ABSTRACT (4-6 sentences)
- Hook with the problem
- Why this matters now
- What most people get wrong
- Your unique angle or solution
- Specific outcome or benefit for the reader
- Who specifically this is for

3. CONTENT OPPORTUNITY SCORE
Rate each factor 1-10:
- Problem severity: How painful is this for developers?
- Audience size: How many developers face this?
- Solution complexity: Can you provide real value?
- Competitive gap: Are others covering this well?
- Business relevance: Does it connect to your product?
- Evergreen potential: Will this stay relevant?
Total: /60

4. TARGET KEYWORDS
- Primary keyword (with search intent)
- 2-3 secondary keywords
- Long-tail opportunities

5. OUTLINE
- H2 sections (4-6)
- Key points for each section
- Code examples or data to include
- Expert sources to cite

6. DISTRIBUTION STRATEGY
- Primary channel (company blog, Dev.to, etc.)
- Social media approach (thread, snippet, visual)
- Communities to share in (specific subreddits, Discord servers)
- Repurposing opportunities (newsletter, video, podcast)

7. DIFFERENTIATION
How this differs from existing content on the topic:
- Unique data or research
- Contrarian perspective
- More practical and actionable
- Better examples or case studies

RANKING:
After generating all 10, rank them by:
1. Highest opportunity score
2. Quickest to produce
3. Most likely to drive business results

Present in a clear, scannable format so I can quickly identify which posts to prioritize.
```

## Research sources for developer content

**Community platforms:**
- Reddit (r/programming, r/webdev, r/devops, tech-specific subreddits)
- Hacker News discussions
- Dev.to and Hashnode trending posts
- Stack Overflow questions and trends

**Social media:**
- Twitter/X developer conversations
- LinkedIn technical discussions
- Discord and Slack communities

**Competitor analysis:**
- Company engineering blogs (Stripe, Vercel, Supabase, Cloudflare)
- Developer documentation patterns
- Conference talk topics

**Search data:**
- Google Trends for developer topics
- Keyword research tools
- "People also ask" patterns

## Content opportunity scoring

Rate each factor 1-10:
- **Problem severity**: How painful is this for developers?
- **Audience size**: How many developers face this?
- **Solution complexity**: Can you provide real value?
- **Competitive gap**: Are others covering this well?
- **Business relevance**: Does it connect to your product?
- **Evergreen potential**: Will this stay relevant?

Posts scoring 45+ out of 60 are high-priority opportunities.

## References

- Based on methodology from "Picks and Shovels: Marketing to Developers During the AI Gold Rush"

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

blog-post-ideation

Directory Structure

SKILL.md

Report

Notice