Agent skill

Programmatic SEO Planner

by gooseworks-ai in gooseworks-ai/goose-skills

Identify programmatic SEO page patterns worth building for your product — vs/ pages, integrations/, for-{industry}/, alternatives-to/, use-cases/ — and design the template structure, data model, and…

MITAuto-check passedMarketing & SEO

Install Programmatic SEO Planner

skills CLI
$ npx skills add gooseworks-ai/goose-skills --skill programmatic-seo-planner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gooseworks-ai/goose-skills programmatic-seo-planner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo/composites/programmatic-seo-planner .claude/skills/programmatic-seo-planner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
programmatic-seo-planner
GitHub stars
1.2k
Used in
1 other repo
Token cost
~3.3k tokens
SKILL.md length
1,224 words
Files
2
Skills in repo
273
Repo updated
First seen
Licence
MIT

At a glance

Identify programmatic SEO page patterns worth building for your product — vs/ pages, integrations/, for-{industry}/, alternatives-to/, use-cases/ — and design the template structure, data model, and…

  • Works in 6 steps: Intake → Pattern Discovery → Pattern Evaluation → …
  • Tasks that involve Programmatic SEO
  • SKILL.md covers When to Use, Tool Enhancement (Optional), Phase 0: Intake and Phase 1: Pattern Discovery, plus 7 more sections
  • Calls python3; needs DATAFORSEO_PASSWORD and KEYWORDS_EVERYWHERE_API_KEY

What it does

Programmatic SEO Planner is an agent skill from gooseworks-ai/goose-skills. Identify programmatic SEO page patterns worth building for your product — vs/ pages, integrations/, for-{industry}/, alternatives-to/, use-cases/ — and design the template structure, data model, and priority order. Outputs a complete pSEO blueprint with URL patterns, title templates, content frameworks, and data sources per variable.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).

It sits in Marketing & SEO, covering Programmatic SEO. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.

When your agent uses it

  • Tasks that involve Programmatic SEO

Example prompts

  • “/programmatic-seo-planner”

Requirements

  • Python 3
  • A credential in KEYWORDS_EVERYWHERE_API_KEY
  • A credential in SEMRUSH_API_KEY

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Intake
  2. Pattern Discovery
  3. Pattern Evaluation
  4. Template Design
  5. Prioritization & Roadmap
  6. Output

What it can do on your machine

Read from SKILL.md and the folder at commit c650c6d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • DATAFORSEO_PASSWORD
    • KEYWORDS_EVERYWHERE_API_KEY
    • SEMRUSH_API_KEY
    • AHREFS_API_TOKEN
    • APIFY_API_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Programmatic SEO Planner loads about 3.3k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 1,224 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 1,224 words, ~3,339 tokens.

Download SKILL.mdSave it as .claude/skills/programmatic-seo-planner/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
programmatic-seo-planner
description
Identify programmatic SEO page patterns worth building for your product — vs/ pages, integrations/, for-{industry}/, alternatives-to/, use-cases/ — and design the template structure, data model, and priority order. Outputs a complete pSEO blueprint with URL patterns, title templates, content frameworks, and data sources per variable.
tags
seo

Programmatic SEO Page Planner

Programmatic SEO is how startups generate hundreds of high-intent pages from templates — "{Your Product} vs {Competitor}", "Best {Category} for {Industry}", "{Integration} + {Your Product}". This skill figures out which patterns are worth building, designs the templates, and prioritizes the buildout.

Core principle: pSEO isn't about spinning content. It's about finding a data axis (something that varies per page) where each variation has real search demand and your product has a genuine answer. This skill validates both before you invest in building.

When to Use

  • "How do we scale SEO pages without writing each one manually?"
  • "Should we build vs/ comparison pages?"
  • "What programmatic SEO patterns work for SaaS?"
  • "How can we rank for hundreds of long-tail keywords?"
  • "Plan our pSEO strategy"

Tool Enhancement (Optional)

This skill works with existing capabilities but produces significantly better results when paired with a keyword data API for bulk volume lookups across hundreds of long-tail variations.

Agent Prompt to User

"I can plan your programmatic SEO strategy using our existing tools. However, for the best results — especially accurate search volume data across hundreds of keyword variations — I'd recommend connecting a keyword data API."

Recommended: DataForSEO (pay-per-use, ~$0.01/keyword, no monthly minimum)

  • Sign up at dataforseo.com → get API login + password
  • Set DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD env vars

Alternatives that also work:

  • Keywords Everywhere API ($1 per 10 credits = 100K keywords, very cheap) → set KEYWORDS_EVERYWHERE_API_KEY
  • SEMrush API (if you have a subscription) → set SEMRUSH_API_KEY
  • Ahrefs API (if you have a subscription) → set AHREFS_API_TOKEN

"Want to use one of these, or should I proceed with baseline mode? Baseline still works — I'll use our Apify-based SEO tools for top-level data, though volume estimates for individual long-tail patterns will be less precise."

Mode Selection
  • Enhanced mode — Bulk keyword volume lookups via DataForSEO / Keywords Everywhere / SEMrush / Ahrefs. Gets exact monthly search volume, keyword difficulty, and CPC for each pattern variation. Enables confident prioritization.
  • Baseline mode — Uses seo-domain-analyzer (Apify) for domain-level metrics and web_search for pattern validation. Volume estimates are directional, not exact. Still produces a solid blueprint — just less granular on per-variation demand.

Phase 0: Intake

  1. Your product — URL + one-sentence description
  2. Category — What category/market do you play in?
  3. Competitors — 3-5 competitor URLs (we'll analyze their pSEO plays)
  4. ICP — Who's searching for your product? (roles, industries, company stages)
  5. Existing content — Do you already have a blog/resource section? (URL if yes)
  6. CMS/tech stack — What powers your site? (Webflow, WordPress, Next.js, etc.) — informs template feasibility
  7. Tool preference — Enhanced mode with keyword API, or baseline? (see Tool Enhancement above)

Phase 1: Pattern Discovery

1A: Competitor pSEO Analysis

Run site-content-catalog for each competitor:

bash
python3 skills/site-content-catalog/scripts/catalog_content.py \
  --url "<competitor_url>" \
  --output json

Analyze URL structures for programmatic patterns:

  • /vs/, /compare/, /alternatives/ — Comparison pages
  • /integrations/, /connect/, /apps/ — Integration pages
  • /for-{industry}/, /solutions/, /use-cases/ — Vertical/use-case pages
  • /templates/, /examples/, /glossary/ — Resource pages
  • /tools/, /calculators/, /generators/ — Tool pages

For each pattern found, note:

  • URL pattern (regex)
  • Estimated page count
  • What varies per page (the "data axis")
  • Sample page titles
1B: Market Pattern Mapping

Based on your product category, evaluate these standard pSEO pattern types:

Pattern TypeURL StructureData AxisBest For
Versus/Comparison/vs/{competitor}Competitor namesHigh-intent, bottom-funnel
Alternatives/alternatives/{competitor}Competitor namesDisplacement queries
Integrations/integrations/{tool}Tool/app namesMid-funnel, ecosystem
Industry verticals/for/{industry}Industry namesVertical targeting
Use cases/use-cases/{use-case}Job-to-be-doneMid-funnel, discovery
Glossary/Definitions/glossary/{term}Industry termsTop-funnel, authority
Templates/Examples/templates/{type}Template typesMid-funnel, utility
Tools/Calculators/tools/{tool-name}Tool functionsTop-funnel, link bait
Location pages/{service}-in-{city}City/region namesLocal-intent (if relevant)
1C: Customer Language Mining

Run reddit-post-finder to find how ICP talks about the problem:

bash
python3 skills/reddit-post-finder/scripts/search_reddit.py \
  --subreddit "<relevant_subs>" \
  --keywords "<category>,<problem keyword>" \
  --days 365 --sort top --time year

Extract:

  • Questions people ask → potential glossary/guide patterns
  • "How do I [X] with [tool]?" → integration/use-case patterns
  • "Is there a [X] for [industry]?" → vertical page patterns
  • Comparison discussions → vs/ page patterns
1D: Keyword Volume Validation

Enhanced mode (DataForSEO / Keywords Everywhere / SEMrush / Ahrefs):

For each candidate pattern, generate 20-50 keyword variations and pull exact volumes:

  • "your-product vs {competitor1}", "your-product vs {competitor2}", etc.
  • "best {category} for {industry1}", "best {category} for {industry2}", etc.
  • "{your-product} {integration1} integration", etc.

Aggregate per pattern type:

  • Total addressable monthly searches across all variations
  • Average volume per variation
  • Volume distribution (are a few variations high-volume or is it evenly spread?)
  • Average keyword difficulty

Baseline mode:

Use seo-domain-analyzer for competitor domain metrics, web_search to spot-check if key variations have SERP results (indicating real demand), and manual estimation based on:

  • Competitor page count per pattern (more pages = likely more demand)
  • Google autocomplete suggestions for pattern variations
  • Reddit/community question frequency
Show full SKILL.md (496 more words)Show less

Phase 2: Pattern Evaluation

Score each candidate pattern on:

FactorWeightHow to Assess
Search demand30%Total addressable volume across all variations
Intent quality25%How close to purchase decision? (vs/ = high, glossary = low)
Template feasibility20%Can you create a useful, differentiated page from a template?
Data availability15%Can you programmatically source the data that varies?
Competitive gap10%Are competitors NOT doing this pattern, or doing it poorly?

Score each pattern 0-100. Rank by score.

Feasibility Check Per Pattern

For each pattern scoring 50+, validate:

  1. Data source — Where does the variable data come from?

    • Competitor names → manual list (finite, high-value)
    • Integration/tool names → API marketplace, app directory
    • Industry names → standard industry lists
    • Terms/glossary → keyword research output
    • Templates → product feature matrix
  2. Content differentiation — Can each page offer genuine value, or will they be thin?

    • vs/ pages need real feature comparisons, not just "we're better"
    • Integration pages need actual setup guides or use cases
    • Vertical pages need industry-specific pain points and examples
  3. Technical feasibility — Can your CMS generate these at scale?

    • Static site generators (Next.js, Astro) → excellent for pSEO
    • Webflow CMS → good, max 10K items per collection
    • WordPress → good with custom post types
    • Manual creation → not pSEO, just a lot of pages

Phase 3: Template Design

For each pattern being built, design:

Template Blueprint
markdown
## Pattern: [vs/{competitor}]

### URL Structure
/vs/{competitor-slug}

### Title Template
{Your Product} vs {Competitor} — [Year] Comparison | {Your Brand}

### Meta Description Template
Compare {Your Product} and {Competitor} side-by-side. See pricing, features,
pros/cons, and which is better for {ICP description}.

### H1
{Your Product} vs {Competitor}: Honest Comparison

### Page Sections (content framework)
1. **TL;DR** — 3-sentence summary of key differences (above fold)
2. **Quick comparison table** — Feature matrix with checkmarks
3. **Detailed comparison** — 4-6 key dimensions, 2-3 paragraphs each
4. **Pricing comparison** — Plan-by-plan breakdown
5. **Who should choose {Your Product}** — ICP fit description
6. **Who should choose {Competitor}** — Fair assessment
7. **What real users say** — Review quotes from both sides
8. **CTA** — Trial/demo prompt

### Data Required Per Page
- competitor_name: string
- competitor_slug: string
- competitor_features: array (from their website/docs)
- competitor_pricing: object (from pricing page)
- competitor_reviews: array (from G2/Capterra)
- your_differentiators: array (per competitor)

### Content Guidelines
- Minimum 1,500 words per page
- Must include at least one unique insight (not just feature lists)
- Use actual screenshots or diagrams where possible
- Update quarterly (pricing/features change)

Repeat for each pattern type.

Phase 4: Prioritization & Roadmap

Build the implementation plan:

Priority Matrix
PatternScoreEst. PagesVolume/PageTotal VolumeBuild EffortPriority
vs/ comparisons85153004,500MediumP0 — Build first
integrations/7240803,200HighP1 — Build second
for-{industry}/68122002,400MediumP1 — Build second
alternatives-to/6582502,000LowP0 — Quick win
glossary/45100404,000LowP2 — Authority play

Month 1: Quick wins

  • Build [pattern A] — [X] pages, [rationale]
  • Build [pattern B] — [X] pages, [rationale]

Month 2: Scale

  • Build [pattern C] — [X] pages, [rationale]
  • Measure Month 1 patterns, iterate templates

Month 3: Expand

  • Build [pattern D] — [X] pages, [rationale]
  • Update Month 1 pages with performance data
Per-Pattern Data Source Plan

For each pattern, specify exactly where the variable data comes from:

  • Manual curation (competitors list — finite, high quality)
  • API source (integration marketplace)
  • Scraping (review sites, competitor pages)
  • Internal data (product features, pricing)

Phase 5: Output

markdown
# Programmatic SEO Blueprint — [Product Name] — [DATE]

## Executive Summary
- [N] patterns evaluated, [M] recommended for buildout
- Total addressable search volume: [X]/month
- Estimated pages to build: [Y]
- Recommended buildout timeline: [Z] months

---

## Pattern Analysis (ranked by priority)

### P0: [Pattern Name]
- URL structure: [pattern]
- Pages to build: [N]
- Total monthly volume: [X]
- Template blueprint: [see below]
- Data source: [where variable data comes from]
- Build effort: [Low/Medium/High]
- Expected time to rank: [2-4 months / 4-8 months / etc.]

[Full template blueprint per Phase 3]

### P1: [Pattern Name]
...

---

## Technical Requirements
- CMS: [capabilities needed]
- Data pipeline: [how to source variable data]
- Update cadence: [how often to refresh]

---

## Quick-Start Guide
1. Start with [pattern] — lowest effort, highest intent
2. Create [N] pages using the template above
3. Monitor for [X] weeks before expanding
4. ...

Save to the current working directory or wherever the user prefers.

Cost

ComponentCost
Site catalog per competitor (Apify)~$0.05-0.10
Reddit scraper~$0.05-0.10
SEO domain analyzer~$0.10-0.20
DataForSEO keyword lookups (enhanced)~$0.50-2.00 (depending on variation count)
Keywords Everywhere (enhanced alt)~$0.01-0.05
AnalysisFree (LLM reasoning)
Total (baseline)~$0.20-0.50
Total (enhanced)~$0.70-2.50

Tools Required

  • Apify API token — APIFY_API_TOKEN env var
  • Upstream skills: site-content-catalog, seo-domain-analyzer, reddit-post-finder
  • Optional (enhanced): DataForSEO (DATAFORSEO_LOGIN + DATAFORSEO_PASSWORD), Keywords Everywhere (KEYWORDS_EVERYWHERE_API_KEY), SEMrush (SEMRUSH_API_KEY), or Ahrefs (AHREFS_API_TOKEN)

Trigger Phrases

  • "Plan our programmatic SEO strategy"
  • "What pSEO pages should we build?"
  • "Design vs/ comparison pages for our product"
  • "How do we scale to hundreds of SEO pages?"
  • "Build a pSEO blueprint for [client]"
  • "What programmatic patterns should we use?"

© gooseworks-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/seo/composites/programmatic-seo-planner of gooseworks-ai/goose-skills.

  • SKILL.md
  • skill.meta.json

Open the folder on GitHubat commit c650c6d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Programmatic SEO Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Programmatic SEO Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Programmatic SEO Planner this skillgooseworks-ai/goose-skills1.2k1 repos~3.3kAutomated safety check: PassMIT
SEO Competitor Comparison PagesAgriciDaniel/claude-seo19k5 repos~1.9kAutomated safety check: PassMIT
Universal SEO AnalysisAgriciDaniel/claude-seo19k—~4.9kAutomated safety check: PassMIT
Competitor Alternativesfreekmurze/dotfiles1k24 repos~2kAutomated safety check: PassNone
Programmatic SEOfreekmurze/dotfiles1k22 repos~1.7kAutomated safety check: PassNone
Directory Submissionscoreyhaines31/marketingskills54k2 repos~6.7kAutomated safety check: PassMIT

Similar skills

  • SEO Competitor Comparison Pages

    AgriciDaniel/claude-seo

    Generates X vs Y comparison pages, alternatives-to-X pages, best-tools roundups and feature-matrix tables, with schema markup and verifiable data rules.

    19k GitHub starsUsed in 5 repos~1.9k tokens
    Marketing & SEOAuto-check passed
  • Universal SEO Analysis

    AgriciDaniel/claude-seo

    Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.

    19k GitHub stars~4.9k tokensUpdated 6 days ago
    Marketing & SEOAuto-check passed
  • Competitor Alternatives

    freekmurze/dotfiles

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.

    1k GitHub starsUsed in 24 repos~2k tokens
    Marketing & SEOAuto-check passed
  • Programmatic SEO

    freekmurze/dotfiles

    When the user wants to create SEO-driven pages at scale using templates and data.

    1k GitHub starsUsed in 22 repos~1.7k tokens
    Marketing & SEOAuto-check passed
  • Directory Submissions

    coreyhaines31/marketingskills

    When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.

    54k GitHub starsUsed in 2 repos~6.7k tokens
    Marketing & SEOAuto-check passed
  • Global SEO Growth

    minhnv0807/ai-business-skills

    Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.

    609 GitHub stars~5k tokensUpdated 28 days ago
    Marketing & SEOAuto-check passed

More from gooseworks-ai/goose-skills

All 273 skills in this repo
  • Reddit Post Finder

    gooseworks-ai/goose-skills

    Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Create Image Fal

    gooseworks-ai/goose-skills

    Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.

    1.2k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Render Hook Replacement

    gooseworks-ai/goose-skills

    Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.

    1.2k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Blog Feed Monitor

    gooseworks-ai/goose-skills

    Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.

    1.2k GitHub starsUsed in 1 repo~578 tokens
    Auto-check passed
  • Competitor Post Engagers

    gooseworks-ai/goose-skills

    Find leads by scraping engagers from a competitor's top LinkedIn posts.

    1.2k GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check: notes
  • Render Chatgpt Chat

    gooseworks-ai/goose-skills

    Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…

    1.2k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Categories

Questions about Programmatic SEO Planner

What does Programmatic SEO Planner do?

Identify programmatic SEO page patterns worth building for your product — vs/ pages, integrations/, for-{industry}/, alternatives-to/, use-cases/ — and design the template structure, data model, and…. Programmatic SEO Planner is an agent skill from gooseworks-ai/goose-skills. Identify programmatic SEO page patterns worth building for your product — vs/ pages, integrations/, for-{industry}/, alternatives-to/, use-cases/ — and design the template structure, data model, and priority order.

When should I use Programmatic SEO Planner?

Programmatic SEO Planner fits situations like: tasks that involve Programmatic SEO.

How do I install Programmatic SEO Planner in Claude Code?

Run `npx skills add gooseworks-ai/goose-skills --skill programmatic-seo-planner -a claude-code`. Or copy the skill folder (skills/seo/composites/programmatic-seo-planner in gooseworks-ai/goose-skills) into .claude/skills/programmatic-seo-planner in your project. Claude Code loads it when a task matches its description.

How do I install Programmatic SEO Planner in Codex?

Run `npx skills add gooseworks-ai/goose-skills --skill programmatic-seo-planner -a codex`. Or copy the skill folder (skills/seo/composites/programmatic-seo-planner in gooseworks-ai/goose-skills) into .agents/skills/programmatic-seo-planner in your project. Codex loads it when a task matches its description.

Can I use Programmatic SEO Planner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gooseworks-ai/goose-skills --skill programmatic-seo-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/programmatic-seo-planner, .gemini/skills/programmatic-seo-planner, .github/skills/programmatic-seo-planner and .opencode/skills/programmatic-seo-planner in your project.

What does Programmatic SEO Planner need to run?

Going by SKILL.md and its folder, Programmatic SEO Planner needs the command-line tools its instructions call (python3) and credentials named DATAFORSEO_PASSWORD, KEYWORDS_EVERYWHERE_API_KEY, SEMRUSH_API_KEY and AHREFS_API_TOKEN. Our summary lists: Python 3; A credential in KEYWORDS_EVERYWHERE_API_KEY; A credential in SEMRUSH_API_KEY.

Does Programmatic SEO Planner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Programmatic SEO Planner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Programmatic SEO Planner use?

Programmatic SEO Planner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Programmatic SEO Planner use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Programmatic SEO Planner?

Skills that share tags, products or a category with Programmatic SEO Planner: SEO Competitor Comparison Pages (AgriciDaniel/claude-seo, 19k stars), Universal SEO Analysis (AgriciDaniel/claude-seo, 19k stars), Competitor Alternatives (freekmurze/dotfiles, 1k stars) and Programmatic SEO (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Programmatic SEO Planner?

gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.

Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.