[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PJY0MYS5SSBCPE4FNHENS4":3,"skill-same:01M6PJY0MYS5SSBCPE4FNHENS4":92},{"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":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":14,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":6,"updatedAt":66,"install":67,"resources":79},"01M6PJY0MYS5SSBCPE4FNHENS4","seo-technical",null,"Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".","headmktlucca-ui\u002Fneuroads-lp","headmktlucca-ui","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F247379838?v=4","01M6PDVAV6M1W96D1SR1PDF8CS","NeuroAds","01M6PDVAZ4P281GNDKD45CYTF5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fseo-technical\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,40,41,42,43,44,45,46,47,48],"seo","technical","seo technical","crawl","vitals","categories","headers","URL","technical seo audit","rendering","crawlability","across","structure","security","mobile","seo audit","data","audit","issues","core","2026-11-10 10:12:30",false,"---\nname: seo-technical\ndescription: >\n  Technical SEO audit across 9 categories: crawlability, indexability, security,\n  URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering,\n  and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\",\n  \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.2.0\"\n  category: seo\n---\n\n# Technical SEO Audit\n\n## Categories\n\n### 1. Crawlability\n- robots.txt: exists, valid, not blocking important resources\n- XML sitemap: exists, referenced in robots.txt, valid format\n- Noindex tags: intentional vs accidental\n- Crawl depth: important pages within 3 clicks of homepage\n- JavaScript rendering: check if critical content requires JS execution\n- Crawl budget: for large sites (>10k pages), efficiency matters\n\n#### AI Crawler Management\n\nAs of 2025-2026, AI companies actively crawl the web to train models and power AI search. Managing these crawlers via robots.txt is a critical technical SEO consideration.\n\n**Known AI crawlers:**\n\n| Crawler | Company | robots.txt token | Purpose |\n|---------|---------|-----------------|---------|\n| GPTBot | OpenAI | `GPTBot` | Model training |\n| ChatGPT-User | OpenAI | `ChatGPT-User` | Real-time browsing |\n| ClaudeBot | Anthropic | `ClaudeBot` | Model training |\n| PerplexityBot | Perplexity | `PerplexityBot` | Search index + training |\n| Bytespider | ByteDance | `Bytespider` | Model training |\n| Google-Extended | Google | `Google-Extended` | Gemini training (NOT search) |\n| CCBot | Common Crawl | `CCBot` | Open dataset |\n\n**Key distinctions:**\n- Blocking `Google-Extended` prevents Gemini training use but does NOT affect Google Search indexing or AI Overviews (those use `Googlebot`)\n- Blocking `GPTBot` prevents OpenAI training but does NOT prevent ChatGPT from citing your content via browsing (`ChatGPT-User`)\n- ~3-5% of websites now use AI-specific robots.txt rules\n\n**Example, selective AI crawler blocking:**\n```\n# Allow search indexing, block AI training crawlers\nUser-agent: GPTBot\nDisallow: \u002F\n\nUser-agent: Google-Extended\nDisallow: \u002F\n\nUser-agent: Bytespider\nDisallow: \u002F\n\n# Allow all other crawlers (including Googlebot for search)\nUser-agent: *\nAllow: \u002F\n```\n\n**Recommendation:** Consider your AI visibility strategy before blocking. Being cited by AI systems drives brand awareness and referral traffic. Cross-reference the `seo-geo` skill for full AI visibility optimization.\n\n### 2. Indexability\n- Canonical tags: self-referencing, no conflicts with noindex\n- Duplicate content: near-duplicates, parameter URLs, www vs non-www\n- Thin content: pages below minimum word counts per type\n- Pagination: rel=next\u002Fprev or load-more pattern\n- Hreflang: correct for multi-language\u002Fmulti-region sites\n- Index bloat: unnecessary pages consuming crawl budget\n\n### 3. Security\n- HTTPS: enforced, valid SSL certificate, no mixed content\n- Security headers:\n  - Content-Security-Policy (CSP)\n  - Strict-Transport-Security (HSTS)\n  - X-Frame-Options\n  - X-Content-Type-Options\n  - Referrer-Policy\n- HSTS preload: check preload list inclusion for high-security sites\n\n### 4. URL Structure\n- Clean URLs: descriptive, hyphenated, no query parameters for content\n- Hierarchy: logical folder structure reflecting site architecture\n- Redirects: no chains (max 1 hop), 301 for permanent moves\n- URL length: flag >100 characters\n- Trailing slashes: consistent usage\n\n### 5. Mobile Optimization\n- Responsive design: viewport meta tag, responsive CSS\n- Touch targets: minimum 48x48px with 8px spacing\n- Font size: minimum 16px base\n- No horizontal scroll\n- Mobile-first indexing: Google indexes mobile version. **Mobile-first indexing is 100% complete as of July 5, 2024.** Google now crawls and indexes ALL websites exclusively with the mobile Googlebot user-agent.\n\n### 6. Core Web Vitals\n- **LCP** (Largest Contentful Paint): target \u003C2.5s\n- **INP** (Interaction to Next Paint): target \u003C200ms\n  - INP replaced FID on March 12, 2024. FID was fully removed from all Chrome tools (CrUX API, PageSpeed Insights, Lighthouse) on September 9, 2024. Do NOT reference FID anywhere.\n- **CLS** (Cumulative Layout Shift): target \u003C0.1\n- Evaluation uses 75th percentile of real user data\n- Use PageSpeed Insights API or CrUX data if MCP available\n\n### 7. Structured Data\n- Detection: JSON-LD (preferred), Microdata, RDFa\n- Validation against Google's supported types\n- See seo-schema skill for full analysis\n\n### 8. JavaScript Rendering\n- Check if content visible in initial HTML vs requires JS\n- Identify client-side rendered (CSR) vs server-side rendered (SSR)\n- Flag SPA frameworks (React, Vue, Angular) that may cause indexing issues\n- Verify dynamic rendering setup if applicable\n\n#### JavaScript SEO: Canonical & Indexing Guidance (December 2025)\n\nGoogle updated its JavaScript SEO documentation in December 2025 with critical clarifications:\n\n1. **Canonical conflicts:** If a canonical tag in raw HTML differs from one injected by JavaScript, Google may use EITHER one. Ensure canonical tags are identical between server-rendered HTML and JS-rendered output.\n2. **noindex with JavaScript:** If raw HTML contains `\u003Cmeta name=\"robots\" content=\"noindex\">` but JavaScript removes it, Google MAY still honor the noindex from raw HTML. Serve correct robots directives in the initial HTML response.\n3. **Non-200 status codes:** Google does NOT render JavaScript on pages returning non-200 HTTP status codes. Any content or meta tags injected via JS on error pages will be invisible to Googlebot.\n4. **Structured data in JavaScript:** Product, Article, and other structured data injected via JS may face delayed processing. For time-sensitive structured data (especially e-commerce Product markup), include it in the initial server-rendered HTML.\n\n**Best practice:** Serve critical SEO elements (canonical, meta robots, structured data, title, meta description) in the initial server-rendered HTML rather than relying on JavaScript injection.\n\n### 9. IndexNow Protocol\n- Check if site supports IndexNow for Bing, Yandex, Naver\n- Supported by search engines other than Google\n- Recommend implementation for faster indexing on non-Google engines\n\n## Agent-Friendly Pages (forward-looking)\n\nAI agents (not just AI summarizers) increasingly read sites through three\nchannels: vision models on screenshots, raw HTML\u002FDOM, and the **accessibility\ntree** (the cleanest signal). Audit criteria — semantic HTML (real `\u003Cbutton>`\nand `\u003Ca>`, not `\u003Cdiv onclick>`), label associations, interactive target sizing,\nlayout stability across templates, `cursor: pointer` correctness — live in\n`references\u002Fagent-friendly-pages.md`.\n\n### Audit command\n\n```bash\n# Render with Playwright + capture accessibility tree, then score\npython3 scripts\u002Fagent_ux_check.py https:\u002F\u002Fexample.com --json\n```\n\nThe scanner outputs an Agent-UX score (0-100) plus itemized issues:\n- HTML findings: real buttons \u002F anchors, `\u003Cdiv onclick>` widgets, semantic\n  landmarks, inputs without `\u003Clabel for>`, inputs without ARIA labels\n- Accessibility tree findings: total nodes, interactive nodes, unnamed\n  interactive elements, `role=\"generic\"` ratio\n\nThe accessibility-tree snapshot uses Playwright's\n`page.accessibility.snapshot(interesting_only=False)`. To capture the tree\nwithout scoring, use `python3 scripts\u002Frender_page.py \u003Curl> --a11y-tree --json`.\n\nSurface findings as **opportunities**, not failures. The standards (WebMCP,\nagent UX heuristics) are early — don't gate audits on a sub-100 score.\n\n## Output\n\n### Technical Score: XX\u002F100\n\n### Category Breakdown\n| Category | Status | Score |\n|----------|--------|-------|\n| Crawlability | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Indexability | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Security | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| URL Structure | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Mobile | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Core Web Vitals | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Structured Data | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| JS Rendering | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| IndexNow | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n\n### Critical Issues (fix immediately)\n### High Priority (fix within 1 week)\n### Medium Priority (fix within 1 month)\n### Low Priority (backlog)\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `on_page_instant_pages` for real page analysis (status codes, page timing, broken links, on-page checks), `on_page_lighthouse` for Lighthouse audits (performance, accessibility, SEO scores), and `domain_analytics_technologies_domain_technologies` for technology stack detection.\n\n## Google API Integration (Optional)\n\nIf Google API credentials are configured, use `python3 scripts\u002Fpagespeed_check.py \u003Curl> --json` for real PSI + CrUX field data (replaces lab-only CWV estimates), `python3 scripts\u002Fcrux_history.py \u003Curl> --json` for 25-week CWV trends, and `python3 scripts\u002Fgsc_inspect.py \u003Curl> --json` for real indexation status per URL.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL, checking DNS resolution, and confirming the site is publicly accessible. |\n| robots.txt not found | Note that no robots.txt was detected at the root domain. Recommend creating one with appropriate directives. Continue audit on remaining categories. |\n| HTTPS not configured | Flag as a critical issue. Report whether HTTP is served without redirect, mixed content exists, or SSL certificate is missing\u002Fexpired. |\n| Core Web Vitals data unavailable | Note that CrUX data is not available (common for low-traffic sites). Suggest using Lighthouse lab data as a proxy and recommend increasing traffic before re-testing. |\n","# Technical SEO Audit\n\n## Categories\n\n### 1. Crawlability\n- robots.txt: exists, valid, not blocking important resources\n- XML sitemap: exists, referenced in robots.txt, valid format\n- Noindex tags: intentional vs accidental\n- Crawl depth: important pages within 3 clicks of homepage\n- JavaScript rendering: check if critical content requires JS execution\n- Crawl budget: for large sites (>10k pages), efficiency matters\n\n#### AI Crawler Management\n\nAs of 2025-2026, AI companies actively crawl the web to train models and power AI search. Managing these crawlers via robots.txt is a critical technical SEO consideration.\n\n**Known AI crawlers:**\n\n| Crawler | Company | robots.txt token | Purpose |\n|---------|---------|-----------------|---------|\n| GPTBot | OpenAI | `GPTBot` | Model training |\n| ChatGPT-User | OpenAI | `ChatGPT-User` | Real-time browsing |\n| ClaudeBot | Anthropic | `ClaudeBot` | Model training |\n| PerplexityBot | Perplexity | `PerplexityBot` | Search index + training |\n| Bytespider | ByteDance | `Bytespider` | Model training |\n| Google-Extended | Google | `Google-Extended` | Gemini training (NOT search) |\n| CCBot | Common Crawl | `CCBot` | Open dataset |\n\n**Key distinctions:**\n- Blocking `Google-Extended` prevents Gemini training use but does NOT affect Google Search indexing or AI Overviews (those use `Googlebot`)\n- Blocking `GPTBot` prevents OpenAI training but does NOT prevent ChatGPT from citing your content via browsing (`ChatGPT-User`)\n- ~3-5% of websites now use AI-specific robots.txt rules\n\n**Example, selective AI crawler blocking:**\n```\n# Allow search indexing, block AI training crawlers\nUser-agent: GPTBot\nDisallow: \u002F\n\nUser-agent: Google-Extended\nDisallow: \u002F\n\nUser-agent: Bytespider\nDisallow: \u002F\n\n# Allow all other crawlers (including Googlebot for search)\nUser-agent: *\nAllow: \u002F\n```\n\n**Recommendation:** Consider your AI visibility strategy before blocking. Being cited by AI systems drives brand awareness and referral traffic. Cross-reference the `seo-geo` skill for full AI visibility optimization.\n\n### 2. Indexability\n- Canonical tags: self-referencing, no conflicts with noindex\n- Duplicate content: near-duplicates, parameter URLs, www vs non-www\n- Thin content: pages below minimum word counts per type\n- Pagination: rel=next\u002Fprev or load-more pattern\n- Hreflang: correct for multi-language\u002Fmulti-region sites\n- Index bloat: unnecessary pages consuming crawl budget\n\n### 3. Security\n- HTTPS: enforced, valid SSL certificate, no mixed content\n- Security headers:\n  - Content-Security-Policy (CSP)\n  - Strict-Transport-Security (HSTS)\n  - X-Frame-Options\n  - X-Content-Type-Options\n  - Referrer-Policy\n- HSTS preload: check preload list inclusion for high-security sites\n\n### 4. URL Structure\n- Clean URLs: descriptive, hyphenated, no query parameters for content\n- Hierarchy: logical folder structure reflecting site architecture\n- Redirects: no chains (max 1 hop), 301 for permanent moves\n- URL length: flag >100 characters\n- Trailing slashes: consistent usage\n\n### 5. Mobile Optimization\n- Responsive design: viewport meta tag, responsive CSS\n- Touch targets: minimum 48x48px with 8px spacing\n- Font size: minimum 16px base\n- No horizontal scroll\n- Mobile-first indexing: Google indexes mobile version. **Mobile-first indexing is 100% complete as of July 5, 2024.** Google now crawls and indexes ALL websites exclusively with the mobile Googlebot user-agent.\n\n### 6. Core Web Vitals\n- **LCP** (Largest Contentful Paint): target \u003C2.5s\n- **INP** (Interaction to Next Paint): target \u003C200ms\n  - INP replaced FID on March 12, 2024. FID was fully removed from all Chrome tools (CrUX API, PageSpeed Insights, Lighthouse) on September 9, 2024. Do NOT reference FID anywhere.\n- **CLS** (Cumulative Layout Shift): target \u003C0.1\n- Evaluation uses 75th percentile of real user data\n- Use PageSpeed Insights API or CrUX data if MCP available\n\n### 7. Structured Data\n- Detection: JSON-LD (preferred), Microdata, RDFa\n- Validation against Google's supported types\n- See seo-schema skill for full analysis\n\n### 8. JavaScript Rendering\n- Check if content visible in initial HTML vs requires JS\n- Identify client-side rendered (CSR) vs server-side rendered (SSR)\n- Flag SPA frameworks (React, Vue, Angular) that may cause indexing issues\n- Verify dynamic rendering setup if applicable\n\n#### JavaScript SEO: Canonical & Indexing Guidance (December 2025)\n\nGoogle updated its JavaScript SEO documentation in December 2025 with critical clarifications:\n\n1. **Canonical conflicts:** If a canonical tag in raw HTML differs from one injected by JavaScript, Google may use EITHER one. Ensure canonical tags are identical between server-rendered HTML and JS-rendered output.\n2. **noindex with JavaScript:** If raw HTML contains `\u003Cmeta name=\"robots\" content=\"noindex\">` but JavaScript removes it, Google MAY still honor the noindex from raw HTML. Serve correct robots directives in the initial HTML response.\n3. **Non-200 status codes:** Google does NOT render JavaScript on pages returning non-200 HTTP status codes. Any content or meta tags injected via JS on error pages will be invisible to Googlebot.\n4. **Structured data in JavaScript:** Product, Article, and other structured data injected via JS may face delayed processing. For time-sensitive structured data (especially e-commerce Product markup), include it in the initial server-rendered HTML.\n\n**Best practice:** Serve critical SEO elements (canonical, meta robots, structured data, title, meta description) in the initial server-rendered HTML rather than relying on JavaScript injection.\n\n### 9. IndexNow Protocol\n- Check if site supports IndexNow for Bing, Yandex, Naver\n- Supported by search engines other than Google\n- Recommend implementation for faster indexing on non-Google engines\n\n## Agent-Friendly Pages (forward-looking)\n\nAI agents (not just AI summarizers) increasingly read sites through three\nchannels: vision models on screenshots, raw HTML\u002FDOM, and the **accessibility\ntree** (the cleanest signal). Audit criteria — semantic HTML (real `\u003Cbutton>`\nand `\u003Ca>`, not `\u003Cdiv onclick>`), label associations, interactive target sizing,\nlayout stability across templates, `cursor: pointer` correctness — live in\n`references\u002Fagent-friendly-pages.md`.\n\n### Audit command\n\n```bash\n# Render with Playwright + capture accessibility tree, then score\npython3 scripts\u002Fagent_ux_check.py https:\u002F\u002Fexample.com --json\n```\n\nThe scanner outputs an Agent-UX score (0-100) plus itemized issues:\n- HTML findings: real buttons \u002F anchors, `\u003Cdiv onclick>` widgets, semantic\n  landmarks, inputs without `\u003Clabel for>`, inputs without ARIA labels\n- Accessibility tree findings: total nodes, interactive nodes, unnamed\n  interactive elements, `role=\"generic\"` ratio\n\nThe accessibility-tree snapshot uses Playwright's\n`page.accessibility.snapshot(interesting_only=False)`. To capture the tree\nwithout scoring, use `python3 scripts\u002Frender_page.py \u003Curl> --a11y-tree --json`.\n\nSurface findings as **opportunities**, not failures. The standards (WebMCP,\nagent UX heuristics) are early — don't gate audits on a sub-100 score.\n\n## Output\n\n### Technical Score: XX\u002F100\n\n### Category Breakdown\n| Category | Status | Score |\n|----------|--------|-------|\n| Crawlability | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Indexability | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Security | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| URL Structure | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Mobile | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Core Web Vitals | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Structured Data | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| JS Rendering | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| IndexNow | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n\n### Critical Issues (fix immediately)\n### High Priority (fix within 1 week)\n### Medium Priority (fix within 1 month)\n### Low Priority (backlog)\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `on_page_instant_pages` for real page analysis (status codes, page timing, broken links, on-page checks), `on_page_lighthouse` for Lighthouse audits (performance, accessibility, SEO scores), and `domain_analytics_technologies_domain_technologies` for technology stack detection.\n\n## Google API Integration (Optional)\n\nIf Google API credentials are configured, use `python3 scripts\u002Fpagespeed_check.py \u003Curl> --json` for real PSI + CrUX field data (replaces lab-only CWV estimates), `python3 scripts\u002Fcrux_history.py \u003Curl> --json` for 25-week CWV trends, and `python3 scripts\u002Fgsc_inspect.py \u003Curl> --json` for real indexation status per URL.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL, checking DNS resolution, and confirming the site is publicly accessible. |\n| robots.txt not found | Note that no robots.txt was detected at the root domain. Recommend creating one with appropriate directives. Continue audit on remaining categories. |\n| HTTPS not configured | Flag as a critical issue. Report whether HTTP is served without redirect, mixed content exists, or SSL certificate is missing\u002Fexpired. |\n| Core Web Vitals data unavailable | Note that CrUX data is not available (common for low-traffic sites). Suggest using Lighthouse lab data as a proxy and recommend increasing traffic before re-testing. |\n",{"name":5,"license":15,"metadata":54,"description":57,"argument-hint":58,"user-invocable":59},{"author":55,"version":56,"category":29},"AgriciDaniel","2.2.0","Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".\n","[url]",true,"main","7a940b8e5af16c95e5c190a524421d32fc7445a9",".agent\u002Fskills\u002Fseo-technical","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui","https:\u002F\u002Fneuroads.com.br","2026-08-12 00:42:44",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":59},[69,72,75],{"tool":70,"command":71},"npx","npx skills add headmktlucca-ui\u002Fneuroads-lp --skill seo-technical",{"tool":73,"command":74},"bunx","bunx skills add headmktlucca-ui\u002Fneuroads-lp --skill seo-technical",{"tool":76,"command":77},"pnpm","pnpm dlx skills add headmktlucca-ui\u002Fneuroads-lp --skill seo-technical","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fseo-technical\u002FSKILL.md",[80,86],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"LICENSE.txt","LICENSE","许可证",143,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fseo-technical\u002FLICENSE.txt",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fagent-friendly-pages.md","REFERENCE","参考文档",5437,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fseo-technical\u002Freferences\u002Fagent-friendly-pages.md",[93,117,141,167,184,217],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":105,"publishedAt":49},"01M6PTDCZTXTGSTX4RFK901YSZ","xunit-skill","Generates xUnit.net tests in C#. Covers Fact\u002FTheory, constructor injection, IClassFixture, and FluentAssertions. Use when user mentions \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal\", \"C# xUnit\". Triggers on: \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal C#\", \"xUnit.net\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxunit-skill\u002FSKILL.md",[99,102],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[106,107,108,109,110,111,112,113,114,115,116],"xunit","xunit skill","testing","injection","user","use","tests","triggers","unit","unit-testing","C#",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":125,"publishedAt":49},"01M6PTCB59ZTG5FTMWGPYEMMBP","xcuitest-skill","Generates XCUITest UI tests for iOS\u002FiPadOS apps in Swift. Apple's native testing framework for reliable, fast UI automation. Supports local simulators and TestMu AI cloud real devices. Use when user mentions \"XCUITest\", \"XCTest\", \"iOS UI test\", \"Swift test\", \"XCUIApplication\". Triggers on: \"XCUITest\", \"XCTest UI\", \"iOS UI test\", \"Swift UI test\", \"XCUIApplication\", \"TestMu\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxcuitest-skill\u002FSKILL.md",[123,124],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},[126,127,108,128,129,130,131,132,111,43,133,134,135,136,112,113,137,138,139,140],"xcuitest","xcuitest skill","automation","test","testing framework","ios","devices","mobile-testing","ui test","local","apple","apps","native","for","objective",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":151,"publishedAt":49},"01M6PTATMNTY9NF4J7KSR76YK6","world-builder","Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworld-builder\u002FSKILL.md",[147,150],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},[152,153,154,155,156,157,158,159,111,160,161,162,163,164,165,139,166],"builder","world","world builder","MCP","create","mcp tools","Tools","game","pokemon","manage","style","via","theme","zone","generative",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":175,"publishedAt":49},"01M6PT9Z92JTSQEHE1QR0NNW5F","webdriverio-skill","Generates WebdriverIO (WDIO) automation tests in JavaScript or TypeScript. Supports local and TestMu AI cloud. Use when user mentions \"WebdriverIO\", \"WDIO\", \"wdio.conf\", \"browser.url\", \"$\", \"$$\". Triggers on: \"WebdriverIO\", \"WDIO\", \"wdio\", \"browser.$\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebdriverio-skill\u002FSKILL.md",[173,174],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},[176,108,177,128,178,179,180,181,110,111,182,135,112,113,36,183],"webdriverio skill","typescript","javascript","browser","cloud","e2e","e2e-testing","conf",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":197,"publishedAt":49},"01M6PT9NVK36ZWCQ69YXK3FR4K","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb\u002FSKILL.md",[190,193,194],{"categoryNo":191,"categoryName":192,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":195,"categoryName":196,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,113,216],"design","web","guidelines","web design guidelines","web design","css","performance","components","web components","tasks","code","web performance","ui","platform design","html","responsive design","responsive","platform","implementing",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":225,"publishedAt":49},"01M6PT9A3JKRE3X34276F2FW5R","watchos-design-guidelines","Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwatchos\u002FSKILL.md",[223,224],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":195,"categoryName":196,"taxonomyType":26,"taxonomyTypeDesc":27},[198,200,226,207,210,111,227,228,136,215,229,113,137,230,139,231,232],"watchos design guidelines","workout","human","watch","interface","platform-design","features"]