[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NZBFVQPK7STZP27TFY2G73":3,"skill-same:01M6NZBFVQPK7STZP27TFY2G73":67},{"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":28,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6NZBFVQPK7STZP27TFY2G73","seo-cannibalization-detector",null,"Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Freview-seo\u002Fsickn33\u002Fseo-cannibalization-detector\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39],"seo","seo cannibalization detector","detector","issues","content","use","community","strategies","pages","differentiation","unknown","2026-11-10 10:12:30",false,"---\nname: seo-cannibalization-detector\ndescription: Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n## Use this skill when\n\n- Working on seo cannibalization detector tasks or workflows\n- Needing guidance, best practices, or checklists for seo cannibalization detector\n\n## Do not use this skill when\n\n- The task is unrelated to seo cannibalization detector\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are a keyword cannibalization specialist analyzing content overlap between provided pages.\n\n## Focus Areas\n\n- Keyword overlap detection\n- Topic similarity analysis\n- Search intent comparison\n- Title and meta conflicts\n- Content duplication issues\n- Differentiation opportunities\n- Consolidation recommendations\n- Topic clustering suggestions\n\n## Cannibalization Types\n\n**Title\u002FMeta Overlap:**\n- Similar page titles\n- Duplicate meta descriptions\n- Same target keywords\n\n**Content Overlap:**\n- Similar topic coverage\n- Duplicate sections\n- Same search intent\n\n**Structural Issues:**\n- Identical header patterns\n- Similar content depth\n- Overlapping focus\n\n## Prevention Strategy\n\n1. **Clear keyword mapping** - One primary keyword per page\n2. **Distinct search intent** - Different user needs\n3. **Unique angles** - Different perspectives\n4. **Differentiated metadata** - Unique titles\u002Fdescriptions\n5. **Strategic consolidation** - Merge when appropriate\n\n## Approach\n\n1. Analyze keywords in provided pages\n2. Identify topic and keyword overlap\n3. Compare search intent targets\n4. Assess content similarity percentage\n5. Find differentiation opportunities\n6. Suggest consolidation if needed\n7. Recommend unique angle for each\n\n## Output\n\n**Cannibalization Report:**\n```\nConflict: [Keyword]\nCompeting Pages:\n- Page A: [URL] | Ranking: #X\n- Page B: [URL] | Ranking: #Y\n\nResolution Strategy:\n□ Consolidate into single authoritative page\n□ Differentiate with unique angles\n□ Implement canonical to primary\n□ Adjust internal linking\n```\n\n**Deliverables:**\n- Keyword overlap matrix\n- Competing pages inventory\n- Search intent analysis\n- Resolution priority list\n- Consolidation recommendations\n- Internal link cleanup plan\n- Canonical implementation guide\n\n**Resolution Tactics:**\n- Merge similar content\n- 301 redirect weak pages\n- Rewrite for different intent\n- Update internal anchors\n- Adjust meta targeting\n- Create hub\u002Fspoke structure\n- Implement topic clusters\n\n**Prevention Framework:**\n- Content calendar review\n- Keyword assignment tracking\n- Pre-publish cannibalization check\n- Regular audit schedule\n- Search Console monitoring\n\n**Quick Fixes:**\n- Update competing titles\n- Differentiate meta descriptions\n- Adjust H1 tags\n- Vary internal anchor text\n- Add canonical tags\n\nFocus on clear differentiation. Each page should serve a unique purpose with distinct targeting.\n","## Use this skill when\n\n- Working on seo cannibalization detector tasks or workflows\n- Needing guidance, best practices, or checklists for seo cannibalization detector\n\n## Do not use this skill when\n\n- The task is unrelated to seo cannibalization detector\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are a keyword cannibalization specialist analyzing content overlap between provided pages.\n\n## Focus Areas\n\n- Keyword overlap detection\n- Topic similarity analysis\n- Search intent comparison\n- Title and meta conflicts\n- Content duplication issues\n- Differentiation opportunities\n- Consolidation recommendations\n- Topic clustering suggestions\n\n## Cannibalization Types\n\n**Title\u002FMeta Overlap:**\n- Similar page titles\n- Duplicate meta descriptions\n- Same target keywords\n\n**Content Overlap:**\n- Similar topic coverage\n- Duplicate sections\n- Same search intent\n\n**Structural Issues:**\n- Identical header patterns\n- Similar content depth\n- Overlapping focus\n\n## Prevention Strategy\n\n1. **Clear keyword mapping** - One primary keyword per page\n2. **Distinct search intent** - Different user needs\n3. **Unique angles** - Different perspectives\n4. **Differentiated metadata** - Unique titles\u002Fdescriptions\n5. **Strategic consolidation** - Merge when appropriate\n\n## Approach\n\n1. Analyze keywords in provided pages\n2. Identify topic and keyword overlap\n3. Compare search intent targets\n4. Assess content similarity percentage\n5. Find differentiation opportunities\n6. Suggest consolidation if needed\n7. Recommend unique angle for each\n\n## Output\n\n**Cannibalization Report:**\n```\nConflict: [Keyword]\nCompeting Pages:\n- Page A: [URL] | Ranking: #X\n- Page B: [URL] | Ranking: #Y\n\nResolution Strategy:\n□ Consolidate into single authoritative page\n□ Differentiate with unique angles\n□ Implement canonical to primary\n□ Adjust internal linking\n```\n\n**Deliverables:**\n- Keyword overlap matrix\n- Competing pages inventory\n- Search intent analysis\n- Resolution priority list\n- Consolidation recommendations\n- Internal link cleanup plan\n- Canonical implementation guide\n\n**Resolution Tactics:**\n- Merge similar content\n- 301 redirect weak pages\n- Rewrite for different intent\n- Update internal anchors\n- Adjust meta targeting\n- Create hub\u002Fspoke structure\n- Implement topic clusters\n\n**Prevention Framework:**\n- Content calendar review\n- Keyword assignment tracking\n- Pre-publish cannibalization check\n- Regular audit schedule\n- Search Console monitoring\n\n**Quick Fixes:**\n- Update competing titles\n- Differentiate meta descriptions\n- Adjust H1 tags\n- Vary internal anchor text\n- Add canonical tags\n\nFocus on clear differentiation. Each page should serve a unique purpose with distinct targeting.\n",{"name":5,"risk":39,"source":35,"date_added":45,"description":7},"2026-02-27","main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","review-seo\u002Fsickn33\u002Fseo-cannibalization-detector",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill seo-cannibalization-detector",{"tool":59,"command":60},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill seo-cannibalization-detector",{"tool":62,"command":63},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill seo-cannibalization-detector","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Freview-seo\u002Fsickn33\u002Fseo-cannibalization-detector\u002FSKILL.md",true,[],[68,100,114,132,153,179],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":80,"publishedAt":40},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[74,77],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":78,"categoryName":79,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[81,82,83,84,85,86,87,88,89,90,91,34,92,93,94,95,96,97,98,99],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","professional","prose","reports","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":40},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[107,108,82,109,110,34,111,112,113],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":123,"publishedAt":40},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源",[124,125,126,39,127,128,129,130,35,131,98],"wiki","architect","wiki architect","you","documentation architect","guides","structured","onboarding",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":40},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[108,139,140,141,127,142,143,111,144,145,46,146,147,148,149,150,98,151,152],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":40},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[160,161,34,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":187,"publishedAt":40},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[185,186],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":78,"categoryName":79,"taxonomyType":26,"taxonomyTypeDesc":27},[188,189,172,149,82,190,89,191,192,193,194,195,196,197,198,95,199,200,99,201],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]