[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70H7GVBHJ3DJF18DDN418NF":3,"skill-same:01M70H7GVBHJ3DJF18DDN418NF":77},{"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":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M70H7GVBHJ3DJF18DDN418NF","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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fseo\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"mapping","technical","strategy","schema","structured data","Optimization","page","core","schema markup","content strategy","data","remediation","audit","plan","work","across","when","search","vitals","2026-11-10 10:12:30",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":53,"description":7},{"origin":54},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fseo",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill seo",{"tool":69,"command":70},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill seo",{"tool":72,"command":73},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fseo\u002FSKILL.md",true,[],[78,86,94,101,108,115],{"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":85},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":93},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":93},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":93},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":93},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]