웹사이트의 기술적 건강 상태, 온페이지 최적화, 콘텐츠 품질, 백링크 프로필을 포괄하는 종합적인 SEO 감사를 실행합니다. 사용자가 SEO 감사, 사이트 검토, SEO 건강 점검, '내 SEO에 무슨 문제가 있나요?', 웹사이트 분석 또는 사이트의 검색 성능에 대한 전체 진단을 요청할 때 사용하세요. 속도 관련 문제는 audit-speed를, 기술적 크롤링/색인 문제만 필요한 경우 diagnose-seo를 참조하세요.
이 스킬은 웹사이트의 SEO 성능을 포괄적으로 진단하는 자동화된 감사 도구입니다. 기술적 건강 상태(크롤링 가능성, 색인 상태, 사이트 구조), 온페이지 최적화(메타 태그, 헤더, 콘텐츠 관련성), 콘텐츠 품질(독창성, 깊이, 키워드 사용), 백링크 프로필(링크 품질, 다양성, 독성 링크) 등 네 가지 주요 영역을 분석합니다. 사용자가 'SEO 감사', '사이트 검토', 'SEO 건강 점검', '내 SEO에 무슨 문제가 있나요?'와 같은 요청을 할 때 실행되며, 결과는 구조화된 Markdown 보고서로 제공됩니다. 속도에 특화된 문제는 audit-speed 스킬을, 기술적 크롤링/색인 문제만 필요하다면 diagnose-seo 스킬을 사용하는 것이 좋습니다. 이 스킬은 Claude Code, Cursor, Codex 등 다양한 AI 에이전트 플랫폼에서 사용할 수 있도록 설계되었습니다.
npx skills add https://github.com/calm-north/seojuice-skills/tree/main/skills/auditInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
웹사이트의 기술적 건강 상태, 온페이지 최적화, 콘텐츠 품질, 백링크 프로필을 포괄하는 종합적인 SEO 감사를 실행합니다. 사용자가 SEO 감사, 사이트 검토, SEO 건강 점검, "내 SEO에 무슨 문제가 있나요?", 웹사이트 분석 또는 사이트의 검색 성능에 대한 전체 진단을 요청할 때 사용하세요. 속도 관련 문제는 audit-speed를, 기술적 크롤링/색인 문제만 필요한 경우 diagnose-seo를 참조하세요.
This repo contains 13 individual skills — each has its own dedicated page.
Deep Core Web Vitals and page speed audit. Use when the user asks about page speed, Core Web Vitals, LCP, CLS, INP, FCP, TTFB, Lighthouse scores, why a page is slow, performance optimization, or resource size analysis. For broader technical SEO issues, see diagnose-seo.
Turn competitor SEO data into a prioritized attack plan. Use when the user asks about competitor analysis, competitive gaps, how to outrank competitors, what competitors rank for, keyword overlap, or competitive positioning strategy. For building content to fill gaps, see brief and build-clusters.
Produce an editor-ready content brief for a target keyword or topic. Use when the user asks for a content brief, writing guidelines, article outline, SEO brief, what to include in a blog post, or how to structure content for a keyword. For choosing which topics to write about, see find-keywords. For a full site-wide SEO audit, see audit.
Build a topical authority cluster from a seed keyword or topic. Use when the user asks about topic clusters, content silos, pillar pages, topical authority, content architecture, or how to structure content around a theme. For finding the right keywords, see find-keywords. For writing individual pieces, see brief.
Design a link building campaign with prospect identification, asset creation, and outreach strategy. Use when the user asks about link building, backlinks, domain authority, how to get backlinks, outreach campaigns, digital PR, guest posting, or link acquisition. For internal linking, see fix-linking.
Structured diagnostic for technical SEO problems. Use when the user asks about crawl issues, indexation problems, why pages aren't being indexed, robots.txt questions, canonical errors, sitemap issues, rendering problems, or general technical SEO troubleshooting. For Core Web Vitals and page speed, see audit-speed.
Build a prioritized keyword list for a website, topic, or campaign. Use when the user asks about keyword research, finding keywords to target, building a keyword list, search demand, keyword difficulty, intent mapping, or which keywords to prioritize. For writing content around keywords, see brief. For grouping keywords into clusters, see build-clusters.
Design or audit internal link structure for a website. Use when the user asks about internal linking, link architecture, orphan pages, PageRank flow, anchor text, site structure, silo architecture, or why pages aren't ranking despite good content. For external link building, see build-links.
Guide a website migration without losing rankings — domain moves, CMS switches, URL restructures, HTTP to HTTPS, or redesigns. Use when the user asks about site migration, domain change, CMS migration, URL restructure, redesign SEO impact, redirect mapping, or how to move a site safely.
Optimize content for AI search engines — ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews. Use when the user asks about AI SEO, AISO, getting cited by AI, appearing in AI answers, answer engine optimization, AEO, GEO, LLMO, AI Overviews, zero-click search, or how to appear in ChatGPT/Perplexity results. For traditional SEO, see diagnose-seo.
Build a local SEO strategy covering Google Business Profile, local citations, reviews, and NAP consistency. Use when the user asks about local SEO, Google Business Profile, Google Maps ranking, local pack, NAP consistency, local citations, review strategy, or ranking for "[service] near me" searches.
Diagnose and reverse traffic loss on existing pages. Use when the user asks about content decay, pages losing traffic, declining rankings, traffic drops, why a page stopped ranking, content refresh strategy, or when to consolidate vs redirect old content. For creating new content, see brief.
Identify and capture SERP features for target keywords — featured snippets, People Also Ask boxes, knowledge panels, and rich results. Use when the user asks about featured snippets, position zero, PAA optimization, rich results, schema markup for SERP features, or how to get more SERP real estate.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.