audit-speed은(는) 무엇을 하나요?
핵심 웹 바이탈 및 페이지 속도 심층 감사. 사용자가 페이지 속도, Core Web Vitals, LCP, CLS, INP, FCP, TTFB, Lighthouse 점수, 페이지 속도 저하 원인, 성능 최적화 또는 리소스 크기 분석에 대해 질문할 때 사용합니다. 포괄적인 기술 SEO 문제의 경우 diagnose-seo를 참조하세요.
핵심 웹 바이탈 및 페이지 속도 심층 감사. 사용자가 페이지 속도, Core Web Vitals, LCP, CLS, INP, FCP, TTFB, Lighthouse 점수, 페이지 속도 저하 원인, 성능 최적화 또는 리소스 크기 분석에 대해 질문할 때 사용합니다. 포괄적인 기술 SEO 문제의 경우 diagnose-seo를 참조하세요.
이 스킬은 웹 페이지의 핵심 성능 지표를 심층적으로 분석하고 감사하는 도구입니다. 사용자가 페이지 속도 저하, Lighthouse 점수, Core Web Vitals(LCP, CLS, INP, FCP, TTFB) 항목에 대해 질문하거나 성능 최적화 방안을 요청할 때 활성화됩니다. 주로 **Claude Code**, **Cursor**, **Codex** 같은 AI 에이전트 환경에서 사용되며, 페이지의 리소스 크기 분석과 병목 지점 진단을 지원합니다. SKILL.md 문서를 기반으로 작동하며, 기술 SEO 진단이 필요한 경우 `diagnose-seo` 스킬과 연계하여 사용할 수 있습니다. 개발자나 AI 에이전트 사용자가 사이트 성능 문제를 빠르게 식별하고 최적화 전략을 수립하는 데 유용합니다.
npx skills add https://github.com/calm-north/seojuice-skills/tree/main/skills/audit-speedInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
핵심 웹 바이탈 및 페이지 속도 심층 감사. 사용자가 페이지 속도, Core Web Vitals, LCP, CLS, INP, FCP, TTFB, Lighthouse 점수, 페이지 속도 저하 원인, 성능 최적화 또는 리소스 크기 분석에 대해 질문할 때 사용합니다. 포괄적인 기술 SEO 문제의 경우 diagnose-seo를 참조하세요.
This repo contains 13 individual skills — each has its own dedicated page.
Run a comprehensive SEO audit on a website covering technical health, on-page optimization, content quality, and backlink profile. Use when the user asks for an SEO audit, site review, SEO health check, "what's wrong with my SEO", website analysis, or a full diagnostic of their site's search performance. For speed-specific issues, see audit-speed. For technical crawl/index issues only, 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.