Blog Post from Keyword Cluster
Generate a complete, SEO-optimized blog post from a Rampify keyword cluster. This skill pulls your keyword research, competitive landscape, and content specs, then writes a blog post that targets the right terms from the start.
Type: On-demand skill
Tools used: get_keyword_clusters, create_content_spec, optimize_content
Install path: .claude/skills/rampify-blog-post.md
Install#
Copy the skill file to your project:
mkdir -p .claude/skills
curl -o .claude/skills/rampify-blog-post.md \
https://raw.githubusercontent.com/rampify-dev/rampify-skills/main/skills/blog-post-from-cluster.md
Or create .claude/skills/rampify-blog-post.md manually with the content below.
The Skill File#
---
name: rampify-blog-post
description: Generate an SEO-optimized blog post from a Rampify keyword cluster
---
# Rampify Blog Post Generator
When the user asks to write a blog post, follow this workflow:
## 1. Get the keyword cluster
Use `get_keyword_clusters` to find the cluster for the target topic.
If the user provides a cluster name or URL, filter by that.
If not, list available clusters and ask which one to use.
## 2. Review the keyword data
From the cluster, identify:
- **Primary keyword** — this goes in the title, H1, meta description, and first paragraph
- **Secondary keywords** — work these into H2 headings and body paragraphs
- **Long-tail keywords** — sprinkle these naturally throughout the content
- **Competitive landscape** — understand who ranks and how to differentiate
- **Target URL** — where this post will live
## 3. Write the blog post
Structure the post as:
- Title containing the primary keyword (under 60 characters)
- Opening paragraph that includes the primary keyword naturally
- 3-5 H2 sections, each targeting a secondary or long-tail keyword
- Practical, specific content (code examples, step-by-step instructions, real data)
- Conclusion with a clear next step or CTA
## 4. Generate meta tags
After writing, create:
- Meta title (under 60 chars, primary keyword included)
- Meta description (under 160 chars, primary + secondary keyword)
## 5. Verify with audit
Run `optimize_content` on the target URL after the post is deployed
to verify keyword placement passes the audit. Fix any issues flagged.
## Guidelines
- Write for developers and technical builders, not marketers
- Be specific and actionable, not generic
- Use code blocks, examples, and real data where possible
- No fluff paragraphs. Every sentence should add value
- Match the voice of the site (check existing blog posts for tone)
- Target 1,000-2,000 words for standard posts
Usage#
Once installed, invoke the skill naturally during a Claude Code session:
> Write a blog post for the "ai seo tools" keyword cluster
> Generate a blog post targeting the /blog/schema-markup-guide URL
> Use the rampify-blog-post skill to write about automated keyword research
Claude will automatically use the skill when it matches your request.
What Happens#
- Claude reads the skill from
.claude/skills/rampify-blog-post.md - Calls
get_keyword_clustersto fetch your keyword data from Rampify - Identifies primary, secondary, and long-tail keywords from the cluster
- Writes a structured blog post targeting those keywords
- Generates meta tags with proper keyword placement
- After deploy, runs
optimize_contentto verify the audit passes
Example Output#
For a cluster targeting "schema markup for Next.js":
---
title: "Schema Markup for Next.js: A Developer's Guide to Structured Data"
description: "Learn how to add schema markup to your Next.js site.
JSON-LD implementation with App Router, dynamic schema generation,
and verification."
---
# Schema Markup for Next.js: A Developer's Guide
Adding structured data to your Next.js site tells search engines
exactly what your content is about. Here's how to implement JSON-LD
schema markup with the App Router...
## Why Schema Markup Matters for Next.js Sites
...
## Implementing JSON-LD in the App Router
...
## Dynamic Schema Generation
...
While this example shows Next.js, the skill works with any framework. The keyword data and content strategy come from Rampify; the implementation adapts to your stack.
Source#
View and contribute on GitHub: rampify-dev/rampify-skills