[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C0JYB3WJZJHSVSPAQABV4N":3,"skill-same:01M6C0JYB3WJZJHSVSPAQABV4N":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":33,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":9,"updatedAt":59,"install":60,"resources":73},"01M6C0JYB3WJZJHSVSPAQABV4N","website-audit",null,"Audits a website for SEO, AI search performance, structured data, mobile usability, broken links, and social media cards. Fixes issues found. Use when the user mentions \"audit website\", \"SEO\", \"fix search ranking\", \"AI search\", \"structured data\", \"social media cards\", or \"website performance\".","Nimblesite\u002FDataProvider","Nimblesite","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F178527684?v=4","01M6C0JCTZP0TRD8TD5ASTA0HY","01M6C0JD0KFR7H2S3JVJ0D031N",68,"MIT","https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebsite-audit\u002FSKILL.md",[17,22,25,30],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":31,"categoryName":32,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000035","市场营销",[34,35,36,37,38,39,40,41,42,43,44,45],"website","audit","website audit","structured data","performance","issues","search","data","seo","Media","social media","broken","2026-11-10 10:12:30",false,"---\nname: website-audit\ndescription: Audits a website for SEO, AI search performance, structured data, mobile usability, broken links, and social media cards. Fixes issues found. Use when the user mentions \"audit website\", \"SEO\", \"fix search ranking\", \"AI search\", \"structured data\", \"social media cards\", or \"website performance\".\n---\n\u003C!-- agent-pmo:795a9c2 -->\n\n# Website Audit\n\nPerforms a comprehensive website audit and fixes issues affecting search visibility and AI discoverability.\n\nThis repo's website lives in `Website\u002F` and is built with **Eleventy** (`eleventy.config.js`) plus DocFX for API docs. Templates and content sources live under `Website\u002Fsrc\u002F`; generated output is `Website\u002F_site\u002F` (do NOT edit `_site\u002F` directly).\n\nCopy this checklist and track your progress:\n\n```\nAudit Progress:\n- [ ] Step 1: Read guidelines\n- [ ] Step 2: Audit AI search readiness\n- [ ] Step 3: Audit SEO and keywords\n- [ ] Step 4: Audit crawling and indexing\n- [ ] Step 5: Audit broken links and canonicalization\n- [ ] Step 6: Audit mobile usability\n- [ ] Step 7: Audit structured data\n- [ ] Step 8: Audit social media cards\n- [ ] Step 9: Audit For Unsubstantiated Claims\n- [ ] Step 10: Audit Design Compliance\n- [ ] Step 11: Test with Playwright\n- [ ] Step 12: Report findings\n```\n\n- Check the outputted HTML\u002FCSS\u002FJavaScript AFTER the website is generated by Eleventy. Don't just check the static content before the website is generated.\n- Fix issues at the core where the static content templates are stored (`Website\u002Fsrc\u002F`) — not in the outputted HTML (`Website\u002F_site\u002F`).\n- Never manually edit `Website\u002F_site\u002F`.\n- ENSURE THE FOOTER HAS A copyright link to nimblesite.co\n\n## Step 1 — Read guidelines\n\nFetch and read each of these before auditing. These are the authoritative references for every step that follows.\n\n- [Google's guidance on using generative AI content](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fusing-gen-ai-content)\n- [Top ways to ensure content performs well in Google's AI experiences](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fblog\u002F2025\u002F05\u002Fsucceeding-in-ai-search)\n- [SEO Starter Guide](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fseo-starter-guide)\n\nIf the repo has a business plan doc, take it into account. The DataProvider\u002FLQL specs under `docs\u002Fspecs\u002F` describe the product's value propositions — pull factual claims from there.\n\nIdentify the website source files in `Website\u002Fsrc\u002F`. The framework is Eleventy (templates as `.njk`\u002F`.md` under `Website\u002Fsrc\u002F_includes\u002F`, data files under `Website\u002Fsrc\u002F_data\u002F`).\n\n## Step 2 — Audit AI search readiness\n\nApply the guidance from the AI search article. Check:\n\n1. **Content quality** — Is content original, expert-level, and comprehensive? Flag thin or duplicated pages.\n2. **Clear structure** — Do pages use descriptive headings, lists, and concise answers to likely questions?\n3. **Entity clarity** — Are key terms (LQL, DataProvider, source generator, transpiler, sync, RBAC, WebAuthn) defined clearly so AI can extract them?\n4. **Freshness signals** — Are dates, update timestamps, and authorship present?\n\nFix issues directly in the source files (`Website\u002Fsrc\u002F`). For each fix, note what changed and why.\n\n## Step 3 — Audit SEO and keywords\n\n1. Search [Google Trends](https:\u002F\u002Ftrends.google.com\u002Fhome) for trending keywords related to \"C# source generator\", \"SQL safe queries\", \"offline sync\", \"ORM alternative\", \"type-safe SQL\".\n2. Review each page's `\u003Ctitle>`, `\u003Cmeta name=\"description\">`, and `\u003Ch1>` tags.\n3. Check for keyword opportunities — can trending terms be naturally inserted into headings, descriptions, or body content?\n4. Verify each page has a unique, descriptive title (50-60 chars) and meta description (150-160 chars).\n5. Check image `alt` attributes describe the image content and include relevant keywords where natural.\n\nApply the [SEO Starter Guide](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fseo-starter-guide) principles. Fix issues directly in `Website\u002Fsrc\u002F`.\n\n## Step 4 — Audit crawling and indexing\n\nReference: [Overview of crawling and indexing topics](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing)\n\n1. **robots.txt** — `Website\u002Fsrc\u002Frobots.txt` (passed through to `_site\u002Frobots.txt`). Verify it doesn't block important pages. Reference: [robots.txt spec](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Frobots-txt).\n2. **Sitemap** — generated by `Website\u002Fsrc\u002Fsitemap.njk`. Verify all important pages are listed and no dead URLs are included. Reference: [Sitemap guidelines](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Fsitemaps\u002Flarge-sitemaps).\n3. **Meta robots tags** — Check Eleventy templates for unintended `noindex` or `nofollow` directives on pages that should be indexed.\n\nNote: edit the generators (`robots.txt`, `sitemap.njk`), not the rendered output.\n\n## Step 5 — Audit broken links and canonicalization\n\nReference: [What is canonicalization](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Fcanonicalization)\n\n1. Check all internal links resolve to valid pages (no 404s).\n2. Verify `\u003Clink rel=\"canonical\">` tags are present and point to the correct URL.\n3. Check for duplicate content accessible via multiple URLs (with\u002Fwithout trailing slash, www vs non-www).\n4. Verify redirects use 301 (permanent) not 302 (temporary) where appropriate.\n\n## Step 6 — Audit mobile usability\n\nReference: [Mobile-first indexing best practices](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Fmobile\u002Fmobile-sites-mobile-first-indexing)\n\n1. Verify the `\u003Cmeta name=\"viewport\">` tag is present and correctly configured.\n2. Check that content is identical between mobile and desktop (mobile-first indexing requires this).\n3. Verify touch targets are adequately sized (min 48x48px).\n4. Check font sizes are readable without zooming (min 16px body text).\n\n## Step 7 — Audit structured data\n\nReference: [Structured data guidelines](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fsd-policies)\n\n1. Check for existing JSON-LD `\u003Cscript type=\"application\u002Fld+json\">` blocks in `Website\u002Fsrc\u002F_includes\u002F`.\n2. Verify the structured data matches the page content (no misleading markup).\n3. Add missing structured data where appropriate:\n   - **Organization\u002FPerson** on the homepage\n   - **Article\u002FBlogPosting** on blog posts (with author, datePublished, dateModified)\n   - **BreadcrumbList** for navigation\n   - **FAQ** for pages with question\u002Fanswer content\n   - **SoftwareSourceCode** for the docs API pages\n4. Validate JSON-LD syntax is correct.\n\n## Step 8 — Audit social media cards\n\nReference: [Implementing Social Media Preview Cards](https:\u002F\u002Fdocumentation.platformos.com\u002Fuse-cases\u002Fimplementing-social-media-preview-cards)\n\nCheck every page template includes:\n\n**Open Graph (Facebook\u002FLinkedIn):**\n- `og:title`, `og:description`, `og:image`, `og:url`, `og:type`\n\n**Twitter Card:**\n- `twitter:card`, `twitter:title`, `twitter:description`, `twitter:image`\n\nVerify `og:image` dimensions are at least 1200x630px. Fix missing or incomplete tags.\n\n## Step 9 - Audit For Unsubstantiated Claims\n\nEnsure that all claims are backed up with a link to a reputable source. As an example, this claim isn't valid as content unless it links to an authority that found this through research\n\n> Research shows teams with strong DevEx perform 4-5x better across speed, quality, and engagement\n\nSearch for the authoritative URL and add a link to the URL. If it is not available, change the claim to something that can be substatiated.\n\n## Step 10 — Audit Design Compliance\n\nRead the design system specs (`docs\u002Fspecs\u002Fdataprovider-design-system.md`, `docs\u002Fspecs\u002Flql-design-system.md`) and view the design screens in `Website\u002FDesigns\u002F` (`HomePage.png`, `APIDoc.png`, `BlogsPage.png`).\n\n## Step 11 — Test with Playwright\n\nThe repo already has Playwright configured at `Website\u002Fplaywright.config.ts`. Build and run the website locally:\n\n```bash\ncd Website && npm run build && npm run start\n```\n\nThen run the configured tests, or drive the site manually with the playwright MCP tools.\n\n**Desktop tests (1280x720):**\n\n1. Navigate to the homepage — take a screenshot.\n2. Navigate to each major section (docs, blog, API docs) — verify pages load without errors.\n3. Check the browser console for JavaScript errors.\n4. Verify all navigation links work.\n\n**Mobile tests (375x667, iPhone SE):**\n\n1. Resize the browser to mobile dimensions.\n2. Navigate to the homepage — take a screenshot.\n3. Verify the layout is responsive (no horizontal overflow, readable text).\n4. Test navigation menu (hamburger menu if applicable).\n\nIf any page fails to load or has console errors, fix the issue and retest.\n\n## Step 12 — Report findings\n\nSummarize the audit results:\n\n```\n## Website Audit Report\n\n### Fixed\n- [List each issue fixed with file and line reference]\n\n### Warnings (manual review needed)\n- [Issues that need human judgment]\n\n### Passed\n- [Areas that passed audit with no issues]\n\n### Screenshots\n- [Reference Playwright screenshots taken]\n```\n\n## Rules\n\n- **Fix issues directly** — don't just report them. Only flag issues as warnings when they require human judgment (e.g., content tone, keyword selection).\n- **One step at a time** — complete each step before moving to the next.\n- **Preserve existing content** — improve structure and metadata without rewriting the author's voice.\n- **No keyword stuffing** — keywords must read naturally in context.\n- **Respect the framework** — edit `Website\u002Fsrc\u002F` templates and `eleventy.config.js`, never edit `Website\u002F_site\u002F` generated output.\n","\u003C!-- agent-pmo:795a9c2 -->\n\n# Website Audit\n\nPerforms a comprehensive website audit and fixes issues affecting search visibility and AI discoverability.\n\nThis repo's website lives in `Website\u002F` and is built with **Eleventy** (`eleventy.config.js`) plus DocFX for API docs. Templates and content sources live under `Website\u002Fsrc\u002F`; generated output is `Website\u002F_site\u002F` (do NOT edit `_site\u002F` directly).\n\nCopy this checklist and track your progress:\n\n```\nAudit Progress:\n- [ ] Step 1: Read guidelines\n- [ ] Step 2: Audit AI search readiness\n- [ ] Step 3: Audit SEO and keywords\n- [ ] Step 4: Audit crawling and indexing\n- [ ] Step 5: Audit broken links and canonicalization\n- [ ] Step 6: Audit mobile usability\n- [ ] Step 7: Audit structured data\n- [ ] Step 8: Audit social media cards\n- [ ] Step 9: Audit For Unsubstantiated Claims\n- [ ] Step 10: Audit Design Compliance\n- [ ] Step 11: Test with Playwright\n- [ ] Step 12: Report findings\n```\n\n- Check the outputted HTML\u002FCSS\u002FJavaScript AFTER the website is generated by Eleventy. Don't just check the static content before the website is generated.\n- Fix issues at the core where the static content templates are stored (`Website\u002Fsrc\u002F`) — not in the outputted HTML (`Website\u002F_site\u002F`).\n- Never manually edit `Website\u002F_site\u002F`.\n- ENSURE THE FOOTER HAS A copyright link to nimblesite.co\n\n## Step 1 — Read guidelines\n\nFetch and read each of these before auditing. These are the authoritative references for every step that follows.\n\n- [Google's guidance on using generative AI content](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fusing-gen-ai-content)\n- [Top ways to ensure content performs well in Google's AI experiences](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fblog\u002F2025\u002F05\u002Fsucceeding-in-ai-search)\n- [SEO Starter Guide](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fseo-starter-guide)\n\nIf the repo has a business plan doc, take it into account. The DataProvider\u002FLQL specs under `docs\u002Fspecs\u002F` describe the product's value propositions — pull factual claims from there.\n\nIdentify the website source files in `Website\u002Fsrc\u002F`. The framework is Eleventy (templates as `.njk`\u002F`.md` under `Website\u002Fsrc\u002F_includes\u002F`, data files under `Website\u002Fsrc\u002F_data\u002F`).\n\n## Step 2 — Audit AI search readiness\n\nApply the guidance from the AI search article. Check:\n\n1. **Content quality** — Is content original, expert-level, and comprehensive? Flag thin or duplicated pages.\n2. **Clear structure** — Do pages use descriptive headings, lists, and concise answers to likely questions?\n3. **Entity clarity** — Are key terms (LQL, DataProvider, source generator, transpiler, sync, RBAC, WebAuthn) defined clearly so AI can extract them?\n4. **Freshness signals** — Are dates, update timestamps, and authorship present?\n\nFix issues directly in the source files (`Website\u002Fsrc\u002F`). For each fix, note what changed and why.\n\n## Step 3 — Audit SEO and keywords\n\n1. Search [Google Trends](https:\u002F\u002Ftrends.google.com\u002Fhome) for trending keywords related to \"C# source generator\", \"SQL safe queries\", \"offline sync\", \"ORM alternative\", \"type-safe SQL\".\n2. Review each page's `\u003Ctitle>`, `\u003Cmeta name=\"description\">`, and `\u003Ch1>` tags.\n3. Check for keyword opportunities — can trending terms be naturally inserted into headings, descriptions, or body content?\n4. Verify each page has a unique, descriptive title (50-60 chars) and meta description (150-160 chars).\n5. Check image `alt` attributes describe the image content and include relevant keywords where natural.\n\nApply the [SEO Starter Guide](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fseo-starter-guide) principles. Fix issues directly in `Website\u002Fsrc\u002F`.\n\n## Step 4 — Audit crawling and indexing\n\nReference: [Overview of crawling and indexing topics](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing)\n\n1. **robots.txt** — `Website\u002Fsrc\u002Frobots.txt` (passed through to `_site\u002Frobots.txt`). Verify it doesn't block important pages. Reference: [robots.txt spec](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Frobots-txt).\n2. **Sitemap** — generated by `Website\u002Fsrc\u002Fsitemap.njk`. Verify all important pages are listed and no dead URLs are included. Reference: [Sitemap guidelines](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Fsitemaps\u002Flarge-sitemaps).\n3. **Meta robots tags** — Check Eleventy templates for unintended `noindex` or `nofollow` directives on pages that should be indexed.\n\nNote: edit the generators (`robots.txt`, `sitemap.njk`), not the rendered output.\n\n## Step 5 — Audit broken links and canonicalization\n\nReference: [What is canonicalization](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Fcanonicalization)\n\n1. Check all internal links resolve to valid pages (no 404s).\n2. Verify `\u003Clink rel=\"canonical\">` tags are present and point to the correct URL.\n3. Check for duplicate content accessible via multiple URLs (with\u002Fwithout trailing slash, www vs non-www).\n4. Verify redirects use 301 (permanent) not 302 (temporary) where appropriate.\n\n## Step 6 — Audit mobile usability\n\nReference: [Mobile-first indexing best practices](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Fmobile\u002Fmobile-sites-mobile-first-indexing)\n\n1. Verify the `\u003Cmeta name=\"viewport\">` tag is present and correctly configured.\n2. Check that content is identical between mobile and desktop (mobile-first indexing requires this).\n3. Verify touch targets are adequately sized (min 48x48px).\n4. Check font sizes are readable without zooming (min 16px body text).\n\n## Step 7 — Audit structured data\n\nReference: [Structured data guidelines](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fstructured-data\u002Fsd-policies)\n\n1. Check for existing JSON-LD `\u003Cscript type=\"application\u002Fld+json\">` blocks in `Website\u002Fsrc\u002F_includes\u002F`.\n2. Verify the structured data matches the page content (no misleading markup).\n3. Add missing structured data where appropriate:\n   - **Organization\u002FPerson** on the homepage\n   - **Article\u002FBlogPosting** on blog posts (with author, datePublished, dateModified)\n   - **BreadcrumbList** for navigation\n   - **FAQ** for pages with question\u002Fanswer content\n   - **SoftwareSourceCode** for the docs API pages\n4. Validate JSON-LD syntax is correct.\n\n## Step 8 — Audit social media cards\n\nReference: [Implementing Social Media Preview Cards](https:\u002F\u002Fdocumentation.platformos.com\u002Fuse-cases\u002Fimplementing-social-media-preview-cards)\n\nCheck every page template includes:\n\n**Open Graph (Facebook\u002FLinkedIn):**\n- `og:title`, `og:description`, `og:image`, `og:url`, `og:type`\n\n**Twitter Card:**\n- `twitter:card`, `twitter:title`, `twitter:description`, `twitter:image`\n\nVerify `og:image` dimensions are at least 1200x630px. Fix missing or incomplete tags.\n\n## Step 9 - Audit For Unsubstantiated Claims\n\nEnsure that all claims are backed up with a link to a reputable source. As an example, this claim isn't valid as content unless it links to an authority that found this through research\n\n> Research shows teams with strong DevEx perform 4-5x better across speed, quality, and engagement\n\nSearch for the authoritative URL and add a link to the URL. If it is not available, change the claim to something that can be substatiated.\n\n## Step 10 — Audit Design Compliance\n\nRead the design system specs (`docs\u002Fspecs\u002Fdataprovider-design-system.md`, `docs\u002Fspecs\u002Flql-design-system.md`) and view the design screens in `Website\u002FDesigns\u002F` (`HomePage.png`, `APIDoc.png`, `BlogsPage.png`).\n\n## Step 11 — Test with Playwright\n\nThe repo already has Playwright configured at `Website\u002Fplaywright.config.ts`. Build and run the website locally:\n\n```bash\ncd Website && npm run build && npm run start\n```\n\nThen run the configured tests, or drive the site manually with the playwright MCP tools.\n\n**Desktop tests (1280x720):**\n\n1. Navigate to the homepage — take a screenshot.\n2. Navigate to each major section (docs, blog, API docs) — verify pages load without errors.\n3. Check the browser console for JavaScript errors.\n4. Verify all navigation links work.\n\n**Mobile tests (375x667, iPhone SE):**\n\n1. Resize the browser to mobile dimensions.\n2. Navigate to the homepage — take a screenshot.\n3. Verify the layout is responsive (no horizontal overflow, readable text).\n4. Test navigation menu (hamburger menu if applicable).\n\nIf any page fails to load or has console errors, fix the issue and retest.\n\n## Step 12 — Report findings\n\nSummarize the audit results:\n\n```\n## Website Audit Report\n\n### Fixed\n- [List each issue fixed with file and line reference]\n\n### Warnings (manual review needed)\n- [Issues that need human judgment]\n\n### Passed\n- [Areas that passed audit with no issues]\n\n### Screenshots\n- [Reference Playwright screenshots taken]\n```\n\n## Rules\n\n- **Fix issues directly** — don't just report them. Only flag issues as warnings when they require human judgment (e.g., content tone, keyword selection).\n- **One step at a time** — complete each step before moving to the next.\n- **Preserve existing content** — improve structure and metadata without rewriting the author's voice.\n- **No keyword stuffing** — keywords must read naturally in context.\n- **Respect the framework** — edit `Website\u002Fsrc\u002F` templates and `eleventy.config.js`, never edit `Website\u002F_site\u002F` generated output.\n",{"name":5,"description":7},"main","52a3bb1b0b693dd04699b77cbfb8dfbe4befdec0",".agents\u002Fskills\u002Fwebsite-audit",4,"https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider","https:\u002F\u002Flql.dev\u002F","https:\u002F\u002Fgithub.com\u002FNimblesite","https:\u002F\u002Fwww.nimblesite.co\u002F","2026-11-12 16:20:42",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Nimblesite\u002FDataProvider --skill website-audit",{"tool":66,"command":67},"bunx","bunx skills add Nimblesite\u002FDataProvider --skill website-audit",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Nimblesite\u002FDataProvider --skill website-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebsite-audit\u002FSKILL.md",true,[],[75,82,96,110,124,138],{"skillNo":76,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":81,"publishedAt":46},"01M6C0KDKYAKZ8W4KCZZCGW4YN","https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebsite-audit\u002FSKILL.md",[79,80],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":31,"categoryName":32,"taxonomyType":28,"taxonomyTypeDesc":29},[36,35,34,40,37,38,39,41,42,43,44,45],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":46},"01M6C0KBQHTHM3Q8FTDZHVHHPQ","upgrade-packages","Upgrade all dependencies\u002Fpackages to their latest versions for the detected language(s). Use when the user says \"upgrade packages\", \"update dependencies\", \"bump versions\", \"update packages\", or \"upgrade deps\".","https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupgrade-packages\u002FSKILL.md",[],[89,90,91,92,93,94,95],"upgrade packages","packages","update","package","deps","check","update dependencies",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":46},"01M6C0K9V6V43P869Q52DGDECN","submit-pr","Creates a pull request with a well-structured description after verifying CI passes. Use when the user asks to submit, create, or open a pull request.","https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsubmit-pr\u002FSKILL.md",[],[103,104,105,106,107,108,109],"submit pr","pr","pull request","create","pull","ci","open",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":46},"01M6C0K7RTZMBVC01CZ6HKBP1C","spec-check","Audit spec\u002Fplan documents against the codebase. Ensures every spec section has implementing code, tests, and matching logic. Use when the user says \"check specs\", \"spec audit\", or \"verify specs\".","https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspec-check\u002FSKILL.md",[],[117,94,118,119,120,121,35,122,123],"spec check","spec","documents","implementing code","code","verify","plan",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":46},"01M6C0K5HF3W1KN1J6K4PAQZ8V","fix-bug","Fix a bug using test-driven development. Use when the user reports a bug, describes unexpected behavior, wants to fix a defect, or says something is broken. Enforces a strict test-first workflow where a failing test must be written and verified before any fix is attempted.","https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffix-bug\u002FSKILL.md",[],[131,132,133,134,45,135,136,137],"fix bug","first","grep","Bash","development","test","workflow",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":46},"01M6C0K3SD41A9H3E3NEYFXK9P","code-dedup","Searches for duplicate code, duplicate tests, and dead code, then safely merges or removes them. Use when the user says \"deduplicate\", \"find duplicates\", \"remove dead code\", \"DRY up\", or \"code dedup\". Requires test coverage — refuses to touch untested code.","https:\u002F\u002Fgithub.com\u002FNimblesite\u002FDataProvider\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcode-dedup\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师",[121,148,149,150,151,136],"code dedup","find","dead code","deduplicate"]