[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DSSCZEXK2DKA0CTZ892SK3":3,"skill-same:01M6DSSCZEXK2DKA0CTZ892SK3":61},{"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":22,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6DSSCZEXK2DKA0CTZ892SK3","coding",null,"Production code author — write, edit, debug, and scaffold real code projects. Gives the entity the ability to create working software saved as actual code files.","voardwalker-code\u002FNekoCore-OS","voardwalker-code","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253527670?v=4","01M6DSRW3VB3V3JY99ABQZM55S","01M6DSRW8P3M7580SFQX01R3M9",8,"MIT","https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS\u002Fblob\u002Fmain\u002Fproject\u002FMA\u002FMA-skills\u002Fcoding\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,23,24,25,26,27,28,29,30,31,32,33],"scaffold","debug","create","code","Production","projects","write","edit","files","as","software","2026-11-10 10:12:30",false,"---\nname: coding\ndescription: Production code author — write, edit, debug, and scaffold real code projects. Gives the entity the ability to create working software saved as actual code files.\n---\n\n# Coding Skill\n\nYou can write real code and save it as actual files. Not snippets in chat — real `.js`, `.py`, `.html`, `.css`, `.json`, `.ts`, `.sh`, `.sql`, or any other code file.\n\n## What You Can Do\n\n1. **Write new code files** — create complete, runnable source files\n2. **Edit existing code** — read a file, modify it, write it back\n3. **Scaffold projects** — create folder structures with multiple files\n4. **Debug code** — read code, find bugs, write the fix\n5. **Refactor code** — restructure files while preserving behavior\n\n## Your Tools\n\n```\n[TOOL:ws_list path=\".\"]                          — see files and folders\n[TOOL:ws_read path=\"src\u002Fapp.js\"]                 — read a file's contents\n[TOOL:ws_write path=\"src\u002Fapp.js\" content=\"...\"]  — create or overwrite a file\n[TOOL:ws_append path=\"src\u002Fapp.js\" content=\"...\"] — add to end of a file\n[TOOL:ws_delete path=\"old-file.js\"]              — remove a file\n[TOOL:ws_move src=\"old.js\" dst=\"new.js\"]         — rename or move a file\n[TOOL:ws_mkdir path=\"src\u002Futils\"]                 — create a folder\n[TOOL:cmd_run cmd=\"node src\u002Findex.js\"]           — run a command (see allowed list)\n[TOOL:cmd_run cmd=\"npm test\"]                    — run tests\n```\n\n## CRITICAL RULES — Read These First\n\n### Rule 1: Always write COMPLETE files\nNever write partial code with comments like `\u002F\u002F ...rest of code here...` or `\u002F\u002F existing code unchanged`. Write the ENTIRE file content every time you use `ws_write`. The tool overwrites the whole file.\n\n### Rule 2: Always READ before you EDIT\nBefore changing any existing file, ALWAYS read it first:\n```\n[TOOL:ws_read path=\"src\u002Fapp.js\"]\n```\nThen write the complete modified version back. Never guess what is in a file.\n\n### Rule 3: Always LIST before you READ\nCheck what exists before diving in:\n```\n[TOOL:ws_list path=\".\"]\n[TOOL:ws_list path=\"src\"]\n```\n\n### Rule 4: One tool call, one complete action\nEach `ws_write` call writes one complete file. To create a project with 3 files, you need 3 separate `ws_write` calls.\n\n### Rule 5: Escape quotes in content\nWhen your code contains double quotes, escape them with backslash:\n```\n[TOOL:ws_write path=\"config.json\" content=\"{\\n  \\\"name\\\": \\\"my-app\\\",\\n  \\\"version\\\": \\\"1.0.0\\\"\\n}\"]\n```\n\n## How to Write Code — Step by Step\n\n### Creating a new file\n1. Decide the file path (e.g., `src\u002Futils\u002Fhelpers.js`)\n2. Write the COMPLETE file in one `ws_write` call\n3. Confirm the write succeeded\n\n### Editing an existing file\n1. `[TOOL:ws_read path=\"src\u002Fapp.js\"]` — read current contents\n2. Understand what needs to change\n3. `[TOOL:ws_write path=\"src\u002Fapp.js\" content=\"...FULL modified file...\"]` — write the entire file back with your changes\n\n### Building a multi-file project\n1. Plan the file structure first (list all files you need)\n2. Start with the entry point \u002F main file\n3. Write shared utilities and helpers next\n4. Write secondary files that depend on the shared code\n5. Write configuration files last (package.json, etc.)\n\nExample order for a Node.js project:\n```\nStep 1: ws_mkdir path=\"my-project\u002Fsrc\"\nStep 2: ws_write path=\"my-project\u002Fpackage.json\" content=\"...\"\nStep 3: ws_write path=\"my-project\u002Fsrc\u002Findex.js\" content=\"...\"\nStep 4: ws_write path=\"my-project\u002Fsrc\u002Futils.js\" content=\"...\"\n```\n\n## Language Patterns\n\n### JavaScript \u002F Node.js\n```javascript\n\u002F\u002F Dependencies at top\nconst fs = require('fs');\nconst path = require('path');\n\n\u002F\u002F Constants\nconst DEFAULT_PORT = 3000;\n\n\u002F\u002F Functions\nfunction startServer(port) {\n  if (!port) port = DEFAULT_PORT;\n  \u002F\u002F implementation\n}\n\n\u002F\u002F Exports at bottom\nmodule.exports = { startServer };\n```\n\n### Python\n```python\n\"\"\"Module description.\"\"\"\n\nimport os\nimport sys\n\n# Constants\nDEFAULT_TIMEOUT = 30\n\ndef main():\n    \"\"\"Entry point.\"\"\"\n    # implementation\n    pass\n\nif __name__ == '__main__':\n    main()\n```\n\n### HTML\n```html\n\u003C!DOCTYPE html>\n\u003Chtml lang=\"en\">\n\u003Chead>\n  \u003Cmeta charset=\"UTF-8\">\n  \u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n  \u003Ctitle>Page Title\u003C\u002Ftitle>\n  \u003Clink rel=\"stylesheet\" href=\"styles.css\">\n\u003C\u002Fhead>\n\u003Cbody>\n  \u003Cmain id=\"app\">\u003C\u002Fmain>\n  \u003Cscript src=\"app.js\">\u003C\u002Fscript>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### CSS\n```css\n\u002F* Reset *\u002F\n*, *::before, *::after { box-sizing: border-box; }\n\n\u002F* Variables *\u002F\n:root {\n  --color-primary: #2563eb;\n  --font-main: system-ui, sans-serif;\n}\n\n\u002F* Layout *\u002F\nbody {\n  font-family: var(--font-main);\n  margin: 0;\n  padding: 0;\n}\n```\n\n## Code Quality Checklist\n\nBefore writing any file, verify:\n\n- [ ] **Inputs validated** — functions check that required parameters exist\n- [ ] **No hardcoded secrets** — API keys, passwords, tokens go in config, never in code\n- [ ] **Error messages are specific** — say WHAT failed and WHERE, not just \"Error\"\n- [ ] **No dead code** — no commented-out blocks, no unused imports\n- [ ] **Consistent style** — match the existing project's naming, indentation, quotes\n- [ ] **File is complete** — no placeholder comments, no `TODO` stubs, no `...` gaps\n\n## Debugging Workflow\n\nWhen the user reports a bug:\n\n1. **Read the buggy file:**\n   ```\n   [TOOL:ws_read path=\"src\u002Fbroken.js\"]\n   ```\n\n2. **Understand the expected vs actual behavior** — ask the user if unclear\n\n3. **Trace the problem:**\n   - Where does the data come from? (input)\n   - Where does it go wrong? (transform)\n   - What is the wrong output? (result)\n\n4. **Fix with minimum change** — change only what is broken, do not refactor surrounding code\n\n5. **Write the fixed file:**\n   ```\n   [TOOL:ws_write path=\"src\u002Fbroken.js\" content=\"...complete fixed file...\"]\n   ```\n\n6. **Explain the fix** — tell the user what was wrong and why your change fixes it\n\n## Project Scaffolding Patterns\n\n### Minimal Node.js project\n```\nmy-project\u002F\n  package.json\n  src\u002F\n    index.js\n```\n\n### Node.js with tests\n```\nmy-project\u002F\n  package.json\n  src\u002F\n    index.js\n    utils.js\n  tests\u002F\n    index.test.js\n```\n\n### Static website\n```\nmy-site\u002F\n  index.html\n  css\u002F\n    styles.css\n  js\u002F\n    app.js\n  assets\u002F\n```\n\n### Python project\n```\nmy-project\u002F\n  requirements.txt\n  main.py\n  src\u002F\n    __init__.py\n    core.py\n    utils.py\n```\n\n## What NOT to Do\n\n- **Do NOT write code in chat and ask the user to copy it.** Use `ws_write` to save it directly.\n- **Do NOT write partial files.** Always write the complete file.\n- **Do NOT guess file contents.** Always `ws_read` first before editing.\n- **Do NOT add features the user did not ask for.** Write exactly what was requested.\n- **Do NOT add extensive comments to simple code.** The code should be self-documenting.\n- **Do NOT create test files unless the user asks for tests.**\n- **Do NOT install packages or run shell commands unless you have the cmd_run tool.** If cmd_run is available, use it. Otherwise, you write files — the user runs them.\n\n## Session Notes\n\nAfter completing a coding task, save a brief note:\n```\n[TOOL:ws_append path=\"session.md\" content=\"\\n- Created src\u002Findex.js — Express server with \u002Fapi\u002Fusers endpoint\"]\n```\n\nThis helps you remember what was done if the conversation continues.\n","# Coding Skill\n\nYou can write real code and save it as actual files. Not snippets in chat — real `.js`, `.py`, `.html`, `.css`, `.json`, `.ts`, `.sh`, `.sql`, or any other code file.\n\n## What You Can Do\n\n1. **Write new code files** — create complete, runnable source files\n2. **Edit existing code** — read a file, modify it, write it back\n3. **Scaffold projects** — create folder structures with multiple files\n4. **Debug code** — read code, find bugs, write the fix\n5. **Refactor code** — restructure files while preserving behavior\n\n## Your Tools\n\n```\n[TOOL:ws_list path=\".\"]                          — see files and folders\n[TOOL:ws_read path=\"src\u002Fapp.js\"]                 — read a file's contents\n[TOOL:ws_write path=\"src\u002Fapp.js\" content=\"...\"]  — create or overwrite a file\n[TOOL:ws_append path=\"src\u002Fapp.js\" content=\"...\"] — add to end of a file\n[TOOL:ws_delete path=\"old-file.js\"]              — remove a file\n[TOOL:ws_move src=\"old.js\" dst=\"new.js\"]         — rename or move a file\n[TOOL:ws_mkdir path=\"src\u002Futils\"]                 — create a folder\n[TOOL:cmd_run cmd=\"node src\u002Findex.js\"]           — run a command (see allowed list)\n[TOOL:cmd_run cmd=\"npm test\"]                    — run tests\n```\n\n## CRITICAL RULES — Read These First\n\n### Rule 1: Always write COMPLETE files\nNever write partial code with comments like `\u002F\u002F ...rest of code here...` or `\u002F\u002F existing code unchanged`. Write the ENTIRE file content every time you use `ws_write`. The tool overwrites the whole file.\n\n### Rule 2: Always READ before you EDIT\nBefore changing any existing file, ALWAYS read it first:\n```\n[TOOL:ws_read path=\"src\u002Fapp.js\"]\n```\nThen write the complete modified version back. Never guess what is in a file.\n\n### Rule 3: Always LIST before you READ\nCheck what exists before diving in:\n```\n[TOOL:ws_list path=\".\"]\n[TOOL:ws_list path=\"src\"]\n```\n\n### Rule 4: One tool call, one complete action\nEach `ws_write` call writes one complete file. To create a project with 3 files, you need 3 separate `ws_write` calls.\n\n### Rule 5: Escape quotes in content\nWhen your code contains double quotes, escape them with backslash:\n```\n[TOOL:ws_write path=\"config.json\" content=\"{\\n  \\\"name\\\": \\\"my-app\\\",\\n  \\\"version\\\": \\\"1.0.0\\\"\\n}\"]\n```\n\n## How to Write Code — Step by Step\n\n### Creating a new file\n1. Decide the file path (e.g., `src\u002Futils\u002Fhelpers.js`)\n2. Write the COMPLETE file in one `ws_write` call\n3. Confirm the write succeeded\n\n### Editing an existing file\n1. `[TOOL:ws_read path=\"src\u002Fapp.js\"]` — read current contents\n2. Understand what needs to change\n3. `[TOOL:ws_write path=\"src\u002Fapp.js\" content=\"...FULL modified file...\"]` — write the entire file back with your changes\n\n### Building a multi-file project\n1. Plan the file structure first (list all files you need)\n2. Start with the entry point \u002F main file\n3. Write shared utilities and helpers next\n4. Write secondary files that depend on the shared code\n5. Write configuration files last (package.json, etc.)\n\nExample order for a Node.js project:\n```\nStep 1: ws_mkdir path=\"my-project\u002Fsrc\"\nStep 2: ws_write path=\"my-project\u002Fpackage.json\" content=\"...\"\nStep 3: ws_write path=\"my-project\u002Fsrc\u002Findex.js\" content=\"...\"\nStep 4: ws_write path=\"my-project\u002Fsrc\u002Futils.js\" content=\"...\"\n```\n\n## Language Patterns\n\n### JavaScript \u002F Node.js\n```javascript\n\u002F\u002F Dependencies at top\nconst fs = require('fs');\nconst path = require('path');\n\n\u002F\u002F Constants\nconst DEFAULT_PORT = 3000;\n\n\u002F\u002F Functions\nfunction startServer(port) {\n  if (!port) port = DEFAULT_PORT;\n  \u002F\u002F implementation\n}\n\n\u002F\u002F Exports at bottom\nmodule.exports = { startServer };\n```\n\n### Python\n```python\n\"\"\"Module description.\"\"\"\n\nimport os\nimport sys\n\n# Constants\nDEFAULT_TIMEOUT = 30\n\ndef main():\n    \"\"\"Entry point.\"\"\"\n    # implementation\n    pass\n\nif __name__ == '__main__':\n    main()\n```\n\n### HTML\n```html\n\u003C!DOCTYPE html>\n\u003Chtml lang=\"en\">\n\u003Chead>\n  \u003Cmeta charset=\"UTF-8\">\n  \u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n  \u003Ctitle>Page Title\u003C\u002Ftitle>\n  \u003Clink rel=\"stylesheet\" href=\"styles.css\">\n\u003C\u002Fhead>\n\u003Cbody>\n  \u003Cmain id=\"app\">\u003C\u002Fmain>\n  \u003Cscript src=\"app.js\">\u003C\u002Fscript>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### CSS\n```css\n\u002F* Reset *\u002F\n*, *::before, *::after { box-sizing: border-box; }\n\n\u002F* Variables *\u002F\n:root {\n  --color-primary: #2563eb;\n  --font-main: system-ui, sans-serif;\n}\n\n\u002F* Layout *\u002F\nbody {\n  font-family: var(--font-main);\n  margin: 0;\n  padding: 0;\n}\n```\n\n## Code Quality Checklist\n\nBefore writing any file, verify:\n\n- [ ] **Inputs validated** — functions check that required parameters exist\n- [ ] **No hardcoded secrets** — API keys, passwords, tokens go in config, never in code\n- [ ] **Error messages are specific** — say WHAT failed and WHERE, not just \"Error\"\n- [ ] **No dead code** — no commented-out blocks, no unused imports\n- [ ] **Consistent style** — match the existing project's naming, indentation, quotes\n- [ ] **File is complete** — no placeholder comments, no `TODO` stubs, no `...` gaps\n\n## Debugging Workflow\n\nWhen the user reports a bug:\n\n1. **Read the buggy file:**\n   ```\n   [TOOL:ws_read path=\"src\u002Fbroken.js\"]\n   ```\n\n2. **Understand the expected vs actual behavior** — ask the user if unclear\n\n3. **Trace the problem:**\n   - Where does the data come from? (input)\n   - Where does it go wrong? (transform)\n   - What is the wrong output? (result)\n\n4. **Fix with minimum change** — change only what is broken, do not refactor surrounding code\n\n5. **Write the fixed file:**\n   ```\n   [TOOL:ws_write path=\"src\u002Fbroken.js\" content=\"...complete fixed file...\"]\n   ```\n\n6. **Explain the fix** — tell the user what was wrong and why your change fixes it\n\n## Project Scaffolding Patterns\n\n### Minimal Node.js project\n```\nmy-project\u002F\n  package.json\n  src\u002F\n    index.js\n```\n\n### Node.js with tests\n```\nmy-project\u002F\n  package.json\n  src\u002F\n    index.js\n    utils.js\n  tests\u002F\n    index.test.js\n```\n\n### Static website\n```\nmy-site\u002F\n  index.html\n  css\u002F\n    styles.css\n  js\u002F\n    app.js\n  assets\u002F\n```\n\n### Python project\n```\nmy-project\u002F\n  requirements.txt\n  main.py\n  src\u002F\n    __init__.py\n    core.py\n    utils.py\n```\n\n## What NOT to Do\n\n- **Do NOT write code in chat and ask the user to copy it.** Use `ws_write` to save it directly.\n- **Do NOT write partial files.** Always write the complete file.\n- **Do NOT guess file contents.** Always `ws_read` first before editing.\n- **Do NOT add features the user did not ask for.** Write exactly what was requested.\n- **Do NOT add extensive comments to simple code.** The code should be self-documenting.\n- **Do NOT create test files unless the user asks for tests.**\n- **Do NOT install packages or run shell commands unless you have the cmd_run tool.** If cmd_run is available, use it. Otherwise, you write files — the user runs them.\n\n## Session Notes\n\nAfter completing a coding task, save a brief note:\n```\n[TOOL:ws_append path=\"session.md\" content=\"\\n- Created src\u002Findex.js — Express server with \u002Fapi\u002Fusers endpoint\"]\n```\n\nThis helps you remember what was done if the conversation continues.\n",{"name":5,"description":7},"main","437c11deeb521a7e0ae5845acda86fde6c0c1713","project\u002FMA\u002FMA-skills\u002Fcoding",1,"https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS","https:\u002F\u002Fneko-core.com","https:\u002F\u002Fgithub.com\u002Fvoardwalker-code","2026-03-31 19:44:56",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add voardwalker-code\u002FNekoCore-OS --skill coding",{"tool":53,"command":54},"bunx","bunx skills add voardwalker-code\u002FNekoCore-OS --skill coding",{"tool":56,"command":57},"pnpm","pnpm dlx skills add voardwalker-code\u002FNekoCore-OS --skill coding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS\u002Fblob\u002Fmain\u002Fproject\u002FMA\u002FMA-skills\u002Fcoding\u002FSKILL.md",true,[],[62,73,81,98,110,125],{"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":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":34},"01M6DSWEQ54Y3GAZAN7TMJW3D8","ws_move","Move or rename a file\u002Ffolder in the workspace","https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS\u002Fblob\u002Fmain\u002Fproject\u002Fskills\u002Fws_move\u002FSKILL.md",[],[69,70,71,72],"ws move","file","workspace","rename",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":34},"01M6DSWA5EX7QP108ZNS57EPM9","ws_mkdir","Create a new folder in the workspace","https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS\u002Fblob\u002Fmain\u002Fproject\u002Fskills\u002Fws_mkdir\u002FSKILL.md",[],[80,25,71],"ws mkdir",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":34},"01M6DSW6Y2YP8XTJ2HA3NHACJT","web-search","Browse the web, fetch pages, and extract content. Gives the entity the ability to search and read web content.","https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS\u002Fblob\u002Fmain\u002Fproject\u002Fskills\u002Fweb-search\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97],"web search","search","web","fetch","content","browse","read","extract","pages","read web",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":34},"01M6DSW3W69GV66HXSHGRW2RXK","vscode","Code collaborator — read, write, and plan changes to project files directly in a VS Code workspace. Gives the entity the ability to act as a programming partner.","https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS\u002Fblob\u002Fmain\u002Fproject\u002Fskills\u002Fvscode\u002FSKILL.md",[104],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[100,31,106,107,32,94,29,26,108,71,109],"project","act","plan","programming",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":34},"01M6DSVZS98WHW3ZVEBRTGDYJK","tutorial-notes","Take structured notes in workspace markdown files using deterministic tool calls.","https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS\u002Fblob\u002Fmain\u002Fproject\u002Fskills\u002Ftutorial-notes\u002FSKILL.md",[],[117,118,119,120,121,71,122,31,123,124],"tutorial notes","tutorial","notes","markdown","tool","take","deterministic","structured",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":34},"01M6DSVWEQC2SJCVAVN079NB6V","self-repair","System diagnostics and self-healing — run health scans, interpret results, trigger the fixer generator, guide users through disaster recovery, and rebuild broken files using the BIOS.","https:\u002F\u002Fgithub.com\u002Fvoardwalker-code\u002FNekoCore-OS\u002Fblob\u002Fmain\u002Fproject\u002Fskills\u002Fself-repair\u002FSKILL.md",[],[132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,31,147,148],"self repair","repair","self","broken","system","health","recovery","run","guide","self-healing","healing","disaster recovery","trigger","fixer","rebuild","results","diagnostics"]