Hreflang and International SEO
AgriciDaniel/claude-seo
Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.
Plan, manage, and optimize a domain portfolio. An agent skill from rampstackco/claude-skills.
Install Domain Strategy
$ npx skills add rampstackco/claude-skills --skill domain-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rampstackco/claude-skills domain-strategy --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/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/domain-strategy .claude/skills/domain-strategy && 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 "domain-strategy" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/domain-strategy into .claude/skills/domain-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-strategy", 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/rampstackco/claude-skills/tree/main/skills/domain-strategyType 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 rampstackco/claude-skills --skill domain-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rampstackco/claude-skills domain-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/domain-strategy .agents/skills/domain-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "domain-strategy" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/domain-strategy into .agents/skills/domain-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-strategy", 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 rampstackco/claude-skills --skill domain-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rampstackco/claude-skills domain-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/domain-strategy .cursor/skills/domain-strategy && 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 "domain-strategy" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/domain-strategy into .cursor/skills/domain-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-strategy", 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/rampstackco/claude-skills.git --path skills/domain-strategy--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 rampstackco/claude-skills --skill domain-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rampstackco/claude-skills domain-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/domain-strategy .gemini/skills/domain-strategy && 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 "domain-strategy" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/domain-strategy into .gemini/skills/domain-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-strategy", 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 rampstackco/claude-skills domain-strategyInstalls 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 rampstackco/claude-skills --skill domain-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/domain-strategy .github/skills/domain-strategy && 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 "domain-strategy" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/domain-strategy into .github/skills/domain-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-strategy", 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 rampstackco/claude-skills --skill domain-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rampstackco/claude-skills domain-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/domain-strategy .opencode/skills/domain-strategy && 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 "domain-strategy" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/domain-strategy into .opencode/skills/domain-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-strategy", 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
domain-strategy- GitHub stars
- 935
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,142 words
- Files
- 3 (incl. references)
- Skills in repo
- 103
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan, manage, and optimize a domain portfolio. An agent skill from rampstackco/claude-skills.
- Works in 7 steps: Inventory → Classify by role → Audit current configuration → …
- DNS architecture decisions
- SKILL.md covers When to use, When NOT to use, Required inputs and The framework: 5 decisions, plus 4 more sections
- Calls curl
What it does
Domain Strategy is an agent skill from rampstackco/claude-skills. Plan, manage, and optimize a domain portfolio. Use this skill for DNS architecture decisions, redirect strategies, registrar choice, parking unused domains, multi-site setups, and domain consolidation or split planning. Triggers on DNS, domain, registrar, redirect, parking, subdomain, apex, www vs non-www, multi-site, portfolio, hreflang setup, domain migration. Also triggers when planning a new site that needs domain decisions made before launch.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `README.md` and `references/dns-record-reference.md`).
It sits in Marketing & SEO, covering Technical SEO. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.
When your agent uses it
- DNS architecture decisions
- Redirect strategies
- Registrar choice
- Parking unused domains
Example prompts
- “/domain-strategy”
Workflow steps
7 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 482c9bf. 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:
curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
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
Domain Strategy loads about 2.2k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 1,142 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 rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 1,142 words, ~2,200 tokens.
Download SKILL.mdSave it as
.claude/skills/domain-strategy/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- domain-strategy
- description
- Plan, manage, and optimize a domain portfolio. Use this skill for DNS architecture decisions, redirect strategies, registrar choice, parking unused domains, multi-site setups, and domain consolidation or split planning. Triggers on DNS, domain, registrar, redirect, parking, subdomain, apex, www vs non-www, multi-site, portfolio, hreflang setup, domain migration. Also triggers when planning a new site that needs domain decisions made before launch.
- category
- operations
- catalog_summary
- DNS architecture, redirects, registrars, multi-domain portfolios
- display_order
- 4
Domain Strategy
Decide how domains, subdomains, and DNS work across a portfolio. Stack-agnostic. Works for one site or one hundred.
When to use
- Setting up DNS for a new site (apex vs www, primary vs aliases)
- Choosing or switching registrars
- Planning redirects across multiple domains (parked, retired, consolidated)
- Deciding subdomain vs subfolder vs separate domain for a new product line
- Consolidating multiple sites into one
- Splitting one site into multiple
- Setting up DNS for email, security records, third-party services
When NOT to use
- Migrating content between platforms with URL changes (use
content-migration) - Email authentication setup specifically (use
email-deliverability) - Security headers or HTTPS config (use
security-baseline) - Internationalization domain choices (use
internationalization)
Required inputs
- Current domain inventory (every domain you own or operate)
- Status of each (live, parked, redirected, retired)
- Strategic role of each (primary brand, sub-brand, defensive registration, campaign)
- Current DNS provider and registrar for each
- Email and third-party service dependencies
The framework: 5 decisions
Every domain decision falls into one of these buckets. Address them in order.
Decision 1: Apex vs www as canonical
Pick one. Redirect the other to it. Pick before launch. Changing later is painful.
- Apex (example.com): cleaner, more memorable, the modern default.
- www (www.example.com): historically standard, easier to add CDN-level CNAME records (apex CNAME is technically forbidden but most providers offer ALIAS or ANAME).
Whichever you pick, the other must 301 to it. Both serving content is duplicate content and a soft signal of poor setup.
Decision 2: Subdomain vs subfolder vs separate domain
For a new product, blog, or content section:
| Pattern | Use when |
|---|---|
Subfolder (example.com/blog) | Same brand, want SEO equity to flow, default choice |
Subdomain (blog.example.com) | Different stack or platform, organizationally separate but related |
Separate domain (exampleblog.com) | Different brand, different audience, intentional separation |
Default to subfolder. The case for subdomain or separate domain has to be made.
Decision 3: Registrar strategy
The registrar is where the domain is registered. The DNS provider is where DNS records live. They can be the same or different.
Decisions:
- Single registrar vs multiple: single is simpler. Multiple makes sense for redundancy at scale.
- Lock and 2FA: non-negotiable. Domain hijacking is real and costly.
- Auto-renew: on for everything you care about. Off only for intentional drops.
- WHOIS privacy: on by default. Free at most modern registrars.
- Transfer lock: on except during planned transfers.
Decision 4: DNS provider
The DNS provider controls how domains resolve. Critical for performance, reliability, and security.
Pick a provider that gives you:
- Fast global resolution (anycast network)
- DNSSEC support
- API access for automation
- Reasonable record limits
- Good audit logs
Default DNS records every domain needs:
- A or AAAA records (or CNAME) for the apex and www
- MX records (even just nullified if no email)
- TXT for domain verification, SPF
- CAA records (locks down which certificate authorities can issue certs for the domain)
Decision 5: Parked domain strategy
Domains you own but aren't actively using. Three valid strategies:
- Redirect to a primary site. Best for defensively registered domains close to your main brand. 301 every path to the primary's homepage or matching path.
- Hold blank. A simple page or DNS NXDOMAIN. Acceptable for domains you may use later.
- Park with a landing page. Generic "coming soon" page. Lowest value. Avoid registrar default parking pages (often serve ads against your brand).
Anti-pattern: letting parked domains serve duplicate or near-duplicate content from your main site. This is an SEO liability.
Workflow
Step 1: Inventory
Pull every domain you own from every registrar. Build a single sheet:
| Domain | Registrar | DNS provider | Status | Role | Renewal date | Notes |
|---|
If you can't account for every domain, the strategy can't be accurate.
Step 2: Classify by role
Each domain gets one role:
- Primary (the main site for a brand)
- Alias (redirects to a primary)
- Defensive (registered to prevent others from getting it; usually parked)
- Campaign (short-term, specific use)
- Retired (no longer active; either drop at expiry or redirect permanently)
The classification drives the configuration.
Step 3: Audit current configuration
For each domain check:
- Is the canonical (apex vs www) consistent with the strategy?
- Are redirects 301 (permanent) where intended?
- Is HTTPS enforced on every variant?
- Are DNS records minimal and intentional?
- Is the registrar locked?
- Is auto-renew on?
- Is 2FA on the registrar account?
Document gaps. Each gap is a ticket.
Show full SKILL.md (431 more words)Show less
Step 4: Set the canonical pattern
For new domains and any that need fixing:
- Pick apex or www as canonical
- Configure 301 redirect for the non-canonical
- Force HTTPS for both
- Verify with curl:
curl -I http://example.com,curl -I http://www.example.com,curl -I https://www.example.com. All should chain to a single 200 on the canonical.
Step 5: Document the redirect map
Across the portfolio, document every redirect:
| Source | Destination | Type | Reason | Date set |
|---|
This is invaluable when something breaks or when planning consolidations.
Step 6: Set up monitoring
Monitor:
- DNS resolution (alert on NXDOMAIN or wrong IP)
- HTTPS certificate expiration (alert at 30, 14, 7 days out)
- Redirect chains (alert if a 301 starts returning 200 or 404)
- Renewal dates (alert at 90, 30, 7 days out)
This is the bridge between domain strategy and monitoring-and-alerting.
Step 7: Document and revisit
Domain strategy is a quarterly review topic. Renewals, consolidations, and new launches change the picture. Without scheduled review, the portfolio drifts.
Failure patterns
Both apex and www serve content. Duplicate content. Pick one, redirect the other.
302 redirects where 301 was intended. 302 is temporary. 301 is permanent. SEO equity passes through 301, not (reliably) through 302.
HTTPS not enforced. HTTP variant serving content alongside HTTPS. Force HTTPS at the edge or the load balancer.
Registrar default parking pages. Parked domains serving registrar ads. Free for the registrar, bad for you. Replace with a redirect or your own page.
Domains in multiple registrars by accident. Migrations that didn't fully complete. Consolidate.
No CAA records. Anyone with a misconfigured ACME client can issue a cert for your domain. CAA limits which CAs can issue. Add it.
Auto-renew off "to save money." Domain accidentally drops, gets snapped up, costs ten times more (or is unrecoverable). Auto-renew is cheap insurance.
Subdomains used where subfolders would have been better. SEO equity gets fragmented across hostnames. The case for a subdomain has to be made; the default is subfolder.
Parked domains with thin content "for SEO." Search engines don't reward this. They penalize doorway pages. Either redirect or leave blank.
Output format
A domain strategy document includes:
- Inventory: the spreadsheet of every domain
- Classification: the role of each
- Canonical decisions: apex vs www, locked
- Redirect map: every redirect in the portfolio
- DNS standards: the default record set
- Registrar standards: locked, 2FA, auto-renew
- Monitoring: what's watched, where alerts go
- Renewal calendar: the next 12 months
- Review cadence: when this gets revisited
Reference files
references/dns-record-reference.md: Common DNS records explained, with the syntax for the most useful ones (A, AAAA, CNAME, MX, TXT, CAA, SRV, etc.) and when each is needed.
© rampstackco, 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 2 other files (references) in skills/domain-strategy of rampstackco/claude-skills.
- SKILL.md
- README.md
- references/dns-record-reference.md
Open the folder on GitHubat commit 482c9bf
Compare with similar skills
Domain Strategy 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 |
|---|---|---|---|---|---|---|
| Domain Strategy this skillrampstackco/claude-skills | 935 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Hreflang and International SEOAgriciDaniel/claude-seo | 18k | 5 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Google SEO APIsAgriciDaniel/claude-seo | 18k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude | 11k | — | ~2.8k | Automated safety check: Notes | MIT | |
| SEO Audit with Search Consolenowork-studio/notfair-plugin | 3.9k | 1 repos | ~15k | Automated safety check: Warn | MIT | |
| SEO Drift MonitorAgriciDaniel/claude-seo | 18k | 1 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Google SEO APIs
AgriciDaniel/claude-seo
Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.
GEO-First SEO Audit Tool
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
SEO Audit with Search Console
nowork-studio/notfair-plugin
Runs a full SEO audit that combines Google Search Console, URL Inspection, PageSpeed Insights and a technical crawl, then ranks quick wins and a 30-day plan.
SEO Drift Monitor
AgriciDaniel/claude-seo
Captures baselines of a page's SEO-critical elements, compares later snapshots against them and flags regressions by severity, like version control for on-page SEO.
Broken Link Checker
nowork-studio/notfair-plugin
Crawls a website with a bundled Python script to find broken internal and outbound links, then reports them by status code with the pages they appear on.
More from rampstackco/claude-skills
All 103 skills in this repoAfter Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
Analytics Strategy
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
Brand Style Guide
rampstackco/claude-skills
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.
Brand Voice
rampstackco/claude-skills
Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.
Content And Copy
rampstackco/claude-skills
Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.
Content Strategy
rampstackco/claude-skills
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.
Related
Categories
Questions about Domain Strategy
What does Domain Strategy do?
Plan, manage, and optimize a domain portfolio. An agent skill from rampstackco/claude-skills. Domain Strategy is an agent skill from rampstackco/claude-skills. Plan, manage, and optimize a domain portfolio.
When should I use Domain Strategy?
Domain Strategy fits situations like: DNS architecture decisions; redirect strategies; registrar choice; parking unused domains.
How do I install Domain Strategy in Claude Code?
Run `npx skills add rampstackco/claude-skills --skill domain-strategy -a claude-code`. Or copy the skill folder (skills/domain-strategy in rampstackco/claude-skills) into .claude/skills/domain-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Domain Strategy in Codex?
Run `npx skills add rampstackco/claude-skills --skill domain-strategy -a codex`. Or copy the skill folder (skills/domain-strategy in rampstackco/claude-skills) into .agents/skills/domain-strategy in your project. Codex loads it when a task matches its description.
Can I use Domain Strategy 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 rampstackco/claude-skills --skill domain-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/domain-strategy, .gemini/skills/domain-strategy, .github/skills/domain-strategy and .opencode/skills/domain-strategy in your project.
What does Domain Strategy need to run?
Going by SKILL.md and its folder, Domain Strategy needs the command-line tools its instructions call (curl).
Does Domain Strategy access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Domain Strategy 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 Domain Strategy use?
Domain Strategy 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 Domain Strategy use?
About 2.2k tokens (SKILL.md is roughly 8.8k 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 2k tokens, read only when the agent opens those files.
What are the alternatives to Domain Strategy?
Skills that share tags, products or a category with Domain Strategy: Hreflang and International SEO (AgriciDaniel/claude-seo, 18k stars), Google SEO APIs (AgriciDaniel/claude-seo, 18k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars) and SEO Audit with Search Console (nowork-studio/notfair-plugin, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Domain Strategy?
rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 935 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.
Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.