beat-competitors은(는) 무엇을 하나요?
경쟁사 SEO 데이터를 우선순위가 지정된 공격 계획으로 전환합니다. 사용자가 경쟁사 분석, 경쟁 격차, 경쟁사보다 높은 순위를 차지하는 방법, 경쟁사가 순위를 차지하는 키워드, 키워드 중복 또는 경쟁 포지셔닝 전략에 대해 물을 때 사용하세요. 격차를 메우기 위한 콘텐츠 제작은 brief 및 build-clusters를 참조하세요.
경쟁사 SEO 데이터를 우선순위가 지정된 공격 계획으로 전환합니다. 사용자가 경쟁사 분석, 경쟁 격차, 경쟁사보다 높은 순위를 차지하는 방법, 경쟁사가 순위를 차지하는 키워드, 키워드 중복 또는 경쟁 포지셔닝 전략에 대해 물을 때 사용하세요. 격차를 메우기 위한 콘텐츠 제작은 brief 및 build-clusters를 참조하세요.
이 스킬은 경쟁사 SEO 분석 데이터를 체계적이고 실행 가능한 공격 계획으로 변환하는 AI 어시스턴트 도구입니다. 사용자가 '경쟁사 분석', '경쟁 격차 파악', '경쟁사 제치기', '경쟁사 순위 키워드', '키워드 중복 분석', '경쟁 포지셔닝 전략' 등과 같은 요청을 할 때 활성화됩니다. 이 스킬은 검색 엔진 최적화(SEO) 전문가, 콘텐츠 마케터, 디지털 마케팅 담당자에게 유용하며, 데이터 기반 인사이트를 제공하여 경쟁사 대비 우위를 점할 수 있도록 돕습니다. 주요 작업 흐름은 경쟁사 데이터 수집, 격차 식별, 우선순위 설정, 그리고 실행 가능한 권장 사항 생성으로 구성됩니다. 또한, 구체적인 콘텐츠 제작이 필요한 경우 brief 및 build-clusters 스킬과 연계하여 사용할 수 있습니다.
npx skills add https://github.com/calm-north/seojuice-skills/tree/main/skills/beat-competitorsInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
경쟁사 SEO 데이터를 우선순위가 지정된 공격 계획으로 전환합니다. 사용자가 경쟁사 분석, 경쟁 격차, 경쟁사보다 높은 순위를 차지하는 방법, 경쟁사가 순위를 차지하는 키워드, 키워드 중복 또는 경쟁 포지셔닝 전략에 대해 물을 때 사용하세요. 격차를 메우기 위한 콘텐츠 제작은 brief 및 build-clusters를 참조하세요.
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.
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.
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.