[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75EW40E5KGC6FGF7JQMZTMM":3,"skill-same:01M75EW40E5KGC6FGF7JQMZTMM":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75EW40E5KGC6FGF7JQMZTMM","keyword-research",null,"Discover keyword opportunities, evaluate metrics and SERPs, and save\u002Ftag promising terms.","LongLeo287\u002FSEOSONA-OS","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M75CK60XQGYJY3YDGGFJQDYT",2,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fseo_marketing\u002Fopen_seo\u002Fkeyword-research\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: keyword-research\ndescription: \"Discover keyword opportunities, evaluate metrics and SERPs, and save\u002Ftag promising terms.\"\n---\n\n# OpenSEO Keyword Research\n\n## Goal\n\nTurn seed topics into a prioritized keyword opportunity set using OpenSEO MCP data. The output should help the user decide what to target, what to save, and what to research next.\n\n## Required inputs\n\n- `projectId`\n- One or more seed topics, products, pages, competitors, or audience problems\n- Optional market\u002Flocation\u002Flanguage\n\nIf `projectId` is missing, use `list_projects` first. If the target market\u002Flocation\u002Flanguage is unclear and would materially affect keyword metrics, ask the user; otherwise use the MCP tool defaults.\n\n## OpenSEO MCP tools\n\n- `research_keywords`: primary discovery tool. Use 1-5 seeds per call and prefer 150 results unless the user asks for exhaustive research.\n- `get_keyword_metrics`: hydrate up to 700 known keywords with volume, keyword difficulty (KD), search intent, CPC, and monthly trends in one call. Use it to score candidate or known terms — including the Search Console striking-distance queries from step 1.\n- `get_ranked_keywords`: pull exact ranking keyword rows when a target domain or page is part of the research brief.\n- `get_search_console_performance`: when Search Console is connected, start from the project's real first-party demand — queries already earning impressions and near-ranking (\"striking distance\") terms. Request a high `rowLimit` and filter average position 5-20 client-side, since the API sorts by clicks and can't filter by position. Then hydrate those striking-distance queries with `get_keyword_metrics` to attach difficulty and intent.\n- `get_serp_results`: inspect SERPs for the top candidate terms, especially when intent is ambiguous.\n- `search_local_businesses`, `get_local_serp_results`, and `get_google_business_questions`: use for local SEO topics when a business\u002Flocation radius matters.\n- `list_saved_keywords`: avoid duplicating already-saved work or use existing tags as context.\n- `save_keywords`: save selected keywords only after explicit user confirmation.\n\n## Workflow\n\n1. Normalize seeds into a small set of distinct research angles. If Search Console is connected for the project, first pull `get_search_console_performance` (high `rowLimit`, default lookback), filter to striking-distance positions (~5–20) client-side, and hydrate those queries with `get_keyword_metrics` to attach KD and intent. That ranked, hydrated list is your fastest opportunity set — work it before broad discovery.\n2. If the request is local SEO, identify the business, location\u002Fcoordinates or service area, and local categories. Use `search_local_businesses` and `get_local_serp_results` for the most important location\u002Fkeyword set instead of relying only on national keyword\u002FSERP data.\n3. Call `research_keywords` for exploratory seeds. Use bulk calls when possible.\n4. Use `get_keyword_metrics` to hydrate a fixed keyword list — or the striking-distance queries from step 1 — with volume, KD, and intent before prioritizing.\n5. Use `get_ranked_keywords` when the user provides a domain\u002Fpage and wants opportunities based on current rankings, near-misses, or competitor-owned terms.\n6. Remove irrelevant, duplicate, branded-only, and off-intent terms.\n7. Prioritize by practical opportunity, not volume alone:\n   - Strong match to the user's product\u002Fpage\u002Ftopic\n   - Clear search intent\n   - Reasonable difficulty\n   - Useful volume\u002FCPC signal\n   - SERP where the user can plausibly compete\n   - For local SEO, local-pack\u002FMaps visibility and proximity fit\n8. Use `get_serp_results` for high-potential or ambiguous keywords when SERP intent would change the recommendation; keep the default check small.\n9. Present a shortlist and a longer opportunity table.\n10. Ask before saving keywords. When saving, suggest concise tags such as `topic:\u003Ctopic>`, `intent:\u003Cintent>`, or `page:\u003Cslug>`.\n\n## Output format\n\nStart with the highest-signal recommendation:\n\n- Best opportunity theme\n- Top keywords to target now\n- Keywords to save\n- Risks or SERP caveats\n\nThen include a compact table:\n\n| Keyword | Intent | Volume |  KD | CPC | Priority | Notes |\n| ------- | ------ | -----: | --: | --: | -------- | ----- |\n\nEnd with next actions, including whether to run keyword clustering, create a content brief, or save the chosen keywords.\n\n## Guardrails\n\n- Do not invent metrics. If OpenSEO does not return a value, write `unknown`.\n- Do not call `save_keywords` without explicit confirmation.\n- Prefer business-fit and intent-fit over chasing the largest volume term.\n","# OpenSEO Keyword Research\n\n## Goal\n\nTurn seed topics into a prioritized keyword opportunity set using OpenSEO MCP data. The output should help the user decide what to target, what to save, and what to research next.\n\n## Required inputs\n\n- `projectId`\n- One or more seed topics, products, pages, competitors, or audience problems\n- Optional market\u002Flocation\u002Flanguage\n\nIf `projectId` is missing, use `list_projects` first. If the target market\u002Flocation\u002Flanguage is unclear and would materially affect keyword metrics, ask the user; otherwise use the MCP tool defaults.\n\n## OpenSEO MCP tools\n\n- `research_keywords`: primary discovery tool. Use 1-5 seeds per call and prefer 150 results unless the user asks for exhaustive research.\n- `get_keyword_metrics`: hydrate up to 700 known keywords with volume, keyword difficulty (KD), search intent, CPC, and monthly trends in one call. Use it to score candidate or known terms — including the Search Console striking-distance queries from step 1.\n- `get_ranked_keywords`: pull exact ranking keyword rows when a target domain or page is part of the research brief.\n- `get_search_console_performance`: when Search Console is connected, start from the project's real first-party demand — queries already earning impressions and near-ranking (\"striking distance\") terms. Request a high `rowLimit` and filter average position 5-20 client-side, since the API sorts by clicks and can't filter by position. Then hydrate those striking-distance queries with `get_keyword_metrics` to attach difficulty and intent.\n- `get_serp_results`: inspect SERPs for the top candidate terms, especially when intent is ambiguous.\n- `search_local_businesses`, `get_local_serp_results`, and `get_google_business_questions`: use for local SEO topics when a business\u002Flocation radius matters.\n- `list_saved_keywords`: avoid duplicating already-saved work or use existing tags as context.\n- `save_keywords`: save selected keywords only after explicit user confirmation.\n\n## Workflow\n\n1. Normalize seeds into a small set of distinct research angles. If Search Console is connected for the project, first pull `get_search_console_performance` (high `rowLimit`, default lookback), filter to striking-distance positions (~5–20) client-side, and hydrate those queries with `get_keyword_metrics` to attach KD and intent. That ranked, hydrated list is your fastest opportunity set — work it before broad discovery.\n2. If the request is local SEO, identify the business, location\u002Fcoordinates or service area, and local categories. Use `search_local_businesses` and `get_local_serp_results` for the most important location\u002Fkeyword set instead of relying only on national keyword\u002FSERP data.\n3. Call `research_keywords` for exploratory seeds. Use bulk calls when possible.\n4. Use `get_keyword_metrics` to hydrate a fixed keyword list — or the striking-distance queries from step 1 — with volume, KD, and intent before prioritizing.\n5. Use `get_ranked_keywords` when the user provides a domain\u002Fpage and wants opportunities based on current rankings, near-misses, or competitor-owned terms.\n6. Remove irrelevant, duplicate, branded-only, and off-intent terms.\n7. Prioritize by practical opportunity, not volume alone:\n   - Strong match to the user's product\u002Fpage\u002Ftopic\n   - Clear search intent\n   - Reasonable difficulty\n   - Useful volume\u002FCPC signal\n   - SERP where the user can plausibly compete\n   - For local SEO, local-pack\u002FMaps visibility and proximity fit\n8. Use `get_serp_results` for high-potential or ambiguous keywords when SERP intent would change the recommendation; keep the default check small.\n9. Present a shortlist and a longer opportunity table.\n10. Ask before saving keywords. When saving, suggest concise tags such as `topic:\u003Ctopic>`, `intent:\u003Cintent>`, or `page:\u003Cslug>`.\n\n## Output format\n\nStart with the highest-signal recommendation:\n\n- Best opportunity theme\n- Top keywords to target now\n- Keywords to save\n- Risks or SERP caveats\n\nThen include a compact table:\n\n| Keyword | Intent | Volume |  KD | CPC | Priority | Notes |\n| ------- | ------ | -----: | --: | --: | -------- | ----- |\n\nEnd with next actions, including whether to run keyword clustering, create a content brief, or save the chosen keywords.\n\n## Guardrails\n\n- Do not invent metrics. If OpenSEO does not return a value, write `unknown`.\n- Do not call `save_keywords` without explicit confirmation.\n- Prefer business-fit and intent-fit over chasing the largest volume term.\n",{"name":5,"description":7},"main","4fd50b1281e8cd978866b6b4556242605cabf708","2_KNOWLEDGE\u002Fframeworks\u002Fseo_marketing\u002Fopen_seo\u002Fkeyword-research",1,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS","https:\u002F\u002Fseosona-os.vercel.app","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-10-09 15:14:13",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add LongLeo287\u002FSEOSONA-OS --skill keyword-research",{"tool":39,"command":40},"bunx","bunx skills add LongLeo287\u002FSEOSONA-OS --skill keyword-research",{"tool":42,"command":43},"pnpm","pnpm dlx skills add LongLeo287\u002FSEOSONA-OS --skill keyword-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fseo_marketing\u002Fopen_seo\u002Fkeyword-research\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M75F0T3V3W7JQQ05X26NNN2T","web_crawler_katana","High-speed web crawling using Katana patterns for deep site mapping, URL discovery, and content extraction.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fweb_crawler_katana\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M75F0Q2QJXDGAFKC7D84GT88","server_log_analyzer","Analyzes Nginx\u002FApache server logs to identify Googlebot crawl patterns, errors, and performance bottlenecks.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fserver_log_analyzer\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75F0KZP6D8R8XPN2YT35BAJ","schema_markup_generator","Auto-generates JSON-LD structured data for any page type (Article, Product, FAQ, LocalBusiness, etc.).","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fschema_markup_generator\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M75F0G3KX4Y86AXJXTKXVEVA","internal_linking_optimizer","Analyzes and optimizes the internal link graph of a website for SEO authority distribution.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Finternal_linking_optimizer\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75F0CS1RYX4YPJC7N6RAAQJ","google_trends_analyzer","Detects trending topics and seasonal patterns using Google Trends data for content planning and keyword strategy.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fgoogle_trends_analyzer\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75F0ASMQ1GKPFX82D19SRTN","brand_context_analyzer","Tracks brand mentions, sentiment, and online reputation across web sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fbrand_context_analyzer\u002FSKILL.md",[],[]]