[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74EH3TPBFCCW8WDVBDASPJP":3,"skill-same:01M74EH3TPBFCCW8WDVBDASPJP":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74EH3TPBFCCW8WDVBDASPJP","nat-path-checks",null,"Use when fixing NeMo Agent Toolkit documentation path-check failures, especially failed `ci\u002Fscripts\u002Fpath_checks.py` output, slash-delimited text mistaken for paths, relative path references, Markdown code escaping, and path-check allowlist decisions.","lzy18001500226\u002FMoSim","lzy18001500226","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152623587?v=4","01M71ZMEX36NK05B642131DEEK","01M71ZMEXSMX72KPVNJ572G0CM",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FFrameworks\u002FNeMo-Agent-Toolkit-develop\u002Fskills\u002Fnat-path-checks\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: nat-path-checks\ndescription: Use when fixing NeMo Agent Toolkit documentation path-check failures, especially failed `ci\u002Fscripts\u002Fpath_checks.py` output, slash-delimited text mistaken for paths, relative path references, Markdown code escaping, and path-check allowlist decisions.\nauthor: NVIDIA Corporation and Affiliates\nlicense: Apache-2.0\n---\n\n# NeMo Agent Toolkit Path Checks\n\nUse this skill when CI reports failed path checks from `ci\u002Fscripts\u002Fpath_checks.py`, especially when copied CI output lists entries like:\n\n```text\nFailed path checks:\n- docs\u002Fexample.md:40:10 -> data\u002Ftest1\n```\n\n## Workflow\n\n1. Open each reported file at the exact line before editing.\n2. Classify the reported token by meaning, not just by shape.\n3. Apply the smallest fix that preserves meaning.\n4. Re-run path checks and Markdown link checks on the changed files.\n\n## Fix Decision Table\n\n| Reported token means | Preferred fix | Example |\n| --- | --- | --- |\n| Prose shorthand, not a path | Rewrite in words. Do not hide it in code just to silence CI. | `linux\u002Famd64` -> `linux or amd64`; `pass\u002Ffail` -> `pass or fail` |\n| Two field names or concepts | Name each item separately, usually as code spans if they are literal fields. | `question\u002Fanswer` -> `question` and `answer` |\n| Exact CLI, protocol, API, config, or method literal | Wrap the literal in inline code, or use a fenced code block for multi-line examples. | `tools\u002Flist` -> `tools\u002Flist` |\n| Placeholder path in prose | Wrap the placeholder in inline code. | `path\u002Fto\u002Fworkflow.yml` -> `path\u002Fto\u002Fworkflow.yml` |\n| Placeholder paths in a list or snippet | Use a fenced code block with an appropriate language or `text`. | Put `data\u002Ftest1` and `data\u002Ftest2` inside a fenced block. |\n| Real repo-relative path | Make the path correct relative to the current file, and link it when useful. | `[README](..\u002F..\u002FREADME.md)` |\n| Intended generated output path | Use inline code or a fenced block unless the file should already exist in the repo. | `.\u002Foutput\u002Fresults.json` |\n| Repeated false positive across many docs | Prefer a local wording or escaping fix. Add `ALLOWLISTED_WORDS`, `IGNORED_PATHS`, or `ALLOWLISTED_FILE_PATH_PAIRS` only for true checker limitations. | Add an allowlist only after confirming the token should pass everywhere. |\n\n## Important Distinctions\n\n- If a slash token is not meant to be copied exactly, rewrite it as prose.\n- If a slash token is meant to be copied exactly, put it in Markdown code.\n- If a slash token points to a real file in the repository, fix the target instead of escaping it.\n- If `data\u002Ftest1` is an example input path, use `data\u002Ftest1`. If it is a real checked-in path, link to the real file or correct the path.\n- Do not replace a meaningful relative path with different wording unless the path was never meant to be literal.\n\n## Validation\n\nRun these from the repository root after editing:\n\n```bash\nuv run ci\u002Fscripts\u002Fpath_checks.sh\nuv run pre-commit run markdown-link-check --files path\u002Fto\u002Fchanged.md\n```\n\nIf a copied CI log contains many failures, fix one file at a time and re-run path checks before applying the same pattern broadly.\n","# NeMo Agent Toolkit Path Checks\n\nUse this skill when CI reports failed path checks from `ci\u002Fscripts\u002Fpath_checks.py`, especially when copied CI output lists entries like:\n\n```text\nFailed path checks:\n- docs\u002Fexample.md:40:10 -> data\u002Ftest1\n```\n\n## Workflow\n\n1. Open each reported file at the exact line before editing.\n2. Classify the reported token by meaning, not just by shape.\n3. Apply the smallest fix that preserves meaning.\n4. Re-run path checks and Markdown link checks on the changed files.\n\n## Fix Decision Table\n\n| Reported token means | Preferred fix | Example |\n| --- | --- | --- |\n| Prose shorthand, not a path | Rewrite in words. Do not hide it in code just to silence CI. | `linux\u002Famd64` -> `linux or amd64`; `pass\u002Ffail` -> `pass or fail` |\n| Two field names or concepts | Name each item separately, usually as code spans if they are literal fields. | `question\u002Fanswer` -> `question` and `answer` |\n| Exact CLI, protocol, API, config, or method literal | Wrap the literal in inline code, or use a fenced code block for multi-line examples. | `tools\u002Flist` -> `tools\u002Flist` |\n| Placeholder path in prose | Wrap the placeholder in inline code. | `path\u002Fto\u002Fworkflow.yml` -> `path\u002Fto\u002Fworkflow.yml` |\n| Placeholder paths in a list or snippet | Use a fenced code block with an appropriate language or `text`. | Put `data\u002Ftest1` and `data\u002Ftest2` inside a fenced block. |\n| Real repo-relative path | Make the path correct relative to the current file, and link it when useful. | `[README](..\u002F..\u002FREADME.md)` |\n| Intended generated output path | Use inline code or a fenced block unless the file should already exist in the repo. | `.\u002Foutput\u002Fresults.json` |\n| Repeated false positive across many docs | Prefer a local wording or escaping fix. Add `ALLOWLISTED_WORDS`, `IGNORED_PATHS`, or `ALLOWLISTED_FILE_PATH_PAIRS` only for true checker limitations. | Add an allowlist only after confirming the token should pass everywhere. |\n\n## Important Distinctions\n\n- If a slash token is not meant to be copied exactly, rewrite it as prose.\n- If a slash token is meant to be copied exactly, put it in Markdown code.\n- If a slash token points to a real file in the repository, fix the target instead of escaping it.\n- If `data\u002Ftest1` is an example input path, use `data\u002Ftest1`. If it is a real checked-in path, link to the real file or correct the path.\n- Do not replace a meaningful relative path with different wording unless the path was never meant to be literal.\n\n## Validation\n\nRun these from the repository root after editing:\n\n```bash\nuv run ci\u002Fscripts\u002Fpath_checks.sh\nuv run pre-commit run markdown-link-check --files path\u002Fto\u002Fchanged.md\n```\n\nIf a copied CI log contains many failures, fix one file at a time and re-run path checks before applying the same pattern broadly.\n",{"name":5,"author":23,"license":14,"description":7},"NVIDIA Corporation and Affiliates","main","e0ec177d00f087cb04e90206b2f7d3aa2f5a1350","References\u002FAgent\u002FFrameworks\u002FNeMo-Agent-Toolkit-develop\u002Fskills\u002Fnat-path-checks","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add lzy18001500226\u002FMoSim --skill nat-path-checks",{"tool":36,"command":37},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill nat-path-checks",{"tool":39,"command":40},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill nat-path-checks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FFrameworks\u002FNeMo-Agent-Toolkit-develop\u002Fskills\u002Fnat-path-checks\u002FSKILL.md",true,[],[45,54,62,70,78,86],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":49,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":53},"01M78RK6JGRPTD3TDSMTQWDQ9P","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":53},"01M78RK29KVRDQXSMVZX1GQTJN","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":53},"01M78RJPF3210Y5DA9VJ6JMMG6","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":53},"01M78RJH7X67C5AY8ZVS7RQNWJ","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":53},"01M78RBBAYMJ6T3ZMAYHCFM6G7","skill-creator-cc","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update 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\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":95},"01M76VV9V2R9FZTVGMJZV7Y996","prd-writing-guide","Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.","MIT","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FSKILL.md",[],[],"2026-11-12 13:55:43"]