[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BNEEQYYRCABX5F4CDJ0FQ":3,"skill-same:01M71BNEEQYYRCABX5F4CDJ0FQ":74},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M71BNEEQYYRCABX5F4CDJ0FQ","wiki-page-writer",null,"Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.","strmt7\u002Fai_skills_collection_benchmarked","strmt7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28989754?v=4","01M71929P914SWKQ7QJV24NBBY","Stratos","01M71929Q9VGKQ7PWYR95VSQQQ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fcloud-azure-microsoft-sdks\u002Fofficial-vendor-reference\u002Fwiki-page-writer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"wiki page writer","wiki","page","writer","writing documentation","when","depth","dark","rich","mode","pages","deep","first-principles","writing","diagrams","use","technical","Citations","code","components","2026-11-10 10:12:30",false,"---\nname: wiki-page-writer\ndescription: Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.0\"\n---\n\n# Wiki Page Writer\n\nYou are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.\n\n## When to Activate\n\n- User asks to document a specific component, system, or feature\n- User wants a technical deep-dive with diagrams\n- A wiki catalogue section needs its content generated\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore generating any page, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## Depth Requirements (NON-NEGOTIABLE)\n\n1. **TRACE ACTUAL CODE PATHS** — Do not guess from file names. Read the implementation.\n2. **EVERY CLAIM NEEDS A SOURCE** — File path + function\u002Fclass name.\n3. **DISTINGUISH FACT FROM INFERENCE** — If you read the code, say so. If inferring, mark it.\n4. **FIRST PRINCIPLES** — Explain WHY something exists before WHAT it does.\n5. **NO HAND-WAVING** — Don't say \"this likely handles...\" — read the code.\n\n## Procedure\n\n1. **Plan**: Determine scope, audience, and documentation budget based on file count\n2. **Analyze**: Read all relevant files; identify patterns, algorithms, dependencies, data flow\n3. **Write**: Generate structured Markdown with diagrams and citations\n4. **Validate**: Verify file paths exist, class names are accurate, Mermaid renders correctly\n\n## Mandatory Requirements\n\n### VitePress Frontmatter\nEvery page must have:\n```\n---\ntitle: \"Page Title\"\ndescription: \"One-line description\"\n---\n```\n\n### Mermaid Diagrams\n- **Minimum 3–5 per page** (scaled by scope: small=3, medium=4, large=5+)\n- **Use at least 2 different diagram types** — don't repeat the same type. Mix `graph`, `sequenceDiagram`, `classDiagram`, `stateDiagram-v2`, `erDiagram`, `flowchart` as appropriate\n- Use `autonumber` in all `sequenceDiagram` blocks\n- **Dark-mode colors (MANDATORY)**: node fills `#2d333b`, borders `#6d5dfc`, text `#e6edf3`\n- Subgraph backgrounds: `#161b22`, borders `#30363d`, lines `#8b949e`\n- If using inline `style`, use dark fills with `,color:#e6edf3`\n- Do NOT use `\u003Cbr\u002F>` (use `\u003Cbr>` or line breaks)\n- **Diagram selection**: structure → graph; behavior → sequence\u002Fstate; data → ER; decisions → flowchart\n\n### Citations\n- Every non-trivial claim needs a citation with the resolved format:\n  - **Remote repo**: `[src\u002Fpath\u002Ffile.ts:42](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42)`\n  - **Local repo**: `(src\u002Fpath\u002Ffile.ts:42)`\n  - **Line ranges**: `[src\u002Fpath\u002Ffile.ts:42-58](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42-L58)`\n- Minimum 5 different source files cited per page\n- If evidence is missing: `(Unknown – verify in path\u002Fto\u002Fcheck)`\n- **Mermaid diagrams**: Add a `\u003C!-- Sources: file_path:line, file_path:line -->` comment block immediately after each diagram\n- **Tables**: Include a \"Source\" column with linked citations when listing components, APIs, or configurations\n\n### Structure\n- Overview (explain WHY) → Architecture → Components → Data Flow → Implementation → References → Related Pages\n- **Use tables aggressively** — prefer tables over prose for any structured information (APIs, configs, components, comparisons)\n- **Summary tables first**: Start each major section with an at-a-glance summary table before details\n- Use comparison tables when introducing technologies or patterns — always compare side-by-side\n- Include a \"Source\" column with linked citations in tables listing code artifacts\n- Use bold for key terms, inline code for identifiers and paths\n- Include pseudocode in a familiar language when explaining complex code paths\n- **Progressive disclosure**: Start with the big picture, then drill into specifics — don't front-load details\n\n### Cross-References Between Wiki Pages\n- **Inline links**: When mentioning a concept, component, or pattern covered on another wiki page, link to it inline using relative Markdown links: `[Component Name](..\u002FNN-section\u002Fpage-name.md)` or `[Section Title](..\u002FNN-section\u002Fpage-name.md#heading-anchor)`\n- **Related Pages section**: End every page with a \"Related Pages\" section listing connected wiki pages:\n  ```markdown\n  ## Related Pages\n\n  | Page | Relationship |\n  |------|-------------|\n  | [Authentication](..\u002F02-architecture\u002Fauthentication.md) | Handles token validation used by this API |\n  | [Data Models](..\u002F03-data-layer\u002Fmodels.md) | Defines the entities processed here |\n  | [Contributor Guide](..\u002Fonboarding\u002Fcontributor-guide.md) | Setup instructions for this module |\n  ```\n- **Link format**: Use relative paths from the current file — VitePress resolves `.md` links to routes automatically\n- **Anchor links**: Link to specific sections with `#kebab-case-heading` anchors (e.g., `[error handling](..\u002F02-architecture\u002Foverview.md#error-handling)`)\n- **Bidirectional where possible**: If page A links to page B, page B should link back to page A\n\n### VitePress Compatibility\n- Escape bare generics outside code fences: `` `List\u003CT>` `` not bare `List\u003CT>`\n- No `\u003Cbr\u002F>` in Mermaid blocks\n- All hex colors must be 3 or 6 digits\n","# Wiki Page Writer\n\nYou are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.\n\n## When to Activate\n\n- User asks to document a specific component, system, or feature\n- User wants a technical deep-dive with diagrams\n- A wiki catalogue section needs its content generated\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore generating any page, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## Depth Requirements (NON-NEGOTIABLE)\n\n1. **TRACE ACTUAL CODE PATHS** — Do not guess from file names. Read the implementation.\n2. **EVERY CLAIM NEEDS A SOURCE** — File path + function\u002Fclass name.\n3. **DISTINGUISH FACT FROM INFERENCE** — If you read the code, say so. If inferring, mark it.\n4. **FIRST PRINCIPLES** — Explain WHY something exists before WHAT it does.\n5. **NO HAND-WAVING** — Don't say \"this likely handles...\" — read the code.\n\n## Procedure\n\n1. **Plan**: Determine scope, audience, and documentation budget based on file count\n2. **Analyze**: Read all relevant files; identify patterns, algorithms, dependencies, data flow\n3. **Write**: Generate structured Markdown with diagrams and citations\n4. **Validate**: Verify file paths exist, class names are accurate, Mermaid renders correctly\n\n## Mandatory Requirements\n\n### VitePress Frontmatter\nEvery page must have:\n```\n---\ntitle: \"Page Title\"\ndescription: \"One-line description\"\n---\n```\n\n### Mermaid Diagrams\n- **Minimum 3–5 per page** (scaled by scope: small=3, medium=4, large=5+)\n- **Use at least 2 different diagram types** — don't repeat the same type. Mix `graph`, `sequenceDiagram`, `classDiagram`, `stateDiagram-v2`, `erDiagram`, `flowchart` as appropriate\n- Use `autonumber` in all `sequenceDiagram` blocks\n- **Dark-mode colors (MANDATORY)**: node fills `#2d333b`, borders `#6d5dfc`, text `#e6edf3`\n- Subgraph backgrounds: `#161b22`, borders `#30363d`, lines `#8b949e`\n- If using inline `style`, use dark fills with `,color:#e6edf3`\n- Do NOT use `\u003Cbr\u002F>` (use `\u003Cbr>` or line breaks)\n- **Diagram selection**: structure → graph; behavior → sequence\u002Fstate; data → ER; decisions → flowchart\n\n### Citations\n- Every non-trivial claim needs a citation with the resolved format:\n  - **Remote repo**: `[src\u002Fpath\u002Ffile.ts:42](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42)`\n  - **Local repo**: `(src\u002Fpath\u002Ffile.ts:42)`\n  - **Line ranges**: `[src\u002Fpath\u002Ffile.ts:42-58](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42-L58)`\n- Minimum 5 different source files cited per page\n- If evidence is missing: `(Unknown – verify in path\u002Fto\u002Fcheck)`\n- **Mermaid diagrams**: Add a `\u003C!-- Sources: file_path:line, file_path:line -->` comment block immediately after each diagram\n- **Tables**: Include a \"Source\" column with linked citations when listing components, APIs, or configurations\n\n### Structure\n- Overview (explain WHY) → Architecture → Components → Data Flow → Implementation → References → Related Pages\n- **Use tables aggressively** — prefer tables over prose for any structured information (APIs, configs, components, comparisons)\n- **Summary tables first**: Start each major section with an at-a-glance summary table before details\n- Use comparison tables when introducing technologies or patterns — always compare side-by-side\n- Include a \"Source\" column with linked citations in tables listing code artifacts\n- Use bold for key terms, inline code for identifiers and paths\n- Include pseudocode in a familiar language when explaining complex code paths\n- **Progressive disclosure**: Start with the big picture, then drill into specifics — don't front-load details\n\n### Cross-References Between Wiki Pages\n- **Inline links**: When mentioning a concept, component, or pattern covered on another wiki page, link to it inline using relative Markdown links: `[Component Name](..\u002FNN-section\u002Fpage-name.md)` or `[Section Title](..\u002FNN-section\u002Fpage-name.md#heading-anchor)`\n- **Related Pages section**: End every page with a \"Related Pages\" section listing connected wiki pages:\n  ```markdown\n  ## Related Pages\n\n  | Page | Relationship |\n  |------|-------------|\n  | [Authentication](..\u002F02-architecture\u002Fauthentication.md) | Handles token validation used by this API |\n  | [Data Models](..\u002F03-data-layer\u002Fmodels.md) | Defines the entities processed here |\n  | [Contributor Guide](..\u002Fonboarding\u002Fcontributor-guide.md) | Setup instructions for this module |\n  ```\n- **Link format**: Use relative paths from the current file — VitePress resolves `.md` links to routes automatically\n- **Anchor links**: Link to specific sections with `#kebab-case-heading` anchors (e.g., `[error handling](..\u002F02-architecture\u002Foverview.md#error-handling)`)\n- **Bidirectional where possible**: If page A links to page B, page B should link back to page A\n\n### VitePress Compatibility\n- Escape bare generics outside code fences: `` `List\u003CT>` `` not bare `List\u003CT>`\n- No `\u003Cbr\u002F>` in Mermaid blocks\n- All hex colors must be 3 or 6 digits\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"version":46},"Microsoft","1.0.0","main","5c95bcac4646c5aed06bd9aed5235cfc7985aafc","included\u002Fskills\u002Fby-category\u002Fcloud-azure-microsoft-sdks\u002Fofficial-vendor-reference\u002Fwiki-page-writer",0,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked","https:\u002F\u002Fgithub.com\u002Fstrmt7","2026-11-11 04:18:12",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add strmt7\u002Fai_skills_collection_benchmarked --skill wiki-page-writer",{"tool":60,"command":61},"bunx","bunx skills add strmt7\u002Fai_skills_collection_benchmarked --skill wiki-page-writer",{"tool":63,"command":64},"pnpm","pnpm dlx skills add strmt7\u002Fai_skills_collection_benchmarked --skill wiki-page-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fcloud-azure-microsoft-sdks\u002Fofficial-vendor-reference\u002Fwiki-page-writer\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Facceptance-criteria.md","REFERENCE","参考文档",2254,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fcloud-azure-microsoft-sdks\u002Fofficial-vendor-reference\u002Fwiki-page-writer\u002Freferences\u002Facceptance-criteria.md",[75,109,138,163,187,213],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":91,"publishedAt":39},"01M71D4H3T6M57DFKN8HENAWRV","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fwebapp-testing\u002FSKILL.md",[83,88],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000009","前端开发",[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"webapp","testing","webapp testing","for","applications","local","frontend","debugging","toolkit","logs","browser","with","playwright","web","behavior","ui","screenshots",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":39},"01M71D4CQR2A2TB7GASCR5ZBG3","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fskill-creator-anthropics\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fskill-creator-anthropics\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000023","Skill与智能体开发",[120,121,122,123,124,125,24,126,127,128,129,130,131,132,133,134,135,136,95,137],"skill creator","creator","performance","improve","run evals","new","analysis","create","optimize","variance analysis","run","edit","benchmark","a skill","existing skill","evals","modify","accuracy",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":146,"publishedAt":39},"01M71D488XHEZVXXSXFYP8ENMH","playwright-skill","Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web functionality, or perform browser-based testing.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Flatest-release-browser-automation\u002Fplaywright-skill\u002FSKILL.md",[144,145],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":117,"categoryName":118,"taxonomyType":86,"taxonomyTypeDesc":87},[104,147,148,149,93,150,151,24,152,102,153,154,155,156,157,158,159,160,161,162],"playwright skill","browser automation","flows","auto","access","Bash","website","ux","login","scripts","read","write","node","install","network","responsive",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":171,"publishedAt":39},"01M71CY25GM939M6RES91QSG3T","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Fweb-artifacts-builder\u002FSKILL.md",[170],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},[172,173,174,105,175,176,177,95,178,179,98,180,34,181,38,182,183,184,185,186],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","react","multi","state","routing","state management",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":191,"sourceHtmlUrl":192,"categories":193,"keywords":203,"publishedAt":39},"01M71CXZB60QJJ1H4S3NN94WMZ","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Ffrontend-design\u002FSKILL.md",[194,195,198],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":196,"categoryName":197,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":199,"categoryName":200,"taxonomyType":201,"taxonomyTypeDesc":202},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[98,204,205,177,206,207,208,96,209,29,34,24,174,37,38,210,182,211,212,103],"design","frontend design","ui design","generic","aesthetics","landing","web ui","react components","examples",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":39},"01M71CVZ54WFBTVA7R16PFY1ZE","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fzarr-python\u002FSKILL.md",[],[220,221,222,223,224,225,226,227,228,95,229,230,231,232,233,234,235,236],"zarr python","python","zarr","arrays","Cloud Storage","scientific","storage","parallel","dask","numpy","gcs","s3","integration","scientific computing","cloud","scale","pipelines"]