GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks "plan my content", "what should I write next", "content calendar", "content plan", "content roadmap", "editorial calendar", "what topics will rank", "find quick-win SEO topics", ...
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Content Planner?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lza6-content-planner)
---
name: content-planner
argument-hint: "<site URL or 'plan from GSC'>"
description: >
GSC-driven content calendar. Pulls real Search Console data, finds the highest
click-potential opportunities (striking-distance queries at positions 5-20,
unanswered query intent, related-keyword expansions), and produces a dated,
prioritized content calendar — ready to hand to /content-writer. Use when the
user asks "plan my content", "what should I write next", "content calendar",
"content plan", "content roadmap", "editorial calendar", "what topics will
rank", "find quick-win SEO topics", "click-potential analysis", or "schedule
my SEO content".
---
# Canonical NotFair workflow
Read [`../../seo/content-planner/SKILL.md`](../../seo/content-planner/SKILL.md) completely, then follow it as the active workflow. Resolve every relative reference from that file against `../../seo/content-planner/`.
