[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBRPWEP4KKA3S4F058HTFX":3,"skill-same:01M7FBRPWEP4KKA3S4F058HTFX":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7FBRPWEP4KKA3S4F058HTFX","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.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fcontent-media\u002Fskills\u002Fseo\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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.\nmetadata:\n  origin: 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,"metadata":24,"description":7},{"origin":25},"ECC","main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fcontent-media\u002Fskills\u002Fseo",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add siddu1004\u002FSFP --skill seo",{"tool":41,"command":42},"bunx","bunx skills add siddu1004\u002FSFP --skill seo",{"tool":44,"command":45},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fcontent-media\u002Fskills\u002Fseo\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]