content-planner

Featured

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".

Data & Documents 3,283 stars 406 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Content Planner You are NotFair's content strategist for the unfair SEO/Ads agent. Your job is **not** to brainstorm topic ideas — that's `keyword-research`. Your job is to mine the user's *actual* Search Console data, find the highest-click-potential opportunities for *this* site, and produce a dated calendar the user can publish against. The output is a structured `content-calendar.json` plus a Markdown summary. The JSON is consumed by the `notfair-content-calendar` viewer (a local server that renders the calendar in the browser). **Boundary with sibling skills:** - `keyword-research` — start from a seed, discover the keyword universe - `content-planner` (this skill) — start from GSC, prioritize *your* opportunities, schedule them - `content-writer` — take one planned topic and write the full post --- ## Step 1 — Setup (config + GSC) Read and follow `../seo-analysis/SKILL.md` Step 1 for GSC connection. The planner cannot run without GSC — if no GSC property is connected, **stop and walk the user through OAuth**. Don't invent data. Resolve `{data_dir}` the same way the Google Ads preamble does (`.notfair/` in the repo if `.notfair.json` exists, else `~/.notfair/`). The calendar lives at `{data_dir}/content-calendar.json`. --- ## Step 2 — Pull GSC opportunity data Pull a wide net once, filter in memory. Fewer round-trips, better correlation. For the chosen GSC property, fetch **last 90 days** of: 1. **Query × Page** report — top 5000 rows. The Cartesian view is ...

Details

Author
nowork-studio
Repository
nowork-studio/NotFair
Created
4 months ago
Last Updated
4 days ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

content-calendar

Use to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from strategy and pillars. Run when the user says "content calendar," "editorial calendar," "social media calendar," "posting schedule," "content plan" (ongoing), "what should I post each week," "build me a posting routine/cadence," or wants a repeatable system rather than one period's posts. Reads social-strategy, content-pillars, and brand-profile first; sizes cadence to real capacity; builds a recurring skeleton of buckets and named series with room reserved for reactive/trend content; sets the planning rhythm (batch, buffer, review). Hands a period's briefs to batch-content-plan, content to the writing skills, and scheduling to scheduling-and-queue. For filling one specific week/month with actual posts use batch-content-plan; for higher-level channel/goal choices use social-strategy.

5 Updated 3 days ago
social-media-skills
AI & Automation Featured

content-calendar

Plan content calendars. Use when: monthly or quarterly scheduling, platform assignments, content pillars, repurposing.

636 Updated 1 weeks ago
indranilbanerjee
AI & Automation Listed

aeo-llm-content-planner

Produce a prioritized 90-day AEO/SEO content roadmap by consuming outputs from LLM Citation Audit (#4), Entity & Topical Authority Mapper (#5), and Competitor Content Gap Analysis (#12), deduplicating and merging related opportunities, identifying dependencies between work items, and sequencing the resulting deliverables across a calendar that respects team capacity. The output is a single integrated view that replaces three or four separate opportunity lists with no shared timeline. Use this skill whenever a user asks for a content calendar, content roadmap, quarterly content plan, 90-day plan, Q1/Q2/Q3/Q4 planning, content strategy sequencing, how to prioritize AEO work, or when multiple audit skills have been run and the user needs a unified execution plan. Chains with brand-kit.md (team, capacity, tone), llm-citation-audit.md (failure-mode-classified prompts), entity-topical-map.md (topic tree and Publish/Earn/Integrate actions), competitor-content-gap.md (content/quality/intent opportunities), and option

0 Updated 2 days ago
search-atlas-group