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.
Pre-consultation diagnostic questionnaire for clients building websites with AI tools (Claude, Codex, Cursor, Bolt, v0, etc.) who have concerns about quality, design, or maintainability.
Install Site Diagnosis
$ npx skills add glebis/claude-skills --skill site-diagnosis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glebis/claude-skills site-diagnosis --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/glebis/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/site-diagnosis .claude/skills/site-diagnosis && 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 "site-diagnosis" agent skill from https://github.com/glebis/claude-skills/tree/main/site-diagnosis into .claude/skills/site-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-diagnosis", 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/glebis/claude-skills/tree/main/site-diagnosisType 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 glebis/claude-skills --skill site-diagnosis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glebis/claude-skills site-diagnosis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/site-diagnosis .agents/skills/site-diagnosis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "site-diagnosis" agent skill from https://github.com/glebis/claude-skills/tree/main/site-diagnosis into .agents/skills/site-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-diagnosis", 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 glebis/claude-skills --skill site-diagnosis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glebis/claude-skills site-diagnosis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/site-diagnosis .cursor/skills/site-diagnosis && 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 "site-diagnosis" agent skill from https://github.com/glebis/claude-skills/tree/main/site-diagnosis into .cursor/skills/site-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-diagnosis", 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/glebis/claude-skills.git --path site-diagnosis--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 glebis/claude-skills --skill site-diagnosis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glebis/claude-skills site-diagnosis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/site-diagnosis .gemini/skills/site-diagnosis && 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 "site-diagnosis" agent skill from https://github.com/glebis/claude-skills/tree/main/site-diagnosis into .gemini/skills/site-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-diagnosis", 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 glebis/claude-skills site-diagnosisInstalls 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 glebis/claude-skills --skill site-diagnosis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/site-diagnosis .github/skills/site-diagnosis && 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 "site-diagnosis" agent skill from https://github.com/glebis/claude-skills/tree/main/site-diagnosis into .github/skills/site-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-diagnosis", 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 glebis/claude-skills --skill site-diagnosis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install glebis/claude-skills site-diagnosis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/site-diagnosis .opencode/skills/site-diagnosis && 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 "site-diagnosis" agent skill from https://github.com/glebis/claude-skills/tree/main/site-diagnosis into .opencode/skills/site-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-diagnosis", 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
site-diagnosis- GitHub stars
- 391
- Token cost
- ~2.3k tokens
- SKILL.md length
- 980 words
- Files
- 1
- Skills in repo
- 92
- Repo updated
- First seen
- Licence
- MIT
At a glance
Pre-consultation diagnostic questionnaire for clients building websites with AI tools (Claude, Codex, Cursor, Bolt, v0, etc.) who have concerns about quality, design, or maintainability.
- Preparing for a website review consultation
- SKILL.md covers How This Works, Round 0: Language, Round 1: Project & Background and Round 2: Current State & Pain…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A client asks for a site audit
What it does
Site Diagnosis is an agent skill from glebis/claude-skills. Pre-consultation diagnostic questionnaire for clients building websites with AI tools (Claude, Codex, Cursor, Bolt, v0, etc.) who have concerns about quality, design, or maintainability. Collects structured answers about their project, tools, pain points, and goals, then generates a consultation brief. Use when preparing for a website review consultation, when a client asks for a site audit, or when someone says their AI-built site has problems. Supports Russian and English — asks the client to choose language…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering SEO audit. The repository describes itself as: Collection of Claude Code skills for enhanced AI workflows. The licence is MIT.
When your agent uses it
- Preparing for a website review consultation
- A client asks for a site audit
- Someone says their AI-built site has problems
Example prompts
- “/site-diagnosis”
What it can do on your machine
Read from SKILL.md and the folder at commit 3b88261. 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 (its code samples are markdown).
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
Site Diagnosis loads about 2.3k tokens when it runs. Until then it costs about 134 tokens; SKILL.md has 980 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 glebis/claude-skills at commit 3b88261, republished under its MIT licence (© glebis). 980 words, ~2,306 tokens.
Download SKILL.mdSave it as
.claude/skills/site-diagnosis/SKILL.md (or your agent's skills folder).- name
- site-diagnosis
- description
- Pre-consultation diagnostic questionnaire for clients building websites with AI tools (Claude, Codex, Cursor, Bolt, v0, etc.) who have concerns about quality, design, or maintainability. Collects structured answers about their project, tools, pain points, and goals, then generates a consultation brief. Use when preparing for a website review consultation, when a client asks for a site audit, or when someone says their AI-built site has problems. Supports Russian and English — asks the client to choose language first.
Site Diagnosis — Pre-Consultation Questionnaire
You are conducting a structured diagnostic interview to prepare for a website consultation. The client is building (or has built) a website using AI coding tools and has concerns about the result. Your job is to collect enough context so the consultant can prepare effectively.
How This Works
Walk the client through 5 rounds of questions using AskUserQuestion. Round 0 picks the language; Rounds 1–4 cover the diagnostic themes. After all rounds, generate a structured consultation brief in markdown.
Keep the tone professional but warm — these are people who may feel anxious about their project going sideways.
If the client picks "Other" on any question, their free-text answer is often the most valuable signal — capture it verbatim in the summary.
Round 0: Language
Ask this question alone, before anything else:
Question 0 — "Language / Язык"
- header: "Язык"
- question: "На каком языке вам удобнее проходить анкету? / Which language do you prefer?"
- options:
- "Русский" — Russian
- "English" — English
- multiSelect: false
Store the chosen language. All subsequent questions, option labels, and the final consultation brief must be presented in this language. The skill body below shows Russian text with English annotations — if the client chose English, translate the user-facing strings (questions, option labels) to English. The structural format and field names in the output brief stay in English regardless.
Round 1: Project & Background
Ask these 3 questions together:
Question 1 — "Что вы делаете?"
- header: "Проект"
- question: "Какой сайт вы делаете или уже сделали?"
- options:
- "Лендинг / одностраничник" — single page, usually for a product or service launch
- "Сайт-визитка / портфолио" — personal or business card site, portfolio
- "Интернет-магазин" — e-commerce with catalog and payments
- "Блог / контентный сайт" — content-driven, articles, media
- multiSelect: false
Question 2 — "Ваш технический уровень"
- header: "Опыт"
- question: "Как бы вы описали свой технический уровень?"
- options:
- "Полный ноль — до ИИ не писал(а) код" — no prior coding experience
- "Базовый — могу поправить HTML/CSS" — can do basic edits
- "Средний — понимаю фреймворки, могу разобраться" — comfortable with frameworks
- "Продвинутый — программирую профессионально" — professional developer
- multiSelect: false
Question 3 — "Какие ИИ-инструменты используете?"
- header: "Инструменты"
- question: "Какими ИИ-инструментами вы пользуетесь для создания сайта?"
- options:
- "Claude (Code, Projects, чат)" — Anthropic's Claude in any form
- "Cursor / Windsurf / другая ИИ-IDE" — AI-powered code editors
- "Bolt / Lovable / v0" — no-code AI builders
- "ChatGPT / Codex" — OpenAI tools
- multiSelect: true
Round 2: Current State & Pain Points
Question 4 — "На каком этапе проект?"
- header: "Этап"
- question: "На каком этапе сейчас находится ваш сайт?"
- options:
- "В самом начале — есть идея, мало кода" — early stage
- "В процессе — основная часть сделана, но не готово" — mid-build
- "Почти готов — доделываю детали" — nearly done
- "Уже запущен — но хочу улучшить" — live, needs improvement
- multiSelect: false
Question 5 — "Что беспокоит больше всего?"
- header: "Боли"
- question: "Что вас больше всего беспокоит в текущем состоянии сайта?"
- options:
- "Дизайн — выглядит 'как от ИИ', непрофессионально" — generic AI look
- "Код — не понимаю что там внутри, боюсь сломать" — black box code
- "Администрирование — непонятно как обновлять контент" — content management
- "Производительность — медленно грузится, ошибки" — performance issues
- multiSelect: true
Question 6 — "Что нравится в текущем результате?"
- header: "Плюсы"
- question: "Есть ли что-то, что вам нравится в том, что уже получилось?"
- options:
- "Да, базовая структура и логика хорошие" — good foundation
- "Да, отдельные страницы/секции удались" — some parts work well
- "Скорее нет — хочу переделать существенную часть" — mostly unhappy
- "Сложно оценить — поэтому и нужна консультация" — can't tell, need expert eye
- multiSelect: false
Show full SKILL.md (440 more words)Show less
Round 3: Design & Technical Details
Question 7 — "Проблемы с дизайном"
- header: "Дизайн"
- question: "Какие проблемы с дизайном вы видите?"
- options:
- "Выглядит шаблонно / скучно" — looks templated, generic
- "Цвета и шрифты не сочетаются" — poor color/typography choices
- "Неудобная навигация, непонятная структура" — bad UX/IA
- "Плохо выглядит на телефоне" — not mobile-friendly
- multiSelect: true
Question 8 — "Где размещён сайт?"
- header: "Хостинг"
- question: "Где размещён (или планируется разместить) ваш сайт?"
- options:
- "Vercel / Netlify / Cloudflare Pages" — modern JAMstack hosting
- "Свой сервер / VPS" — self-hosted
- "Пока нигде — только локально" — local only
- "Не знаю / не уверен(а)" — don't know
- multiSelect: false
Question 9 — "Технологии"
- header: "Стек"
- question: "Знаете ли вы, какие технологии использует ваш сайт?"
- options:
- "React / Next.js" — React ecosystem
- "HTML/CSS/JS без фреймворка" — vanilla stack
- "Другой фреймворк (Vue, Svelte, Astro...)" — other framework
- "Не знаю — ИИ сам выбрал" — AI chose, client doesn't know
- multiSelect: false
Round 4: Goals & Expectations
Question 10 — "Как планируете обновлять контент?"
- header: "Контент"
- question: "Как вы планируете обновлять контент на сайте после запуска?"
- options:
- "Буду просить ИИ вносить изменения" — ask AI to edit
- "Хочу CMS (админку), чтобы самому менять" — wants a CMS
- "Буду редактировать код вручную" — manual code edits
- "Пока не думал(а) об этом" — hasn't considered this yet
- multiSelect: false
Question 11 — "Что хотите получить от консультации?"
- header: "Цель"
- question: "Какой результат консультации был бы для вас идеальным?"
- options:
- "Конкретный план — что исправить и в каком порядке" — actionable fix plan
- "Оценку — стоит ли продолжать или лучше начать заново" — go/no-go assessment
- "Обучение — научиться лучше работать с ИИ-инструментами" — learn to use AI better
- "Помощь с конкретной проблемой (расскажу подробнее)" — specific problem
- multiSelect: true
Question 12 — "Что ещё важно знать?"
This is a free-text question. Do NOT use AskUserQuestion here — instead, ask the client directly in conversation text (in their chosen language):
Russian: "Последний вопрос! Пожалуйста, напишите свободным текстом всё, что считаете важным: ссылку на сайт или репозиторий, примерный бюджет на доработку, конкретные страницы или элементы, которые беспокоят, референсы (сайты, которые нравятся) — любые детали, которые помогут подготовиться к консультации."
English: "Last question! Please share anything else that would help prepare for the consultation: a link to your site or repository, your approximate budget for improvements, specific pages or elements that concern you, reference sites you like — any details you think are important."
Wait for the client's free-text response before generating the summary.
Generating the Summary
After all 4 rounds, generate a consultation brief in this format and save it to the Obsidian vault at Claude-Drafts/YYYYMMDD-site-diagnosis-CLIENT.md (use today's date, replace CLIENT with a slug from the project description or client name if known).
---
type: consultation-brief
created_date: '[[YYYYMMDD]]'
status: pending
---
# Site Diagnosis Brief
## Client Profile
- **Technical level**: [answer]
- **AI tools**: [answer]
## Project
- **Type**: [answer]
- **Stage**: [answer]
- **Tech stack**: [answer]
- **Hosting**: [answer]
## Pain Points
- **Primary concerns**: [answer]
- **Design issues**: [answer]
- **Content management plan**: [answer]
## What's Working
[answer]
## Consultation Goals
[answer]
## Additional Details
[Free-text answer from Question 12 — links, budget, references, specific concerns. Capture verbatim, then add any structured observations below.]
## Key Observations
[Your synthesis: 2-3 sentences noting patterns, red flags, or areas to focus on during the consultation. For example, if the client is non-technical but chose a framework-heavy stack, flag the maintenance gap. If they want a CMS but are on a static site, note the mismatch.]
## Suggested Consultation Focus
[Based on the answers, suggest 3-4 specific topics to cover in the consultation, ordered by priority]After saving, tell the user where the file is and offer a brief summary of what you noticed — the patterns, mismatches, or key risks that stand out from the answers.
© glebis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in site-diagnosis of glebis/claude-skills.
Open the folder on GitHubat commit 3b88261
Compare with similar skills
Site Diagnosis 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 |
|---|---|---|---|---|---|---|
| Site Diagnosis this skillglebis/claude-skills | 391 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Hreflang and International SEOAgriciDaniel/claude-seo | 19k | 5 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Google SEO APIsAgriciDaniel/claude-seo | 19k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Evaluate Skillevery-app/open-seo | 23k | — | ~1.8k | Automated safety check: Notes | MIT | |
| FLOW SEO FrameworkAgriciDaniel/claude-seo | 19k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude | 11k | — | ~2.8k | Automated safety check: Notes | 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.
Evaluate Skill
every-app/open-seo
Test a candidate OpenSEO skill end to end by running fresh, isolated Codex sessions against the local backend and scoring the reports they save.
FLOW SEO Framework
AgriciDaniel/claude-seo
Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.
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.
GEO Monthly Delta Report
zubair-trabzada/geo-seo-claude
Compares a baseline and a current GEO audit for a client, calculates score changes and action item progress, and writes a monthly progress report.
More from glebis/claude-skills
All 92 skills in this repoPII Annotation and Agreement Scorer
glebis/claude-skills
Runs a human-first workflow for labeling PII spans in a transcript, then scores inter-annotator agreement and drafts an adjudicated gold set.
Non-Destructive Chrome Automation
glebis/claude-skills
Automates a dedicated, logged-in Chrome instance per profile without ever closing the user's own open tabs or browser windows.
Deep Research
glebis/claude-skills
This skill should be used when conducting comprehensive research on any topic using the OpenAI Deep Research API.
Elimination Research
glebis/claude-skills
This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric…
Narrated HTML Presentations
glebis/claude-skills
Generates a self-contained HTML presentation with article and slides modes, ElevenLabs voiceover narration and optional GPT Image 2 illustrations.
Synthetic Coaching Session Generator
glebis/claude-skills
Writes fictional but realistic coaching or therapy session transcripts for evals, demos and few-shot examples, in several modalities and export formats.
Related
Categories
Questions about Site Diagnosis
What does Site Diagnosis do?
Pre-consultation diagnostic questionnaire for clients building websites with AI tools (Claude, Codex, Cursor, Bolt, v0, etc.) who have concerns about quality, design, or maintainability. Site Diagnosis is an agent skill from glebis/claude-skills.) who have concerns about quality, design, or maintainability.
When should I use Site Diagnosis?
Site Diagnosis fits situations like: preparing for a website review consultation; A client asks for a site audit; someone says their AI-built site has problems.
How do I install Site Diagnosis in Claude Code?
Run `npx skills add glebis/claude-skills --skill site-diagnosis -a claude-code`. Or copy the skill folder (site-diagnosis in glebis/claude-skills) into .claude/skills/site-diagnosis in your project. Claude Code loads it when a task matches its description.
How do I install Site Diagnosis in Codex?
Run `npx skills add glebis/claude-skills --skill site-diagnosis -a codex`. Or copy the skill folder (site-diagnosis in glebis/claude-skills) into .agents/skills/site-diagnosis in your project. Codex loads it when a task matches its description.
Can I use Site Diagnosis 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 glebis/claude-skills --skill site-diagnosis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/site-diagnosis, .gemini/skills/site-diagnosis, .github/skills/site-diagnosis and .opencode/skills/site-diagnosis in your project.
What does Site Diagnosis need to run?
SKILL.md names no scripts, command-line tools or credentials: Site Diagnosis is instructions for the agent only.
Does Site Diagnosis 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 Site Diagnosis 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 Site Diagnosis use?
Site Diagnosis 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 Site Diagnosis use?
About 2.3k tokens (SKILL.md is roughly 9.2k 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 Site Diagnosis?
Skills that share tags, products or a category with Site Diagnosis: Hreflang and International SEO (AgriciDaniel/claude-seo, 19k stars), Google SEO APIs (AgriciDaniel/claude-seo, 19k stars), Evaluate Skill (every-app/open-seo, 23k stars) and FLOW SEO Framework (AgriciDaniel/claude-seo, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Site Diagnosis?
glebis (a GitHub user) maintains it in glebis/claude-skills, which has 391 GitHub stars. The repository holds 92 skills in this directory. The repository was last updated on October 8, 2026.
Source: glebis/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.