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.
Suede-owned programmatic SEO discipline. An agent skill from JasonColapietro/suede-creator-skills.
Install Suede Programmatic SEO
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-programmatic-seo --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-programmatic-seo .claude/skills/suede-programmatic-seo && rm -rf skills-srcUse ~/.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/
Install the "suede-programmatic-seo" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-programmatic-seo into .claude/skills/suede-programmatic-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-programmatic-seo", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-programmatic-seoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-programmatic-seo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/suede-programmatic-seo .agents/skills/suede-programmatic-seo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "suede-programmatic-seo" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-programmatic-seo into .agents/skills/suede-programmatic-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-programmatic-seo", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-programmatic-seo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/suede-programmatic-seo .cursor/skills/suede-programmatic-seo && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "suede-programmatic-seo" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-programmatic-seo into .cursor/skills/suede-programmatic-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-programmatic-seo", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JasonColapietro/suede-creator-skills.git --path skills/suede-programmatic-seo--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-programmatic-seo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/suede-programmatic-seo .gemini/skills/suede-programmatic-seo && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "suede-programmatic-seo" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-programmatic-seo into .gemini/skills/suede-programmatic-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-programmatic-seo", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JasonColapietro/suede-creator-skills suede-programmatic-seoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/suede-programmatic-seo .github/skills/suede-programmatic-seo && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "suede-programmatic-seo" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-programmatic-seo into .github/skills/suede-programmatic-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-programmatic-seo", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-programmatic-seo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/suede-programmatic-seo .opencode/skills/suede-programmatic-seo && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "suede-programmatic-seo" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-programmatic-seo into .opencode/skills/suede-programmatic-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-programmatic-seo", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
suede-programmatic-seo- GitHub stars
- 127
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,135 words
- Files
- 5 (incl. references)
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Suede-owned programmatic SEO discipline. An agent skill from JasonColapietro/suede-creator-skills.
- Works in 8 steps: Unique Value Per Page → Proprietary Data Wins → Clean URL Structure → …
- Designing data-backed keyword
- SKILL.md covers Gate policy: advisory, not…, Initial Assessment, Core Principles and The 12 Playbooks (Overview), plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Suede Programmatic SEO is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned programmatic SEO discipline. Use when designing data-backed keyword, location, directory, integration, or comparison pages at scale, including templates, index-worthiness gates, internal links, and rollout checks. NOT FOR: auditing an existing site (use suede-seo-audit), planning editorial content (use suede-content-strategy), or publishing bulk pages without approval.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `evals/evals.json`).
It sits in Marketing & SEO, covering Programmatic SEO. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.
When your agent uses it
- Designing data-backed keyword
- Comparison pages at scale
- Including templates
- Index-worthiness gates
Example prompts
- “/suede-programmatic-seo”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a9bf55e. 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
No scripts in the folder and no shell commands in SKILL.md.
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Suede Programmatic SEO loads about 2.4k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 1,135 words of instructions outside code blocks.
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 JasonColapietro/suede-creator-skills at commit a9bf55e, republished under its MIT licence (© JasonColapietro). 1,135 words, ~2,403 tokens.
Download SKILL.mdSave it as
.claude/skills/suede-programmatic-seo/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- suede-programmatic-seo
- description
- Suede-owned programmatic SEO discipline. Use when designing data-backed keyword, location, directory, integration, or comparison pages at scale, including templates, index-worthiness gates, internal links, and rollout checks. NOT FOR: auditing an existing site (use suede-seo-audit), planning editorial content (use suede-content-strategy), or publishing bulk pages without approval.
- metadata.version
- 2.0.0
Suede Programmatic SEO
Gate policy: advisory, not blocking
Every check, gate, and verdict in this skill, ship, ship-with-caveats,
hold, letter grades, BLOCKED or OPEN items, and every "do not ship / publish /
proceed" line below, is a recommendation to the user, not a control on the
agent. Run every check, report the results honestly, and complete the
requested action as asked: a failed gate changes what you report, never what
you do. Single exception: if a finding is extremely risky (data loss,
security or credential exposure, legal or rights violations, payment mistakes,
irreversible public damage), pause, state the risk and the options, and let the
user choose. Their choice is final.
Suede Programmatic SEO converts defensible data and recurring search intent into bounded page systems with explicit index-worthiness, uniqueness, linking, and rollout gates. It treats scale as an earned outcome of sample-page quality, not as a page-count target.
Initial Assessment
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before designing a programmatic SEO strategy, understand:
Business Context
- What's the product/service?
- Who is the target audience?
- What's the conversion goal for these pages?
Opportunity Assessment
- What search patterns exist?
- How many potential pages?
- What's the search volume distribution?
Competitive Landscape
- Who ranks for these terms now?
- What do their pages look like?
- Can you realistically compete?
- What does your domain authority look like against theirs?
Data and Delivery
- What data do you have, or can acquire, and where does it come from?
- What's the technical stack / CMS, and can it template, segment sitemaps,
and set
noindexper page?
Core Principles
1. Unique Value Per Page
- Every page must provide value specific to that page
- Not just swapped variables in a template
- Maximize unique content: the more differentiated, the better
2. Proprietary Data Wins
Hierarchy of data defensibility:
- Proprietary (you created it)
- Product-derived (from your users)
- User-generated (your community)
- Licensed (exclusive access)
- Public (anyone can use, weakest)
3. Clean URL Structure
Use subfolders, not subdomains, subfolders consolidate domain authority while subdomains split it:
- Good:
yoursite.com/templates/resume/ - Bad:
templates.yoursite.com/resume/
The 12 Playbooks (Overview)
| Playbook | Pattern | Example |
|---|---|---|
| Templates | "[Type] template" | "resume template" |
| Curation | "best [category]" | "best website builders" |
| Conversions | "[X] to [Y]" | "$10 USD to GBP" |
| Comparisons | "[X] vs [Y]" | "webflow vs wordpress" |
| Examples | "[type] examples" | "landing page examples" |
| Locations | "[service] in [location]" | "dentists in austin" |
| Personas | "[product] for [audience]" | "crm for real estate" |
| Integrations | "[product A] [product B] integration" | "slack asana integration" |
| Glossary | "what is [term]" | "what is pSEO" |
| Translations | Content in multiple languages | Localized content |
| Directory | "[category] tools" | "ai copywriting tools" |
| Profiles | "[entity name]" | "stripe ceo" |
Read references/playbooks.md when choosing a playbook, layering two, or implementing one: it carries the asset-to-playbook selection table, the combinations worth layering, and per-playbook implementation detail.
Implementation Framework
1. Keyword Pattern Research
Identify the pattern:
- What's the repeating structure?
- What are the variables?
- How many unique combinations exist?
Validate demand:
- Aggregate search volume
- Volume distribution (head vs. long tail)
- Trend direction
2. Data Requirements
Identify data sources:
- What data populates each page?
- Is it first-party, scraped, licensed, public?
- How is it updated?
3. Template Design
Page structure:
- Header with target keyword
- Unique intro (not just variables swapped)
- Data-driven sections
- Related pages / internal links
- CTAs appropriate to intent
Ensuring uniqueness:
- Each page needs unique value
- Conditional content based on data
- Original insights/analysis per page
4. Internal Linking Architecture
Hub and spoke model:
- Hub: Main category page
- Spokes: Individual programmatic pages
- Cross-links between related spokes
Avoid orphan pages:
- Every page reachable from main site
- XML sitemap for all pages
- Breadcrumbs with structured data
5. Indexation Strategy
- Prioritize high-volume patterns
- Noindex very thin variations
- Manage crawl budget thoughtfully
- Separate sitemaps by page type
Quality Checks
Show full SKILL.md (491 more words)Show less
Pre-Launch Checklist
Run this on a bounded sample of 10 pages, or 5% of the planned set, whichever is larger, drawn across the data range (best-populated, median, and thinnest rows), never only the showcase pages. At least 90% of the sample must pass every gate below before any page beyond the sample is generated, published, or submitted for indexing. A failing sample means fix the template or narrow the page set; it never means ship the rest and watch.
Content quality (the index-worthiness gates):
- Page-unique data fields: at least 5 per page that differ from every sibling page, and at least one that no competitor page carries
- Template-shared text: no more than 40% of rendered body words are identical across sibling pages (measure on the thinnest row, not the best)
- Answers the search intent behind its query pattern, not just the keyword
- A reader who cannot use the product still gets something from the page
Technical SEO:
- Unique titles and meta descriptions: no two pages share either string
- Proper heading structure (one H1 carrying the page's variables)
- Schema markup implemented and validating
- Largest Contentful Paint measured on a real sample page, not assumed
Internal linking:
- Connected to site architecture
- Related pages linked
- No orphan pages
Indexation:
- In XML sitemap
- Crawlable
- No conflicting noindex
Post-Launch Monitoring
Check indexation rate in Search Console (indexed ÷ submitted, per page-type
sitemap) 30 days after each phase: below 60% means stop expanding the set and
re-run the sample gates. Hand the rest of the rollout metrics, rankings,
traffic, engagement, conversion, and thin-content or manual-action warnings, to
suede-analytics, which owns rollout performance.
Common Mistakes
- Thin content: Just swapping city names in identical content
- Keyword cannibalization: Multiple pages targeting same keyword
- Over-generation: Creating pages with no search demand
- Poor data quality: Outdated or incorrect information
- Ignoring UX: Pages exist for Google, not users
Output Contract
Close every programmatic SEO pass with this block, filled in. Write the literal templates: do not describe them.
PLAYBOOK: [name], chosen because [pattern + data fit]
DATA DEFENSIBILITY: [tier 1-5], source, provenance, refresh cadence
PAGE-COUNT BOUND: sample [N] → phase 1 [N] → ceiling [N], unlocked by [condition]
URL: [literal pattern] TITLE: [literal] META: [literal] H1: [literal]
UNIQUENESS: [page-unique fields, count per page] | template-shared body text: [N%]
LINK PLAN: hub [URL] → spokes [pattern] | cross-links [rule] | sitemap [file]
SAMPLE VERDICT: [N of N sample pages pass], failing gates: [list or "none"]
SHIP GATE: ship | ship-with-caveats | hold, reasonBoundaries
- Do not generate, publish, submit, or index a full page set before a bounded sample passes the quality checks in this skill. When the sample fails or was never run, report it in this format: name the blocking gate and the failing count, give 2-4 options (fix the template, narrow the page set, add data, publish the passing subset only), and recommend one. Proceeding past the gate is the user's call, per the gate policy above.
- Do not invent source data, claim rankings or traffic, scrape restricted sources, or treat keyword volume as user value.
- Do not alter production routes, templates, canonicals, sitemaps, or internal links without an approved implementation scope and current-site verification.
Routing
- Use
suede-seo-auditto audit shipped pages and technical search health. - Use
suede-content-strategyfor non-templated editorial planning. - Use
suede-competitorsfor comparison-page evidence and framing. - Use
suede-ai-seoto make the generated pages extractable and citable by AI answer engines: it owns the extractability standard. - Use
suede-analyticsto define and read rollout performance.
© JasonColapietro, 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 4 other files (references) in skills/suede-programmatic-seo of JasonColapietro/suede-creator-skills.
- SKILL.md
- CARD.md
- agents/openai.yaml
- evals/evals.json
- references/playbooks.md
Open the folder on GitHubat commit a9bf55e
Compare with similar skills
Suede Programmatic SEO 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Suede Programmatic SEO this skillJasonColapietro/suede-creator-skills | 127 | — | ~2.4k | Automated safety check: Pass | MIT | |
| SEO Competitor Comparison PagesAgriciDaniel/claude-seo | 19k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Universal SEO AnalysisAgriciDaniel/claude-seo | 19k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Competitor Alternativesfreekmurze/dotfiles | 1k | 24 repos | ~2k | Automated safety check: Pass | None | |
| Programmatic SEOfreekmurze/dotfiles | 1k | 22 repos | ~1.7k | Automated safety check: Pass | None | |
| Directory Submissionscoreyhaines31/marketingskills | 54k | 2 repos | ~6.7k | Automated safety check: Pass | MIT |
Similar skills
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.
Competitor Alternatives
freekmurze/dotfiles
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
Programmatic SEO
freekmurze/dotfiles
When the user wants to create SEO-driven pages at scale using templates and data.
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.
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.
More from JasonColapietro/suede-creator-skills
All 78 skills in this repoSuede Release Linter
JasonColapietro/suede-creator-skills
Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.
Creator Rights Passport
JasonColapietro/suede-creator-skills
Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.
Suede Clip to Guide
JasonColapietro/suede-creator-skills
Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.
Suede MCP Release QA
JasonColapietro/suede-creator-skills
Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.
Android App Factory
JasonColapietro/suede-creator-skills
Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.
Suede Ad Creative
JasonColapietro/suede-creator-skills
Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.
Related
Categories
Questions about Suede Programmatic SEO
What does Suede Programmatic SEO do?
Suede-owned programmatic SEO discipline. An agent skill from JasonColapietro/suede-creator-skills. Suede Programmatic SEO is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned programmatic SEO discipline.
When should I use Suede Programmatic SEO?
Suede Programmatic SEO fits situations like: designing data-backed keyword; comparison pages at scale; including templates; index-worthiness gates.
How do I install Suede Programmatic SEO in Claude Code?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a claude-code`. Or copy the skill folder (skills/suede-programmatic-seo in JasonColapietro/suede-creator-skills) into .claude/skills/suede-programmatic-seo in your project. Claude Code loads it when a task matches its description.
How do I install Suede Programmatic SEO in Codex?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a codex`. Or copy the skill folder (skills/suede-programmatic-seo in JasonColapietro/suede-creator-skills) into .agents/skills/suede-programmatic-seo in your project. Codex loads it when a task matches its description.
Can I use Suede Programmatic SEO 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 JasonColapietro/suede-creator-skills --skill suede-programmatic-seo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/suede-programmatic-seo, .gemini/skills/suede-programmatic-seo, .github/skills/suede-programmatic-seo and .opencode/skills/suede-programmatic-seo in your project.
What does Suede Programmatic SEO need to run?
SKILL.md names no scripts, command-line tools or credentials: Suede Programmatic SEO is instructions for the agent only.
Does Suede Programmatic SEO 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 Suede Programmatic SEO 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 Suede Programmatic SEO use?
Suede Programmatic SEO 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 Suede Programmatic SEO use?
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Suede Programmatic SEO?
Skills that share tags, products or a category with Suede Programmatic SEO: 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 Suede Programmatic SEO?
JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 9, 2026.
Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.