[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWM2F062BNEDBTT0E2CCNP":3,"skill-same:01M7BWM2F062BNEDBTT0E2CCNP":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7BWM2F062BNEDBTT0E2CCNP","mintlify",null,"Comprehensive reference for building Mintlify documentation sites. Use when creating pages, configuring docs.json, adding components, setting up navigation, or working with API references. Routes to detailed reference files for all components and configuration options.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fcodewithshreyans-skills\u002Fmintlify\u002Fskills\u002Fmintlify\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mintlify\ndescription: Comprehensive reference for building Mintlify documentation sites. Use when creating pages, configuring docs.json, adding components, setting up navigation, or working with API references. Routes to detailed reference files for all components and configuration options.\nlicense: MIT\ncompatibility: Works with any Mintlify documentation project. Requires docs.json configuration file.\nmetadata:\n  author: Mintlify\n  url: https:\u002F\u002Fmintlify.com\n  version: \"0.2\"\n---\n\n# Mintlify reference\n\nReference for building documentation with Mintlify. This file covers essentials that apply to every task. For detailed reference on specific topics, read the files listed in the reference index below.\n\n## Reference index\n\nRead these files **only when your task requires them**. They are in the `reference\u002F` directory next to this file. To find them, look in the same directory as this skill file (e.g., `.claude\u002Fskills\u002Fmintlify\u002Freference\u002F`).\n\n| File | When to read |\n|------|-------------|\n| `reference\u002Fcomponents.md` | Adding or modifying components (callouts, cards, steps, tabs, accordions, code groups, fields, frames, icons, tooltips, badges, trees, mermaid, panels, prompts, colors, tiles, updates, views). |\n| `reference\u002Fconfiguration.md` | Changing docs.json settings (theme, colors, logo, fonts, appearance, navbar, footer, banner, redirects, SEO, integrations, API config). Also covers snippets, hidden pages, .mintignore, custom CSS\u002FJS, and the complete frontmatter fields table. |\n| `reference\u002Fnavigation.md` | Modifying site navigation structure (groups, tabs, anchors, dropdowns, products, versions, languages, OpenAPI in nav). |\n| `reference\u002Fapi-docs.md` | Setting up API documentation (OpenAPI, AsyncAPI, MDX manual API pages, extensions, playground config). |\n\n## Before you start\n\nRead the project's `docs.json` file first. It defines the site's navigation, theme, colors, and configuration.\n\nSearch for existing content before creating new pages. You may need to update an existing page, add a section, or link to existing content rather than duplicating.\n\nRead 2-3 similar pages to match the site's voice, structure, and formatting.\n\n## File format\n\nMintlify uses MDX files (`.mdx` or `.md`) with YAML frontmatter.\n\n```\nproject\u002F\n├── docs.json           # Site configuration (required)\n├── index.mdx\n├── quickstart.mdx\n├── guides\u002F\n│   └── example.mdx\n├── openapi.yml         # API specification (optional)\n├── images\u002F             # Static assets\n│   └── example.png\n└── snippets\u002F           # Reusable components\n    └── component.jsx\n```\n\n### File naming\n\n- Match existing patterns in the directory\n- If no existing files or mixed file naming patterns, use kebab-case: `getting-started.mdx`\n- Add new pages to `docs.json` navigation or they won't appear in the sidebar\n\n### Internal links\n\n- Use root-relative paths without file extensions: `\u002Fgetting-started\u002Fquickstart`\n- Do not use relative paths (`..\u002F`) or absolute URLs for internal pages\n\n### Images\n\nStore images in an `images\u002F` directory. Reference with root-relative paths. All images require descriptive alt text.\n\n```mdx\n![Dashboard showing analytics overview](\u002Fimages\u002Fdashboard.png)\n```\n\n## Page frontmatter\n\nEvery page requires `title` in its frontmatter. Include `description` and `keywords` for SEO.\n\n```yaml\n---\ntitle: \"Clear, descriptive title\"\ndescription: \"Concise summary for SEO and navigation.\"\nkeywords: [\"relevant\", \"search\", \"terms\"]\n---\n```\n\n### Common frontmatter fields\n\n| Field | Type | Required | Description |\n|-------|------|----------|-------------|\n| `title` | string | Yes | Page title in navigation and browser tabs. |\n| `description` | string | No | Brief description for SEO. Displays under the title. |\n| `sidebarTitle` | string | No | Short title for sidebar navigation. |\n| `icon` | string | No | Lucide, Font Awesome, or Tabler icon name. Also accepts a URL or file path. |\n| `tag` | string | No | Label next to page title in sidebar (e.g., \"NEW\"). |\n| `hidden` | boolean | No | Remove from sidebar. Page still accessible by URL. |\n| `mode` | string | No | Page layout: `default`, `wide`, `custom`, `frame`, `center`. |\n| `keywords` | array | No | Search terms for internal search and SEO. |\n| `api` | string | No | API endpoint for interactive playground (e.g., `\"POST \u002Fusers\"`). |\n| `openapi` | string | No | OpenAPI endpoint reference (e.g., `\"GET \u002Fendpoint\"`). |\n\n## Quick component reference\n\nBelow are the most commonly used components. For full props and all 24 components, read `reference\u002Fcomponents.md`.\n\n### Callouts\n\n```mdx\n\u003CNote>Supplementary information, safe to skip.\u003C\u002FNote>\n\u003CInfo>Helpful context such as permissions or prerequisites.\u003C\u002FInfo>\n\u003CTip>Recommendations or best practices.\u003C\u002FTip>\n\u003CWarning>Potentially destructive actions or important caveats.\u003C\u002FWarning>\n\u003CCheck>Success confirmation or completed status.\u003C\u002FCheck>\n\u003CDanger>Critical warnings about data loss or breaking changes.\u003C\u002FDanger>\n```\n\n### Steps\n\n```mdx\n\u003CSteps>\n  \u003CStep title=\"First step\">\n    Instructions for step one.\n  \u003C\u002FStep>\n  \u003CStep title=\"Second step\">\n    Instructions for step two.\n  \u003C\u002FStep>\n\u003C\u002FSteps>\n```\n\n### Tabs and code groups\n\n```mdx\n\u003CTabs>\n  \u003CTab title=\"npm\">\n    ```bash\n    npm install package-name\n    ```\n  \u003C\u002FTab>\n  \u003CTab title=\"yarn\">\n    ```bash\n    yarn add package-name\n    ```\n  \u003C\u002FTab>\n\u003C\u002FTabs>\n```\n\n```mdx\n\u003CCodeGroup>\n\n```javascript example.js\nconst greeting = \"Hello, world!\";\n```\n\n```python example.py\ngreeting = \"Hello, world!\"\n```\n\n\u003C\u002FCodeGroup>\n```\n\n### Cards and columns\n\n```mdx\n\u003CColumns cols={2}>\n  \u003CCard title=\"First card\" icon=\"rocket\" href=\"\u002Fquickstart\">\n    Card description text.\n  \u003C\u002FCard>\n  \u003CCard title=\"Second card\" icon=\"book\" href=\"\u002Fguides\">\n    Card description text.\n  \u003C\u002FCard>\n\u003C\u002FColumns>\n```\n\nUse `\u003CColumns>` to arrange cards (or other content) in a grid. `cols` accepts 1-4.\n\n### Accordions\n\n```mdx\n\u003CAccordionGroup>\n  \u003CAccordion title=\"First section\">Content one.\u003C\u002FAccordion>\n  \u003CAccordion title=\"Second section\">Content two.\u003C\u002FAccordion>\n\u003C\u002FAccordionGroup>\n```\n\n## CLI commands\n\n- `npm i -g mint` — Install the Mintlify CLI.\n- `mint dev` — Local preview at localhost:3000.\n- `mint broken-links` — Check internal links.\n- `mint a11y` — Check for accessibility issues.\n- `mint validate` — Validate documentation builds.\n- `mint upgrade` — Upgrade from `mint.json` to `docs.json`.\n\n## Writing standards\n\n- Second-person voice (\"you\").\n- Active voice, direct language.\n- Sentence case for headings (\"Getting started\", not \"Getting Started\").\n- Sentence case for code block titles.\n- All code blocks must have language tags.\n- All images must have descriptive alt text.\n- No marketing language, filler phrases, or emoji.\n- Keep code examples simple, practical, and tested.\n\n## Common mistakes\n\n- Missing language tag on a code block (use ` ```python `, not ` ``` `).\n- Using relative paths (`..\u002Fpage`) instead of root-relative (`\u002Fsection\u002Fpage`).\n- Forgetting to add new pages to `docs.json` navigation.\n- Images without alt text.\n- Adding file extensions to internal links (`\u002Fpage.mdx` instead of `\u002Fpage`).\n","# Mintlify reference\n\nReference for building documentation with Mintlify. This file covers essentials that apply to every task. For detailed reference on specific topics, read the files listed in the reference index below.\n\n## Reference index\n\nRead these files **only when your task requires them**. They are in the `reference\u002F` directory next to this file. To find them, look in the same directory as this skill file (e.g., `.claude\u002Fskills\u002Fmintlify\u002Freference\u002F`).\n\n| File | When to read |\n|------|-------------|\n| `reference\u002Fcomponents.md` | Adding or modifying components (callouts, cards, steps, tabs, accordions, code groups, fields, frames, icons, tooltips, badges, trees, mermaid, panels, prompts, colors, tiles, updates, views). |\n| `reference\u002Fconfiguration.md` | Changing docs.json settings (theme, colors, logo, fonts, appearance, navbar, footer, banner, redirects, SEO, integrations, API config). Also covers snippets, hidden pages, .mintignore, custom CSS\u002FJS, and the complete frontmatter fields table. |\n| `reference\u002Fnavigation.md` | Modifying site navigation structure (groups, tabs, anchors, dropdowns, products, versions, languages, OpenAPI in nav). |\n| `reference\u002Fapi-docs.md` | Setting up API documentation (OpenAPI, AsyncAPI, MDX manual API pages, extensions, playground config). |\n\n## Before you start\n\nRead the project's `docs.json` file first. It defines the site's navigation, theme, colors, and configuration.\n\nSearch for existing content before creating new pages. You may need to update an existing page, add a section, or link to existing content rather than duplicating.\n\nRead 2-3 similar pages to match the site's voice, structure, and formatting.\n\n## File format\n\nMintlify uses MDX files (`.mdx` or `.md`) with YAML frontmatter.\n\n```\nproject\u002F\n├── docs.json           # Site configuration (required)\n├── index.mdx\n├── quickstart.mdx\n├── guides\u002F\n│   └── example.mdx\n├── openapi.yml         # API specification (optional)\n├── images\u002F             # Static assets\n│   └── example.png\n└── snippets\u002F           # Reusable components\n    └── component.jsx\n```\n\n### File naming\n\n- Match existing patterns in the directory\n- If no existing files or mixed file naming patterns, use kebab-case: `getting-started.mdx`\n- Add new pages to `docs.json` navigation or they won't appear in the sidebar\n\n### Internal links\n\n- Use root-relative paths without file extensions: `\u002Fgetting-started\u002Fquickstart`\n- Do not use relative paths (`..\u002F`) or absolute URLs for internal pages\n\n### Images\n\nStore images in an `images\u002F` directory. Reference with root-relative paths. All images require descriptive alt text.\n\n```mdx\n![Dashboard showing analytics overview](\u002Fimages\u002Fdashboard.png)\n```\n\n## Page frontmatter\n\nEvery page requires `title` in its frontmatter. Include `description` and `keywords` for SEO.\n\n```yaml\n---\ntitle: \"Clear, descriptive title\"\ndescription: \"Concise summary for SEO and navigation.\"\nkeywords: [\"relevant\", \"search\", \"terms\"]\n---\n```\n\n### Common frontmatter fields\n\n| Field | Type | Required | Description |\n|-------|------|----------|-------------|\n| `title` | string | Yes | Page title in navigation and browser tabs. |\n| `description` | string | No | Brief description for SEO. Displays under the title. |\n| `sidebarTitle` | string | No | Short title for sidebar navigation. |\n| `icon` | string | No | Lucide, Font Awesome, or Tabler icon name. Also accepts a URL or file path. |\n| `tag` | string | No | Label next to page title in sidebar (e.g., \"NEW\"). |\n| `hidden` | boolean | No | Remove from sidebar. Page still accessible by URL. |\n| `mode` | string | No | Page layout: `default`, `wide`, `custom`, `frame`, `center`. |\n| `keywords` | array | No | Search terms for internal search and SEO. |\n| `api` | string | No | API endpoint for interactive playground (e.g., `\"POST \u002Fusers\"`). |\n| `openapi` | string | No | OpenAPI endpoint reference (e.g., `\"GET \u002Fendpoint\"`). |\n\n## Quick component reference\n\nBelow are the most commonly used components. For full props and all 24 components, read `reference\u002Fcomponents.md`.\n\n### Callouts\n\n```mdx\n\u003CNote>Supplementary information, safe to skip.\u003C\u002FNote>\n\u003CInfo>Helpful context such as permissions or prerequisites.\u003C\u002FInfo>\n\u003CTip>Recommendations or best practices.\u003C\u002FTip>\n\u003CWarning>Potentially destructive actions or important caveats.\u003C\u002FWarning>\n\u003CCheck>Success confirmation or completed status.\u003C\u002FCheck>\n\u003CDanger>Critical warnings about data loss or breaking changes.\u003C\u002FDanger>\n```\n\n### Steps\n\n```mdx\n\u003CSteps>\n  \u003CStep title=\"First step\">\n    Instructions for step one.\n  \u003C\u002FStep>\n  \u003CStep title=\"Second step\">\n    Instructions for step two.\n  \u003C\u002FStep>\n\u003C\u002FSteps>\n```\n\n### Tabs and code groups\n\n```mdx\n\u003CTabs>\n  \u003CTab title=\"npm\">\n    ```bash\n    npm install package-name\n    ```\n  \u003C\u002FTab>\n  \u003CTab title=\"yarn\">\n    ```bash\n    yarn add package-name\n    ```\n  \u003C\u002FTab>\n\u003C\u002FTabs>\n```\n\n```mdx\n\u003CCodeGroup>\n\n```javascript example.js\nconst greeting = \"Hello, world!\";\n```\n\n```python example.py\ngreeting = \"Hello, world!\"\n```\n\n\u003C\u002FCodeGroup>\n```\n\n### Cards and columns\n\n```mdx\n\u003CColumns cols={2}>\n  \u003CCard title=\"First card\" icon=\"rocket\" href=\"\u002Fquickstart\">\n    Card description text.\n  \u003C\u002FCard>\n  \u003CCard title=\"Second card\" icon=\"book\" href=\"\u002Fguides\">\n    Card description text.\n  \u003C\u002FCard>\n\u003C\u002FColumns>\n```\n\nUse `\u003CColumns>` to arrange cards (or other content) in a grid. `cols` accepts 1-4.\n\n### Accordions\n\n```mdx\n\u003CAccordionGroup>\n  \u003CAccordion title=\"First section\">Content one.\u003C\u002FAccordion>\n  \u003CAccordion title=\"Second section\">Content two.\u003C\u002FAccordion>\n\u003C\u002FAccordionGroup>\n```\n\n## CLI commands\n\n- `npm i -g mint` — Install the Mintlify CLI.\n- `mint dev` — Local preview at localhost:3000.\n- `mint broken-links` — Check internal links.\n- `mint a11y` — Check for accessibility issues.\n- `mint validate` — Validate documentation builds.\n- `mint upgrade` — Upgrade from `mint.json` to `docs.json`.\n\n## Writing standards\n\n- Second-person voice (\"you\").\n- Active voice, direct language.\n- Sentence case for headings (\"Getting started\", not \"Getting Started\").\n- Sentence case for code block titles.\n- All code blocks must have language tags.\n- All images must have descriptive alt text.\n- No marketing language, filler phrases, or emoji.\n- Keep code examples simple, practical, and tested.\n\n## Common mistakes\n\n- Missing language tag on a code block (use ` ```python `, not ` ``` `).\n- Using relative paths (`..\u002Fpage`) instead of root-relative (`\u002Fsection\u002Fpage`).\n- Forgetting to add new pages to `docs.json` navigation.\n- Images without alt text.\n- Adding file extensions to internal links (`\u002Fpage.mdx` instead of `\u002Fpage`).\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"url":25,"author":26,"version":27},"https:\u002F\u002Fmintlify.com","Mintlify","0.2","Works with any Mintlify documentation project. Requires docs.json configuration file.","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fcodewithshreyans-skills\u002Fmintlify\u002Fskills\u002Fmintlify",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill mintlify",{"tool":43,"command":44},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill mintlify",{"tool":46,"command":47},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill mintlify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fcodewithshreyans-skills\u002Fmintlify\u002Fskills\u002Fmintlify\u002FSKILL.md",true,[],[52,59,64,71,76,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":60,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":72,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":84,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]