[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730V3AC9T3BSGQHJ4FC1PAS":3,"skill-same:01M730V3AC9T3BSGQHJ4FC1PAS":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M730V3AC9T3BSGQHJ4FC1PAS","seo",null,"Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap\u002Frobots work, or keyword mapping.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002Fskills\u002Fseo\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: seo\ndescription: Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap\u002Frobots work, or keyword mapping.\norigin: ECC\n---\n\n# SEO\n\nImprove search visibility through technical correctness, performance, and content relevance, not gimmicks.\n\n## When to Use\n\nUse this skill when:\n- auditing crawlability, indexability, canonicals, or redirects\n- improving title tags, meta descriptions, and heading structure\n- adding or validating structured data\n- improving Core Web Vitals\n- doing keyword research and mapping keywords to URLs\n- planning internal linking or sitemap \u002F robots changes\n\n## How It Works\n\n### Principles\n\n1. Fix technical blockers before content optimization.\n2. One page should have one clear primary search intent.\n3. Prefer long-term quality signals over manipulative patterns.\n4. Mobile-first assumptions matter because indexing is mobile-first.\n5. Recommendations should be page-specific and implementable.\n\n### Technical SEO checklist\n\n#### Crawlability\n\n- `robots.txt` should allow important pages and block low-value surfaces\n- no important page should be unintentionally `noindex`\n- important pages should be reachable within a shallow click depth\n- avoid redirect chains longer than two hops\n- canonical tags should be self-consistent and non-looping\n\n#### Indexability\n\n- preferred URL format should be consistent\n- multilingual pages need correct hreflang if used\n- sitemaps should reflect the intended public surface\n- no duplicate URLs should compete without canonical control\n\n#### Performance\n\n- LCP \u003C 2.5s\n- INP \u003C 200ms\n- CLS \u003C 0.1\n- common fixes: preload hero assets, reduce render-blocking work, reserve layout space, trim heavy JS\n\n#### Structured data\n\n- homepage: organization or business schema where appropriate\n- editorial pages: `Article` \u002F `BlogPosting`\n- product pages: `Product` and `Offer`\n- interior pages: `BreadcrumbList`\n- Q&A sections: `FAQPage` only when the content truly matches\n\n### On-page rules\n\n#### Title tags\n\n- aim for roughly 50-60 characters\n- put the primary keyword or concept near the front\n- make the title legible to humans, not stuffed for bots\n\n#### Meta descriptions\n\n- aim for roughly 120-160 characters\n- describe the page honestly\n- include the main topic naturally\n\n#### Heading structure\n\n- one clear `H1`\n- `H2` and `H3` should reflect actual content hierarchy\n- do not skip structure just for visual styling\n\n### Keyword mapping\n\n1. define the search intent\n2. gather realistic keyword variants\n3. prioritize by intent match, likely value, and competition\n4. map one primary keyword\u002Ftheme to one URL\n5. detect and avoid cannibalization\n\n### Internal linking\n\n- link from strong pages to pages you want to rank\n- use descriptive anchor text\n- avoid generic anchors when a more specific one is possible\n- backfill links from new pages to relevant existing ones\n\n## Examples\n\n### Title formula\n\n```text\nPrimary Topic - Specific Modifier | Brand\n```\n\n### Meta description formula\n\n```text\nAction + topic + value proposition + one supporting detail\n```\n\n### JSON-LD example\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"Page Title Here\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"Author Name\"\n  },\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"Brand Name\"\n  }\n}\n```\n\n### Audit output shape\n\n```text\n[HIGH] Duplicate title tags on product pages\nLocation: src\u002Froutes\u002Fproducts\u002F[slug].tsx\nIssue: Dynamic titles collapse to the same default string, which weakens relevance and creates duplicate signals.\nFix: Generate a unique title per product using the product name and primary category.\n```\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n| --- | --- |\n| keyword stuffing | write for users first |\n| thin near-duplicate pages | consolidate or differentiate them |\n| schema for content that is not actually present | match schema to reality |\n| content advice without checking the actual page | read the real page first |\n| generic “improve SEO” outputs | tie every recommendation to a page or asset |\n\n## Related Skills\n\n- `seo-specialist`\n- `frontend-patterns`\n- `brand-voice`\n- `market-research`\n","# SEO\n\nImprove search visibility through technical correctness, performance, and content relevance, not gimmicks.\n\n## When to Use\n\nUse this skill when:\n- auditing crawlability, indexability, canonicals, or redirects\n- improving title tags, meta descriptions, and heading structure\n- adding or validating structured data\n- improving Core Web Vitals\n- doing keyword research and mapping keywords to URLs\n- planning internal linking or sitemap \u002F robots changes\n\n## How It Works\n\n### Principles\n\n1. Fix technical blockers before content optimization.\n2. One page should have one clear primary search intent.\n3. Prefer long-term quality signals over manipulative patterns.\n4. Mobile-first assumptions matter because indexing is mobile-first.\n5. Recommendations should be page-specific and implementable.\n\n### Technical SEO checklist\n\n#### Crawlability\n\n- `robots.txt` should allow important pages and block low-value surfaces\n- no important page should be unintentionally `noindex`\n- important pages should be reachable within a shallow click depth\n- avoid redirect chains longer than two hops\n- canonical tags should be self-consistent and non-looping\n\n#### Indexability\n\n- preferred URL format should be consistent\n- multilingual pages need correct hreflang if used\n- sitemaps should reflect the intended public surface\n- no duplicate URLs should compete without canonical control\n\n#### Performance\n\n- LCP \u003C 2.5s\n- INP \u003C 200ms\n- CLS \u003C 0.1\n- common fixes: preload hero assets, reduce render-blocking work, reserve layout space, trim heavy JS\n\n#### Structured data\n\n- homepage: organization or business schema where appropriate\n- editorial pages: `Article` \u002F `BlogPosting`\n- product pages: `Product` and `Offer`\n- interior pages: `BreadcrumbList`\n- Q&A sections: `FAQPage` only when the content truly matches\n\n### On-page rules\n\n#### Title tags\n\n- aim for roughly 50-60 characters\n- put the primary keyword or concept near the front\n- make the title legible to humans, not stuffed for bots\n\n#### Meta descriptions\n\n- aim for roughly 120-160 characters\n- describe the page honestly\n- include the main topic naturally\n\n#### Heading structure\n\n- one clear `H1`\n- `H2` and `H3` should reflect actual content hierarchy\n- do not skip structure just for visual styling\n\n### Keyword mapping\n\n1. define the search intent\n2. gather realistic keyword variants\n3. prioritize by intent match, likely value, and competition\n4. map one primary keyword\u002Ftheme to one URL\n5. detect and avoid cannibalization\n\n### Internal linking\n\n- link from strong pages to pages you want to rank\n- use descriptive anchor text\n- avoid generic anchors when a more specific one is possible\n- backfill links from new pages to relevant existing ones\n\n## Examples\n\n### Title formula\n\n```text\nPrimary Topic - Specific Modifier | Brand\n```\n\n### Meta description formula\n\n```text\nAction + topic + value proposition + one supporting detail\n```\n\n### JSON-LD example\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"Page Title Here\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"Author Name\"\n  },\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"Brand Name\"\n  }\n}\n```\n\n### Audit output shape\n\n```text\n[HIGH] Duplicate title tags on product pages\nLocation: src\u002Froutes\u002Fproducts\u002F[slug].tsx\nIssue: Dynamic titles collapse to the same default string, which weakens relevance and creates duplicate signals.\nFix: Generate a unique title per product using the product name and primary category.\n```\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n| --- | --- |\n| keyword stuffing | write for users first |\n| thin near-duplicate pages | consolidate or differentiate them |\n| schema for content that is not actually present | match schema to reality |\n| content advice without checking the actual page | read the real page first |\n| generic “improve SEO” outputs | tie every recommendation to a page or asset |\n\n## Related Skills\n\n- `seo-specialist`\n- `frontend-patterns`\n- `brand-voice`\n- `market-research`\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Feverything-claude-code\u002Fskills\u002Fseo",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill seo",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill seo",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002Fskills\u002Fseo\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]