[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBAT8AFDXPF88Z4RXWHWPG":3,"skill-same:01M7CBAT8AFDXPF88Z4RXWHWPG":56},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CBAT8AFDXPF88Z4RXWHWPG","sf-docs",null,"Official Salesforce documentation retrieval guidance. Use when you need authoritative Salesforce docs from developer.salesforce.com or help.salesforce.com, especially when pages are JS-heavy, shell-rendered, or hard to extract with naive fetching.","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\u002Fjaganpro-sf-skills\u002Fsf-docs\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-docs\ndescription: >\n  Official Salesforce documentation retrieval guidance. Use when you need\n  authoritative Salesforce docs from developer.salesforce.com or\n  help.salesforce.com, especially when pages are JS-heavy, shell-rendered, or\n  hard to extract with naive fetching.\nlicense: MIT\nmetadata:\n  version: \"0.4.0\"\n  author: \"Jag Valaiyapathy\"\n---\n\n# sf-docs\n\nUse this skill to retrieve and ground answers in **official Salesforce documentation on the public web**.\n\nThis skill is intentionally simple:\n- **no local corpus**\n- **no indexing**\n- **no benchmark workflow**\n- **no helper CLI dependency**\n- **no PDF fallback**\n\nIts job is to provide a **reliable online retrieval playbook** for Salesforce docs that are hard to fetch, especially `help.salesforce.com`, JS-heavy `developer.salesforce.com`, Lightning Design System docs on `lightningdesignsystem.com`, and other official Salesforce-owned doc pages such as `architect.salesforce.com` and `admin.salesforce.com`.\n\nAn optional wrapper script is available at:\n- `skills\u002Fsf-docs\u002Fscripts\u002Fextract_salesforce_doc.py`\n\nIt automatically routes `help.salesforce.com` URLs into the dedicated Help extractor and supports other official documentation pages such as `*.salesforce.com` and `lightningdesignsystem.com` through a generic browser-rendered path. For bot-sensitive pages, it also supports best-effort optional stealth mode via `--stealth` when `playwright-stealth` is installed.\n\nThe dedicated Help extractor is also available directly at:\n- `skills\u002Fsf-docs\u002Fscripts\u002Fextract_help_salesforce.py`\n\n## Core Goal\n\nFind the best official Salesforce HTML page online and extract enough real content to answer confidently.\n\nIf the evidence is weak, say so clearly instead of forcing a weak answer.\n\n## When to Use\n\nUse `sf-docs` when a user asks for:\n- official Salesforce documentation\n- Apex, API, LWC, metadata, Agentforce, setup, or help articles\n- docs from `developer.salesforce.com`\n- docs from `help.salesforce.com`\n- pages that look JS-heavy, shell-rendered, or difficult to read with ordinary fetches\n\n## Official Sources Only\n\nPrefer Salesforce-owned documentation sources:\n- `developer.salesforce.com`\n- `help.salesforce.com`\n- `architect.salesforce.com`\n- `admin.salesforce.com`\n- `lightningdesignsystem.com`\n- other relevant official Salesforce documentation pages when Salesforce uses them as the source of truth\n\nAvoid third-party blogs, videos, or summary articles unless the user explicitly asks for them.\n\nDo **not** fall back to PDFs.\n\n## Retrieval Workflow\n\n### 1. Classify the request first\n\nBefore fetching anything, identify the likely doc family.\n\n| Family | Typical Source | Use For |\n|---|---|---|\n| Developer docs | `developer.salesforce.com\u002Fdocs\u002F...` | Apex, APIs, LWC, metadata, Agentforce developer docs |\n| Help docs | `help.salesforce.com\u002F...` | setup, admin, product configuration |\n| Architect\u002FAdmin docs | `architect.salesforce.com\u002F...`, `admin.salesforce.com\u002F...` | best practices, patterns, well-architected guidance, admin enablement |\n| Design system docs | `lightningdesignsystem.com\u002F...` | SLDS, Cosmos, design tokens, component and styling guidance |\n| Legacy atlas docs | `developer.salesforce.com\u002Fdocs\u002Fatlas.en-us.*` | older official guide and reference docs |\n\n### 2. Identify the exact concept\n\nExtract the real target before you search:\n- exact API\u002Fclass\u002Fmethod name\n- exact feature name\n- exact product phrase\n- exact setup concept\n\nExamples:\n- `Lightning Message Service`\n- `Wire Service`\n- `System.StubProvider`\n- `Agentforce Actions`\n- `Messaging for In-App and Web allowed domains`\n\n### 3. Prefer targeted official retrieval\n\nDo **not** broad-crawl Salesforce docs.\n\nInstead:\n1. identify the most likely official guide root or article\n2. if search is needed, restrict it to official Salesforce domains only\n3. fetch that official page\n4. check whether the **exact concept actually appears on the page**\n5. if not, inspect and follow the most relevant **1–3 official child links**\n6. stop once you have grounded evidence\n\n### 4. Do not stop at broad landing pages\n\nA guide landing page is **not enough** unless it clearly contains the exact requested concept.\n\nThis is especially important for:\n- LWC docs\n- Agentforce docs\n- broad platform guide homepages\n- help landing pages that link to the real article\n\n### 5. For `developer.salesforce.com`\n\nUse this playbook:\n- start with the most likely official guide root\n- if the page is JS-heavy, prefer browser-rendered extraction\n- check whether the exact concept appears on the page\n- if the concept is missing, inspect official child links and follow the best matching 1–3 links\n- prefer exact concept pages over broad guide roots\n- legacy atlas pages are valid if they are the real official reference for the concept\n\n### 6. For `help.salesforce.com`\n\nHelp pages often fail with naive fetching.\n\nUse this playbook:\n- prefer exact `articleView?id=...` URLs when available\n- use browser-rendered extraction when plain fetch returns shell content\n- treat outputs like `Loading`, `Sorry to interrupt`, `CSS Error`, or mostly chrome\u002Fnavigation text as **failed extraction**, not evidence\n- look for the **real article body**, not just header, nav, or footer text\n- reject shell pages and soft-404 pages such as:\n  - \"We looked high and low but couldn't find that page\"\n  - generic empty help shells\n- if starting from a nearby guide or hub page, follow linked Help articles until you reach the real article body\n- if extraction still fails after targeted retries, return the best official Help URLs you found and explicitly say that article-body extraction was unsuccessful\n\n## Acceptance Rules\n\nA page is good enough to answer from only when at least one of these is true:\n- the exact identifier appears on the page\n- the exact concept phrase appears on the page\n- multiple query-specific phrases appear in the correct official context\n\nA page is **not** good enough when:\n- it is only a broad landing page\n- it is a shell page with little real article text\n- it is from the wrong product area\n- it does not contain the requested identifier or concept\n- it is a third-party explanation when an official page should exist\n\n## Rejection Rules\n\nReject these as final evidence:\n- broad guide homepages without the exact concept\n- release notes when a concept\u002Freference page is expected\n- admin blog posts when developer docs are requested\n- third-party blogs when official docs are available\n- shell-rendered pages with no real article body\n- pages whose titles sound right but whose body does not contain the requested concept\n\n## Grounding Requirements\n\nWhen answering, include:\n1. guide\u002Farticle title\n2. exact official URL\n3. source type:\n   - developer doc page\n   - atlas reference page\n   - help article page\n4. any caveat if extraction was partial or browser-rendered\n\nIf evidence is weak, say so plainly.\n\n## Examples\n\n### Example: Lightning Message Service\nDo **not** stop at the general LWC guide root.\nFind the exact LWC page for Lightning Message Service or follow the most relevant child links from the LWC docs until the exact concept appears.\n\n### Example: Wire Service\nDo **not** answer from the LWC homepage unless `Wire Service` is actually present there.\nFollow the relevant child doc page for wire service or wire adapters.\n\n### Example: Agentforce Actions\nDo **not** answer from a broad Agentforce landing page or a blog post.\nFind the official Agentforce developer page for actions, or follow the best matching child pages from the official Agentforce docs.\n\n### Example: Messaging for In-App and Web allowed domains\nPrefer official Help articles and browser-rendered extraction.\nReject generic help shells. Follow linked Help articles from nearby official messaging docs if needed.\n\n### Example: System.StubProvider\nPrefer the official Salesforce reference\u002Fdeveloper page where the exact identifier appears.\nDo not substitute a broader Apex landing page if the identifier is absent.\n\n## Non-Goals\n\nThis skill should **not**:\n- maintain a local documentation corpus\n- rely on a local index\n- use PDF fallback\n- run benchmark workflows\n- depend on repo-specific scripts to be useful\n\n## Cross-Skill Role\n\nOther `sf-*` skills should use `sf-docs` when they need authoritative Salesforce documentation instead of relying on generic search alone.\n","# sf-docs\n\nUse this skill to retrieve and ground answers in **official Salesforce documentation on the public web**.\n\nThis skill is intentionally simple:\n- **no local corpus**\n- **no indexing**\n- **no benchmark workflow**\n- **no helper CLI dependency**\n- **no PDF fallback**\n\nIts job is to provide a **reliable online retrieval playbook** for Salesforce docs that are hard to fetch, especially `help.salesforce.com`, JS-heavy `developer.salesforce.com`, Lightning Design System docs on `lightningdesignsystem.com`, and other official Salesforce-owned doc pages such as `architect.salesforce.com` and `admin.salesforce.com`.\n\nAn optional wrapper script is available at:\n- `skills\u002Fsf-docs\u002Fscripts\u002Fextract_salesforce_doc.py`\n\nIt automatically routes `help.salesforce.com` URLs into the dedicated Help extractor and supports other official documentation pages such as `*.salesforce.com` and `lightningdesignsystem.com` through a generic browser-rendered path. For bot-sensitive pages, it also supports best-effort optional stealth mode via `--stealth` when `playwright-stealth` is installed.\n\nThe dedicated Help extractor is also available directly at:\n- `skills\u002Fsf-docs\u002Fscripts\u002Fextract_help_salesforce.py`\n\n## Core Goal\n\nFind the best official Salesforce HTML page online and extract enough real content to answer confidently.\n\nIf the evidence is weak, say so clearly instead of forcing a weak answer.\n\n## When to Use\n\nUse `sf-docs` when a user asks for:\n- official Salesforce documentation\n- Apex, API, LWC, metadata, Agentforce, setup, or help articles\n- docs from `developer.salesforce.com`\n- docs from `help.salesforce.com`\n- pages that look JS-heavy, shell-rendered, or difficult to read with ordinary fetches\n\n## Official Sources Only\n\nPrefer Salesforce-owned documentation sources:\n- `developer.salesforce.com`\n- `help.salesforce.com`\n- `architect.salesforce.com`\n- `admin.salesforce.com`\n- `lightningdesignsystem.com`\n- other relevant official Salesforce documentation pages when Salesforce uses them as the source of truth\n\nAvoid third-party blogs, videos, or summary articles unless the user explicitly asks for them.\n\nDo **not** fall back to PDFs.\n\n## Retrieval Workflow\n\n### 1. Classify the request first\n\nBefore fetching anything, identify the likely doc family.\n\n| Family | Typical Source | Use For |\n|---|---|---|\n| Developer docs | `developer.salesforce.com\u002Fdocs\u002F...` | Apex, APIs, LWC, metadata, Agentforce developer docs |\n| Help docs | `help.salesforce.com\u002F...` | setup, admin, product configuration |\n| Architect\u002FAdmin docs | `architect.salesforce.com\u002F...`, `admin.salesforce.com\u002F...` | best practices, patterns, well-architected guidance, admin enablement |\n| Design system docs | `lightningdesignsystem.com\u002F...` | SLDS, Cosmos, design tokens, component and styling guidance |\n| Legacy atlas docs | `developer.salesforce.com\u002Fdocs\u002Fatlas.en-us.*` | older official guide and reference docs |\n\n### 2. Identify the exact concept\n\nExtract the real target before you search:\n- exact API\u002Fclass\u002Fmethod name\n- exact feature name\n- exact product phrase\n- exact setup concept\n\nExamples:\n- `Lightning Message Service`\n- `Wire Service`\n- `System.StubProvider`\n- `Agentforce Actions`\n- `Messaging for In-App and Web allowed domains`\n\n### 3. Prefer targeted official retrieval\n\nDo **not** broad-crawl Salesforce docs.\n\nInstead:\n1. identify the most likely official guide root or article\n2. if search is needed, restrict it to official Salesforce domains only\n3. fetch that official page\n4. check whether the **exact concept actually appears on the page**\n5. if not, inspect and follow the most relevant **1–3 official child links**\n6. stop once you have grounded evidence\n\n### 4. Do not stop at broad landing pages\n\nA guide landing page is **not enough** unless it clearly contains the exact requested concept.\n\nThis is especially important for:\n- LWC docs\n- Agentforce docs\n- broad platform guide homepages\n- help landing pages that link to the real article\n\n### 5. For `developer.salesforce.com`\n\nUse this playbook:\n- start with the most likely official guide root\n- if the page is JS-heavy, prefer browser-rendered extraction\n- check whether the exact concept appears on the page\n- if the concept is missing, inspect official child links and follow the best matching 1–3 links\n- prefer exact concept pages over broad guide roots\n- legacy atlas pages are valid if they are the real official reference for the concept\n\n### 6. For `help.salesforce.com`\n\nHelp pages often fail with naive fetching.\n\nUse this playbook:\n- prefer exact `articleView?id=...` URLs when available\n- use browser-rendered extraction when plain fetch returns shell content\n- treat outputs like `Loading`, `Sorry to interrupt`, `CSS Error`, or mostly chrome\u002Fnavigation text as **failed extraction**, not evidence\n- look for the **real article body**, not just header, nav, or footer text\n- reject shell pages and soft-404 pages such as:\n  - \"We looked high and low but couldn't find that page\"\n  - generic empty help shells\n- if starting from a nearby guide or hub page, follow linked Help articles until you reach the real article body\n- if extraction still fails after targeted retries, return the best official Help URLs you found and explicitly say that article-body extraction was unsuccessful\n\n## Acceptance Rules\n\nA page is good enough to answer from only when at least one of these is true:\n- the exact identifier appears on the page\n- the exact concept phrase appears on the page\n- multiple query-specific phrases appear in the correct official context\n\nA page is **not** good enough when:\n- it is only a broad landing page\n- it is a shell page with little real article text\n- it is from the wrong product area\n- it does not contain the requested identifier or concept\n- it is a third-party explanation when an official page should exist\n\n## Rejection Rules\n\nReject these as final evidence:\n- broad guide homepages without the exact concept\n- release notes when a concept\u002Freference page is expected\n- admin blog posts when developer docs are requested\n- third-party blogs when official docs are available\n- shell-rendered pages with no real article body\n- pages whose titles sound right but whose body does not contain the requested concept\n\n## Grounding Requirements\n\nWhen answering, include:\n1. guide\u002Farticle title\n2. exact official URL\n3. source type:\n   - developer doc page\n   - atlas reference page\n   - help article page\n4. any caveat if extraction was partial or browser-rendered\n\nIf evidence is weak, say so plainly.\n\n## Examples\n\n### Example: Lightning Message Service\nDo **not** stop at the general LWC guide root.\nFind the exact LWC page for Lightning Message Service or follow the most relevant child links from the LWC docs until the exact concept appears.\n\n### Example: Wire Service\nDo **not** answer from the LWC homepage unless `Wire Service` is actually present there.\nFollow the relevant child doc page for wire service or wire adapters.\n\n### Example: Agentforce Actions\nDo **not** answer from a broad Agentforce landing page or a blog post.\nFind the official Agentforce developer page for actions, or follow the best matching child pages from the official Agentforce docs.\n\n### Example: Messaging for In-App and Web allowed domains\nPrefer official Help articles and browser-rendered extraction.\nReject generic help shells. Follow linked Help articles from nearby official messaging docs if needed.\n\n### Example: System.StubProvider\nPrefer the official Salesforce reference\u002Fdeveloper page where the exact identifier appears.\nDo not substitute a broader Apex landing page if the identifier is absent.\n\n## Non-Goals\n\nThis skill should **not**:\n- maintain a local documentation corpus\n- rely on a local index\n- use PDF fallback\n- run benchmark workflows\n- depend on repo-specific scripts to be useful\n\n## Cross-Skill Role\n\nOther `sf-*` skills should use `sf-docs` when they need authoritative Salesforce documentation instead of relying on generic search alone.\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"Jag Valaiyapathy","0.4.0","Official Salesforce documentation retrieval guidance. Use when you need authoritative Salesforce docs from developer.salesforce.com or help.salesforce.com, especially when pages are JS-heavy, shell-rendered, or hard to extract with naive fetching.\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-docs",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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-docs",{"tool":42,"command":43},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-docs",{"tool":45,"command":46},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-docs\u002FSkill.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"metadata.json","REFERENCE","参考文档",403,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-docs\u002Fmetadata.json",[57,64,69,76,81,88],{"skillNo":58,"name":59,"nameZh":6,"description":60,"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},"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":65,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"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},"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":77,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"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},"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":89,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]