[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPPHAFNHT4YXFQ90VHH8FK":3,"skill-same:01M7CPPHAFNHT4YXFQ90VHH8FK":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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":49},"01M7CPPHAFNHT4YXFQ90VHH8FK","mcore-create-issue",null,"Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fmcore-create-issue\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mcore-create-issue\ndescription: Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.\nlicense: Apache-2.0\nwhen_to_use: User shares a GitHub Actions URL and wants to file a bug report; 'create an issue for this failure', 'file a bug for this CI run', 'triage this GitHub Actions failure'.\nuser_invocable: true\nargument: \"GitHub Actions run or job URL\"\nmetadata:\n  author: Philip Petrakian \u003Cppetrakian@nvidia.com>\n---\n\n# Triage CI Failure into a GitHub Issue\n\nInvestigate a failing GitHub Actions job, extract the root cause, and file a\nwell-structured bug issue against `NVIDIA\u002FMegatron-LM`.\n\n## Workflow\n\n### 1. Parse the URL\n\nThe argument is a GitHub Actions URL. It will be one of:\n\n- **Job URL**: `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fruns\u002F\u003Crun_id>\u002Fjob\u002F\u003Cjob_id>`\n- **Run URL**: `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fruns\u002F\u003Crun_id>`\n\nExtract `run_id` and, if present, `job_id`.\n\n### 2. Identify failed jobs\n\n- If a `job_id` was provided, use that job directly.\n- If only a `run_id` was provided, list all failed jobs in the run:\n\n  ```bash\n  gh run view \u003Crun_id> --repo NVIDIA\u002FMegatron-LM --json jobs \\\n    --jq '[.jobs[] | select(.conclusion == \"failure\") | {id: .databaseId, name: .name, url: .url}]'\n  ```\n\n  If multiple jobs failed, ask the user which one to triage, or triage all of them if they say so.\n\n### 3. Fetch the failure logs\n\nFor each failed job, retrieve the logs and narrow them down to the failure:\n\n```bash\n# Pull the raw log and keep only error-bearing lines\ngh api repos\u002FNVIDIA\u002FMegatron-LM\u002Factions\u002Fjobs\u002F\u003Cjob_id>\u002Flogs 2>&1 \\\n  | grep -E \"(FAILED|ERROR|\\bError\\b|assert|Traceback|Exception|##\\[error\\])\" \\\n  | head -200\n```\n\nAlso capture the full job name:\n\n```bash\ngh run view --job \u003Cjob_id> --repo NVIDIA\u002FMegatron-LM --json name --jq .name\n```\n\nIf the grep output is sparse, download the full logs and look for the pytest\n`FAILURES` section or the last non-zero exit signal.\n\n### 4. Resolve the triggering PR and test author\n\n**Triggering PR**: the run's head branch follows the pattern `pull-request\u002F\u003Cnumber>`.\nExtract it and resolve the PR:\n\n```bash\ngh run view \u003Crun_id> --repo NVIDIA\u002FMegatron-LM --json headBranch --jq .headBranch\n# → e.g. \"pull-request\u002F4332\"\n# Extract PR number and fetch metadata:\ngh pr view \u003Cpr_number> --repo NVIDIA\u002FMegatron-LM --json number,title,url \\\n  --jq '{number: .number, title: .title, url: .url}'\n```\n\n**Test file author**: find the GitHub login of whoever last touched the failing\ntest file. The file may not exist on `main` — first determine the PR's base\nbranch, then search from there:\n\n```bash\n# 1. Get the PR's base branch (e.g. \"main\", \"dev\", \"release\u002FX.Y\")\ngh pr view \u003Cpr_number> --repo NVIDIA\u002FMegatron-LM --json baseRefName --jq .baseRefName\n\n# 2. Search commits on that base branch\ngh api \"repos\u002FNVIDIA\u002FMegatron-LM\u002Fcommits?path=\u003Ctest-file-path>&sha=\u003Cbase-branch>&per_page=1\" \\\n  --jq '.[0] | {login: .author.login, name: .commit.author.name, sha: .sha}'\n```\n\nIf the result is empty (file was introduced by the PR itself), query the PR's\ncommits instead:\n\n```bash\ngh api \"repos\u002FNVIDIA\u002FMegatron-LM\u002Fpulls\u002F\u003Cpr_number>\u002Fcommits\" \\\n  --jq '[.[] | select(.files? \u002F\u002F [] | any(.filename == \"\u003Ctest-file-path>\"))] | .[0].author.login'\n```\n\nAs a last resort, list the PR commits and pick the author of the commit whose\nmessage most closely relates to the failing test file.\n\n### 5. Extract the root cause\n\nFrom the logs, identify:\n\n- **Failed test(s)**: lines matching `FAILED tests\u002F...::...` give the exact pytest node IDs.\n- **Error message**: the assertion failure, exception type, or first meaningful\n  traceback frame — keep it under ~30 lines.\n- **Job name**: the GitHub Actions job name (e.g. `tests\u002Funit_tests\u002Ftransformer\u002Fmoe\u002F**\u002F*.py - latest`).\n- **Run \u002F job URLs** and **PR URL**: for linking in the issue.\n\n### 6. Check for duplicate issues\n\nSearch for open issues that already cover the same test:\n\n```bash\ngh issue list --repo NVIDIA\u002FMegatron-LM \\\n  --state open \\\n  --search \"\u003Cfailed-test-filename>\" \\\n  --json number,title,url \\\n  --limit 10\n```\n\n- If a matching open issue exists, **do not create a new one**. Report the\n  existing issue to the user and stop.\n- If no match is found, proceed to file a new issue.\n\n### 7. Create the issue\n\nPass `--assignee \u003Ctest-author-login>` to assign the issue to the test file's\nauthor. Include the triggering PR URL in the issue body.\n\n```bash\ngh issue create \\\n  --repo NVIDIA\u002FMegatron-LM \\\n  --title \"🐛 CI failure: \u003Cfailed-test-node-id>\" \\\n  --label \"bug\" \\\n  --assignee \"\u003Ctest-author-login>\" \\\n  --body \"...\"\n```\n\nUse the bug-report template body structure:\n\n```markdown\n**Describe the bug**\n\nCI test `\u003Cfailed-test-node-id>` failed in job [`\u003Cjob-name>`](\u003Cjob-url>).\nTag @NVIDIA\u002Fmcore-oncall to get oncall's attention to this issue.\n\n**Failing run**\n\n| Field | Value |\n|-------|-------|\n| PR    | [#\u003Cpr_number>: \u003Cpr_title>](\u003Cpr_url>) |\n| Run   | [\u003Crun_id>](\u003Crun_url>) |\n| Job   | [\u003Cjob_name>](\u003Cjob_url>) |\n\n**Error**\n\n```\n\u003Ccore error message \u002F traceback — 30 lines max>\n```\n\n**Steps\u002FCode to reproduce bug**\n\nRe-run the failing CI job linked above, or locally inside the dev container:\n\n```bash\npytest \u003Cfailed-test-node-id>\n```\n\n**Additional context**\n\nTriaged automatically via `\u002Ftriage-issue`.\n```\n\nIf multiple tests failed in the same job, list each one as a separate bullet\nunder \"Describe the bug\" and include the combined error snippets. Assign the\nissue to the author of whichever test file appears first in the failure list.\n\n### 8. Report back to the user\n\nPrint the URL of the newly created issue (or the duplicate, if found) so the\nuser can review or share it.\n\n## Important guidelines\n\n- Never create an issue if a duplicate already exists — link the existing one instead.\n- Always include the triggering PR link in the issue body.\n- Always assign the issue to the test file's most recent author. If the author\n  lookup fails (e.g. the commit was made by a bot or the login is unavailable),\n  skip `--assignee` and note it in the \"Additional context\" section.\n- Keep the error snippet concise (≤30 lines). Truncate long tracebacks and note that the full log is available via the job URL.\n- Do not guess the root cause — quote the actual log output verbatim.\n- If the job is still in progress or the logs are unavailable, say so and ask the user to retry once the run completes.\n","# Triage CI Failure into a GitHub Issue\n\nInvestigate a failing GitHub Actions job, extract the root cause, and file a\nwell-structured bug issue against `NVIDIA\u002FMegatron-LM`.\n\n## Workflow\n\n### 1. Parse the URL\n\nThe argument is a GitHub Actions URL. It will be one of:\n\n- **Job URL**: `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fruns\u002F\u003Crun_id>\u002Fjob\u002F\u003Cjob_id>`\n- **Run URL**: `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fruns\u002F\u003Crun_id>`\n\nExtract `run_id` and, if present, `job_id`.\n\n### 2. Identify failed jobs\n\n- If a `job_id` was provided, use that job directly.\n- If only a `run_id` was provided, list all failed jobs in the run:\n\n  ```bash\n  gh run view \u003Crun_id> --repo NVIDIA\u002FMegatron-LM --json jobs \\\n    --jq '[.jobs[] | select(.conclusion == \"failure\") | {id: .databaseId, name: .name, url: .url}]'\n  ```\n\n  If multiple jobs failed, ask the user which one to triage, or triage all of them if they say so.\n\n### 3. Fetch the failure logs\n\nFor each failed job, retrieve the logs and narrow them down to the failure:\n\n```bash\n# Pull the raw log and keep only error-bearing lines\ngh api repos\u002FNVIDIA\u002FMegatron-LM\u002Factions\u002Fjobs\u002F\u003Cjob_id>\u002Flogs 2>&1 \\\n  | grep -E \"(FAILED|ERROR|\\bError\\b|assert|Traceback|Exception|##\\[error\\])\" \\\n  | head -200\n```\n\nAlso capture the full job name:\n\n```bash\ngh run view --job \u003Cjob_id> --repo NVIDIA\u002FMegatron-LM --json name --jq .name\n```\n\nIf the grep output is sparse, download the full logs and look for the pytest\n`FAILURES` section or the last non-zero exit signal.\n\n### 4. Resolve the triggering PR and test author\n\n**Triggering PR**: the run's head branch follows the pattern `pull-request\u002F\u003Cnumber>`.\nExtract it and resolve the PR:\n\n```bash\ngh run view \u003Crun_id> --repo NVIDIA\u002FMegatron-LM --json headBranch --jq .headBranch\n# → e.g. \"pull-request\u002F4332\"\n# Extract PR number and fetch metadata:\ngh pr view \u003Cpr_number> --repo NVIDIA\u002FMegatron-LM --json number,title,url \\\n  --jq '{number: .number, title: .title, url: .url}'\n```\n\n**Test file author**: find the GitHub login of whoever last touched the failing\ntest file. The file may not exist on `main` — first determine the PR's base\nbranch, then search from there:\n\n```bash\n# 1. Get the PR's base branch (e.g. \"main\", \"dev\", \"release\u002FX.Y\")\ngh pr view \u003Cpr_number> --repo NVIDIA\u002FMegatron-LM --json baseRefName --jq .baseRefName\n\n# 2. Search commits on that base branch\ngh api \"repos\u002FNVIDIA\u002FMegatron-LM\u002Fcommits?path=\u003Ctest-file-path>&sha=\u003Cbase-branch>&per_page=1\" \\\n  --jq '.[0] | {login: .author.login, name: .commit.author.name, sha: .sha}'\n```\n\nIf the result is empty (file was introduced by the PR itself), query the PR's\ncommits instead:\n\n```bash\ngh api \"repos\u002FNVIDIA\u002FMegatron-LM\u002Fpulls\u002F\u003Cpr_number>\u002Fcommits\" \\\n  --jq '[.[] | select(.files? \u002F\u002F [] | any(.filename == \"\u003Ctest-file-path>\"))] | .[0].author.login'\n```\n\nAs a last resort, list the PR commits and pick the author of the commit whose\nmessage most closely relates to the failing test file.\n\n### 5. Extract the root cause\n\nFrom the logs, identify:\n\n- **Failed test(s)**: lines matching `FAILED tests\u002F...::...` give the exact pytest node IDs.\n- **Error message**: the assertion failure, exception type, or first meaningful\n  traceback frame — keep it under ~30 lines.\n- **Job name**: the GitHub Actions job name (e.g. `tests\u002Funit_tests\u002Ftransformer\u002Fmoe\u002F**\u002F*.py - latest`).\n- **Run \u002F job URLs** and **PR URL**: for linking in the issue.\n\n### 6. Check for duplicate issues\n\nSearch for open issues that already cover the same test:\n\n```bash\ngh issue list --repo NVIDIA\u002FMegatron-LM \\\n  --state open \\\n  --search \"\u003Cfailed-test-filename>\" \\\n  --json number,title,url \\\n  --limit 10\n```\n\n- If a matching open issue exists, **do not create a new one**. Report the\n  existing issue to the user and stop.\n- If no match is found, proceed to file a new issue.\n\n### 7. Create the issue\n\nPass `--assignee \u003Ctest-author-login>` to assign the issue to the test file's\nauthor. Include the triggering PR URL in the issue body.\n\n```bash\ngh issue create \\\n  --repo NVIDIA\u002FMegatron-LM \\\n  --title \"🐛 CI failure: \u003Cfailed-test-node-id>\" \\\n  --label \"bug\" \\\n  --assignee \"\u003Ctest-author-login>\" \\\n  --body \"...\"\n```\n\nUse the bug-report template body structure:\n\n```markdown\n**Describe the bug**\n\nCI test `\u003Cfailed-test-node-id>` failed in job [`\u003Cjob-name>`](\u003Cjob-url>).\nTag @NVIDIA\u002Fmcore-oncall to get oncall's attention to this issue.\n\n**Failing run**\n\n| Field | Value |\n|-------|-------|\n| PR    | [#\u003Cpr_number>: \u003Cpr_title>](\u003Cpr_url>) |\n| Run   | [\u003Crun_id>](\u003Crun_url>) |\n| Job   | [\u003Cjob_name>](\u003Cjob_url>) |\n\n**Error**\n\n```\n\u003Ccore error message \u002F traceback — 30 lines max>\n```\n\n**Steps\u002FCode to reproduce bug**\n\nRe-run the failing CI job linked above, or locally inside the dev container:\n\n```bash\npytest \u003Cfailed-test-node-id>\n```\n\n**Additional context**\n\nTriaged automatically via `\u002Ftriage-issue`.\n```\n\nIf multiple tests failed in the same job, list each one as a separate bullet\nunder \"Describe the bug\" and include the combined error snippets. Assign the\nissue to the author of whichever test file appears first in the failure list.\n\n### 8. Report back to the user\n\nPrint the URL of the newly created issue (or the duplicate, if found) so the\nuser can review or share it.\n\n## Important guidelines\n\n- Never create an issue if a duplicate already exists — link the existing one instead.\n- Always include the triggering PR link in the issue body.\n- Always assign the issue to the test file's most recent author. If the author\n  lookup fails (e.g. the commit was made by a bot or the login is unavailable),\n  skip `--assignee` and note it in the \"Additional context\" section.\n- Keep the error snippet concise (≤30 lines). Truncate long tracebacks and note that the full log is available via the job URL.\n- Do not guess the root cause — quote the actual log output verbatim.\n- If the job is still in progress or the logs are unavailable, say so and ask the user to retry once the run completes.\n",{"name":5,"license":15,"argument":24,"metadata":25,"description":7,"when_to_use":27,"user_invocable":28},"GitHub Actions run or job URL",{"author":26},"Philip Petrakian \u003Cppetrakian@nvidia.com>","User shares a GitHub Actions URL and wants to file a bug report; 'create an issue for this failure', 'file a bug for this CI run', 'triage this GitHub Actions failure'.",true,"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fnvidia-skills\u002Fmcore-create-issue",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":28},[39,42,45],{"tool":40,"command":41},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill mcore-create-issue",{"tool":43,"command":44},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill mcore-create-issue",{"tool":46,"command":47},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill mcore-create-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fmcore-create-issue\u002FSkill.md",[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"metadata.json","REFERENCE","参考文档",422,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fmcore-create-issue\u002Fmetadata.json",[57,65,70,77,82,89],{"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":61,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":66,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]