Installation

1. 1
   Make sure Claude is on your device and in your terminal.

   Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

   One-time setup

   Copy

   npm i -g @anthropic-ai/claude-code

   Already have it? Skip ahead.

2. 2
   Paste into Claude Code or into your terminal.

   Install

   Sign up to copy

   git clone ht••••••••••••••••••••••••••••••••••••••••••••••••• •••••••••••••••••••••••••••••••••• •• ••••• •• •••••••••••••••••••••••••••••••••••••••••••••• •• •• •• ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• •••••••••••••••••••••••••••••••••••••••••••••••

   Sign up free to reveal

   This copies the whole skill folder into ~/.claude/skills/content-planner-nowork-studio/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

   Faster alternative (instruction-only skills)

   Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

   Quick install (SKILL.md only)

   Sign up to copy

   mkdir -p ~/.••••••••••••••••••••••••••••••••••••••••••• •• •••• ••••• ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• •• •••••••••••••••••••••••••••••••••••••••••••••••••••••••

   Sign up free to reveal
3. 3
   Restart Claude Code.

   Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

4. 4
   Just ask Claude.

   Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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

What this skill does