find-keywords은(는) 무엇을 하나요?
웹사이트, 주제 또는 캠페인에 대한 우선 순위가 지정된 키워드 목록을 구축합니다. 사용자가 키워드 리서치, 타겟팅할 키워드 찾기, 키워드 목록 구축, 검색 수요, 키워드 난이도, 의도 매핑 또는 우선 순위를 지정할 키워드를 물어볼 때 사용하세요. 키워드에 대한 콘텐츠를 작성하려면 brief를 참조하세요. 키워드를 클러스터로 그룹화하려면 build-clusters를 참조하세요.
웹사이트, 주제 또는 캠페인에 대한 우선 순위가 지정된 키워드 목록을 구축합니다. 사용자가 키워드 리서치, 타겟팅할 키워드 찾기, 키워드 목록 구축, 검색 수요, 키워드 난이도, 의도 매핑 또는 우선 순위를 지정할 키워드를 물어볼 때 사용하세요. 키워드에 대한 콘텐츠를 작성하려면 brief를 참조하세요. 키워드를 클러스터로 그룹화하려면 build-clusters를 참조하세요.
이 스킬은 사용자의 요청에 따라 특정 웹사이트, 주제 또는 마케팅 캠페인에 대한 키워드 조사 및 우선 순위 목록을 자동으로 생성하는 데 사용됩니다. SEO 전문가 또는 콘텐츠 마케터가 타겟 트래픽을 유도할 적절한 키워드를 찾고, 검색량, 경쟁 난이도, 사용자 의도 등을 고려한 체계적인 키워드 목록을 구축할 수 있도록 지원합니다. 이 스킬은 주로 Claude Code와 같은 AI 에이전트 환경에서 작동하며, 사용자의 자연어 질문을 분석하여 관련성 높은 키워드를 발굴하고 우선 순위를 매깁니다. 구체적으로 특정 주제에 대한 주요 키워드와 롱테일 키워드를 제안하고, 각 키워드의 검색 수요와 난이도를 평가하며, 정보 탐색, 구매 의도 등 사용자 의도별로 매핑하는 과정을 자동화합니다. 이를 통해 사용자는 효율적으로 SEO 전략을 수립하고, 콘텐츠 계획을 최적화하며, 경쟁사 대비 우위를 점할 수 있습니다.
npx skills add https://github.com/calm-north/seojuice-skills/tree/main/skills/find-keywordsInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
웹사이트, 주제 또는 캠페인에 대한 우선 순위가 지정된 키워드 목록을 구축합니다. 사용자가 키워드 리서치, 타겟팅할 키워드 찾기, 키워드 목록 구축, 검색 수요, 키워드 난이도, 의도 매핑 또는 우선 순위를 지정할 키워드를 물어볼 때 사용하세요. 키워드에 대한 콘텐츠를 작성하려면 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.
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.
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.