[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CG11R2EF1EVSYN54S4QYFX":3,"skill-same:01M6CG11R2EF1EVSYN54S4QYFX":84},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6CG11R2EF1EVSYN54S4QYFX","vscode-extension-debugger",null,"This skill enables debugging VS Code extensions and their webviews through Chrome DevTools Protocol (CDP).\nIt should be used when:\n- Debugging VS Code extension webviews (custom editors, panels, sidebars)\n- Inspecting DOM structure of extension webviews\n- Taking screenshots of VS Code windows or webviews\n- Executing JavaScript in extension webviews\n- Monitoring console output from extensions\nTriggers on: \"debug extension\", \"inspect webview\", \"extension screenshot\", \"webview DOM\", \"VS Code debugging\"","OpenNekoPaw\u002Fneko-suite","OpenNekoPaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15809061?v=4","01M6CG05V2N1TRWA7J8N1SCXPB","NekoPaw","01M6CG05ZQR78WBSHEMA0Q0362",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002Fskills\u002Fvscode-extension-debugger\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"vscode extension debugger","vscode","vscode extension","debugger","console","cdp","chrome devtools","monitoring","devtools","screenshot","protocol","screenshots","code","debugging","debug","debug extension","windows","javascript","chrome","2026-11-10 10:12:30",false,"---\nname: vscode-extension-debugger\ndescription: |\n  This skill enables debugging VS Code extensions and their webviews through Chrome DevTools Protocol (CDP).\n  It should be used when:\n  - Debugging VS Code extension webviews (custom editors, panels, sidebars)\n  - Inspecting DOM structure of extension webviews\n  - Taking screenshots of VS Code windows or webviews\n  - Executing JavaScript in extension webviews\n  - Monitoring console output from extensions\n  Triggers on: \"debug extension\", \"inspect webview\", \"extension screenshot\", \"webview DOM\", \"VS Code debugging\"\n---\n\n# VS Code Extension Debugger\n\nThis skill provides tools to debug VS Code extensions and their webviews using Chrome DevTools Protocol (CDP).\n\n## Prerequisites\n\n1. VS Code must be running with remote debugging enabled on port 9222\n2. Launch VS Code with: `code --inspect=9222` or configure in launch.json\n3. Node.js must be available with the `ws` package installed globally or in the project\n\n## Core Tool\n\nThe CDP client script at `scripts\u002Fcdp-client.js` provides all debugging capabilities.\n\n### Available Commands\n\n| Command | Description | Usage |\n|---------|-------------|-------|\n| `list` | List all debug targets | `node cdp-client.js list` |\n| `snapshot` | Get DOM snapshot | `node cdp-client.js snapshot \u003CtargetId>` |\n| `screenshot` | Capture screenshot | `node cdp-client.js screenshot \u003CtargetId> [outputPath]` |\n| `eval` | Execute JavaScript | `node cdp-client.js eval \u003CtargetId> \u003Ccode>` |\n| `console` | Get console messages | `node cdp-client.js console \u003CtargetId>` |\n\n## Workflow\n\n### Step 1: List Available Targets\n\nTo find debug targets:\n\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js list\n```\n\nOutput shows all available targets:\n- `type: \"page\"` - VS Code windows (use for screenshots)\n- `type: \"iframe\"` - Extension webviews (use for DOM inspection)\n- `type: \"worker\"` - Background workers\n\n### Step 2: Identify Target\n\nFrom the list output, identify the relevant target:\n- For webview debugging: Find the iframe with `extensionId` matching your extension\n- For screenshots: Use the main page (type: \"page\") without parentId\n\n### Step 3: Inspect or Debug\n\n**Get DOM Snapshot:**\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js snapshot \u003CtargetId>\n```\n\nReturns:\n- `title` - Page\u002Fwebview title\n- `bodyText` - Text content (first 5000 chars)\n- `elements` - Interactive elements (buttons, inputs, etc.)\n\n**Take Screenshot:**\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js screenshot \u003CtargetId> \u002Ftmp\u002Fscreenshot.png\n```\n\nNote: Screenshots only work on top-level pages, not iframes. To capture webview content, screenshot the parent VS Code window.\n\n**Execute JavaScript:**\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js eval \u003CtargetId> \"document.title\"\n```\n\nFor webview iframe content:\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js eval \u003CparentPageId> \"document.getElementById('active-frame').contentDocument.body.innerText\"\n```\n\n**Monitor Console:**\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js console \u003CtargetId>\n```\n\n## Limitations\n\n1. **Screenshots**: Only work on top-level pages (type: \"page\"), not iframes\n2. **Cross-origin**: Some webview content may be cross-origin restricted\n3. **Port**: Default port is 9222, ensure VS Code is launched with this debug port\n\n## Troubleshooting\n\n### \"Connection refused\"\n- Ensure VS Code is running with `--inspect=9222`\n- Check if port 9222 is in use: `lsof -i :9222`\n\n### \"Target not found\"\n- Run `list` command to refresh available targets\n- Webview targets appear only when the webview is visible\n\n### \"Command can only be executed on top-level targets\"\n- This error occurs when trying to screenshot an iframe\n- Use the parent page ID instead for screenshots\n\n## Debug Session Control\n\nControl VS Code debug sessions using AppleScript keyboard shortcuts.\n\n### Available Commands\n\n| Action | Shortcut | AppleScript Command |\n|--------|----------|---------------------|\n| Start Debugging | F5 | `key code 96` |\n| Stop Debugging | Shift+F5 | `key code 96 using {shift down}` |\n| Restart Debugging | Cmd+Shift+F5 | `key code 96 using {command down, shift down}` |\n| Step Over | F10 | `key code 109` |\n| Step Into | F11 | `key code 103` |\n| Step Out | Shift+F11 | `key code 103 using {shift down}` |\n\n### Usage Examples\n\n**Start Debugging:**\n```bash\nosascript \u003C\u003CEOF\ntell application \"Visual Studio Code\" to activate\ndelay 0.3\ntell application \"System Events\"\n    tell process \"Code\"\n        key code 96\n    end tell\nend tell\nEOF\n```\n\n**Stop Debugging:**\n```bash\nosascript \u003C\u003CEOF\ntell application \"Visual Studio Code\" to activate\ndelay 0.3\ntell application \"System Events\"\n    tell process \"Code\"\n        key code 96 using {shift down}\n    end tell\nend tell\nEOF\n```\n\n**Restart Debugging:**\n```bash\nosascript \u003C\u003CEOF\ntell application \"Visual Studio Code\" to activate\ndelay 0.3\ntell application \"System Events\"\n    tell process \"Code\"\n        key code 96 using {command down, shift down}\n    end tell\nend tell\nEOF\n```\n\n### Prerequisites for AppleScript\n\nSystem Preferences > Security & Privacy > Privacy > Accessibility must include:\n- Terminal (or your terminal app)\n- osascript\n\n### VS Code Debug Commands Reference\n\nThese commands can be executed via `vscode.commands.executeCommand()` in extension code:\n\n| Command | Description |\n|---------|-------------|\n| `workbench.action.debug.start` | Start debugging (F5) |\n| `workbench.action.debug.stop` | Stop debugging (Shift+F5) |\n| `workbench.action.debug.restart` | Restart debugging (Cmd+Shift+F5) |\n| `workbench.action.debug.selectandstart` | Select and start debug config |\n| `workbench.action.debug.continue` | Continue execution |\n| `workbench.action.debug.stepOver` | Step over (F10) |\n| `workbench.action.debug.stepInto` | Step into (F11) |\n| `workbench.action.debug.stepOut` | Step out (Shift+F11) |\n\nNote: `vscode.debug.activeDebugSession` is an API property, not a command.\n\n## Example Session\n\n```bash\n# 1. List targets\nnode cdp-client.js list\n# Output: [{\"id\":\"ABC123\",\"type\":\"page\",\"title\":\"[Extension Host] ...\"},...]\n\n# 2. Get webview snapshot (find iframe with your extension)\nnode cdp-client.js snapshot DEF456\n\n# 3. Screenshot the main window\nnode cdp-client.js screenshot ABC123 \u002Ftmp\u002Fvscode.png\n\n# 4. Execute code in webview\nnode cdp-client.js eval DEF456 \"document.querySelectorAll('button').length\"\n\n# 5. Control debug session\nosascript -e 'tell application \"Visual Studio Code\" to activate' && \\\nosascript -e 'tell application \"System Events\" to tell process \"Code\" to key code 96'\n```\n","# VS Code Extension Debugger\n\nThis skill provides tools to debug VS Code extensions and their webviews using Chrome DevTools Protocol (CDP).\n\n## Prerequisites\n\n1. VS Code must be running with remote debugging enabled on port 9222\n2. Launch VS Code with: `code --inspect=9222` or configure in launch.json\n3. Node.js must be available with the `ws` package installed globally or in the project\n\n## Core Tool\n\nThe CDP client script at `scripts\u002Fcdp-client.js` provides all debugging capabilities.\n\n### Available Commands\n\n| Command | Description | Usage |\n|---------|-------------|-------|\n| `list` | List all debug targets | `node cdp-client.js list` |\n| `snapshot` | Get DOM snapshot | `node cdp-client.js snapshot \u003CtargetId>` |\n| `screenshot` | Capture screenshot | `node cdp-client.js screenshot \u003CtargetId> [outputPath]` |\n| `eval` | Execute JavaScript | `node cdp-client.js eval \u003CtargetId> \u003Ccode>` |\n| `console` | Get console messages | `node cdp-client.js console \u003CtargetId>` |\n\n## Workflow\n\n### Step 1: List Available Targets\n\nTo find debug targets:\n\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js list\n```\n\nOutput shows all available targets:\n- `type: \"page\"` - VS Code windows (use for screenshots)\n- `type: \"iframe\"` - Extension webviews (use for DOM inspection)\n- `type: \"worker\"` - Background workers\n\n### Step 2: Identify Target\n\nFrom the list output, identify the relevant target:\n- For webview debugging: Find the iframe with `extensionId` matching your extension\n- For screenshots: Use the main page (type: \"page\") without parentId\n\n### Step 3: Inspect or Debug\n\n**Get DOM Snapshot:**\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js snapshot \u003CtargetId>\n```\n\nReturns:\n- `title` - Page\u002Fwebview title\n- `bodyText` - Text content (first 5000 chars)\n- `elements` - Interactive elements (buttons, inputs, etc.)\n\n**Take Screenshot:**\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js screenshot \u003CtargetId> \u002Ftmp\u002Fscreenshot.png\n```\n\nNote: Screenshots only work on top-level pages, not iframes. To capture webview content, screenshot the parent VS Code window.\n\n**Execute JavaScript:**\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js eval \u003CtargetId> \"document.title\"\n```\n\nFor webview iframe content:\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js eval \u003CparentPageId> \"document.getElementById('active-frame').contentDocument.body.innerText\"\n```\n\n**Monitor Console:**\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js console \u003CtargetId>\n```\n\n## Limitations\n\n1. **Screenshots**: Only work on top-level pages (type: \"page\"), not iframes\n2. **Cross-origin**: Some webview content may be cross-origin restricted\n3. **Port**: Default port is 9222, ensure VS Code is launched with this debug port\n\n## Troubleshooting\n\n### \"Connection refused\"\n- Ensure VS Code is running with `--inspect=9222`\n- Check if port 9222 is in use: `lsof -i :9222`\n\n### \"Target not found\"\n- Run `list` command to refresh available targets\n- Webview targets appear only when the webview is visible\n\n### \"Command can only be executed on top-level targets\"\n- This error occurs when trying to screenshot an iframe\n- Use the parent page ID instead for screenshots\n\n## Debug Session Control\n\nControl VS Code debug sessions using AppleScript keyboard shortcuts.\n\n### Available Commands\n\n| Action | Shortcut | AppleScript Command |\n|--------|----------|---------------------|\n| Start Debugging | F5 | `key code 96` |\n| Stop Debugging | Shift+F5 | `key code 96 using {shift down}` |\n| Restart Debugging | Cmd+Shift+F5 | `key code 96 using {command down, shift down}` |\n| Step Over | F10 | `key code 109` |\n| Step Into | F11 | `key code 103` |\n| Step Out | Shift+F11 | `key code 103 using {shift down}` |\n\n### Usage Examples\n\n**Start Debugging:**\n```bash\nosascript \u003C\u003CEOF\ntell application \"Visual Studio Code\" to activate\ndelay 0.3\ntell application \"System Events\"\n    tell process \"Code\"\n        key code 96\n    end tell\nend tell\nEOF\n```\n\n**Stop Debugging:**\n```bash\nosascript \u003C\u003CEOF\ntell application \"Visual Studio Code\" to activate\ndelay 0.3\ntell application \"System Events\"\n    tell process \"Code\"\n        key code 96 using {shift down}\n    end tell\nend tell\nEOF\n```\n\n**Restart Debugging:**\n```bash\nosascript \u003C\u003CEOF\ntell application \"Visual Studio Code\" to activate\ndelay 0.3\ntell application \"System Events\"\n    tell process \"Code\"\n        key code 96 using {command down, shift down}\n    end tell\nend tell\nEOF\n```\n\n### Prerequisites for AppleScript\n\nSystem Preferences > Security & Privacy > Privacy > Accessibility must include:\n- Terminal (or your terminal app)\n- osascript\n\n### VS Code Debug Commands Reference\n\nThese commands can be executed via `vscode.commands.executeCommand()` in extension code:\n\n| Command | Description |\n|---------|-------------|\n| `workbench.action.debug.start` | Start debugging (F5) |\n| `workbench.action.debug.stop` | Stop debugging (Shift+F5) |\n| `workbench.action.debug.restart` | Restart debugging (Cmd+Shift+F5) |\n| `workbench.action.debug.selectandstart` | Select and start debug config |\n| `workbench.action.debug.continue` | Continue execution |\n| `workbench.action.debug.stepOver` | Step over (F10) |\n| `workbench.action.debug.stepInto` | Step into (F11) |\n| `workbench.action.debug.stepOut` | Step out (Shift+F11) |\n\nNote: `vscode.debug.activeDebugSession` is an API property, not a command.\n\n## Example Session\n\n```bash\n# 1. List targets\nnode cdp-client.js list\n# Output: [{\"id\":\"ABC123\",\"type\":\"page\",\"title\":\"[Extension Host] ...\"},...]\n\n# 2. Get webview snapshot (find iframe with your extension)\nnode cdp-client.js snapshot DEF456\n\n# 3. Screenshot the main window\nnode cdp-client.js screenshot ABC123 \u002Ftmp\u002Fvscode.png\n\n# 4. Execute code in webview\nnode cdp-client.js eval DEF456 \"document.querySelectorAll('button').length\"\n\n# 5. Control debug session\nosascript -e 'tell application \"Visual Studio Code\" to activate' && \\\nosascript -e 'tell application \"System Events\" to tell process \"Code\" to key code 96'\n```\n",{"name":5,"description":7},"main","9204f2e36f084a956241ea3f8e76080c07989947","skills\u002Fvscode-extension-debugger","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw","2026-07-16 01:36:41",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add OpenNekoPaw\u002Fneko-suite --skill vscode-extension-debugger",{"tool":60,"command":61},"bunx","bunx skills add OpenNekoPaw\u002Fneko-suite --skill vscode-extension-debugger",{"tool":63,"command":64},"pnpm","pnpm dlx skills add OpenNekoPaw\u002Fneko-suite --skill vscode-extension-debugger","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002Fskills\u002Fvscode-extension-debugger\u002FSKILL.md",true,[68,74,80],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fcdp-client.js","SCRIPT","脚本",7916,"https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002Fskills\u002Fvscode-extension-debugger\u002Fscripts\u002Fcdp-client.js",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"SOURCE.md","REFERENCE","参考文档",211,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Flit-identity-verify\u002FSOURCE.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Flit-identity-verify\u002FTRUST.auto.yaml",[85,93,101,113,132,143],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":43},"01M6CG10F0FAXC8QY4H4FTKGEE","review","Review functional Home artifacts.","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002Fscripts\u002Fwebview-functional\u002Ffixtures\u002Fhome\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[87,92],"artifacts",{"skillNo":94,"name":95,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":43},"01M6CG0YY2R6ZTQ20MBNMP2MM3","eval-existing-target-skill","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002Fscripts\u002Fagent-eval\u002Fshared-fixtures\u002Fskill-existing-target-workspace\u002F.agents\u002Fskills\u002Feval-existing-target-skill\u002FSKILL.md",[],[99,100],"eval existing target skill","eval",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":43},"01M6CG0XK0G6FC21JSG8DBN31B","evaluation-artifact-author","Author a deterministic portable Skill package when the user requests evaluation artifact evidence.","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002Fscripts\u002Fagent-eval\u002Fshared-fixtures\u002Fskill-artifact-workspace\u002F.agents\u002Fskills\u002Fevaluation-artifact-author\u002FSKILL.md",[],[108,109,110,111,112],"evaluation artifact author","Evaluation","package","user","evidence",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":43},"01M6CG0VBX3TK0J87H9DXX9758","openspec-propose","Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.","MIT","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",[],[121,122,123,124,125,126,127,128,111,92,129,130,131],"openspec propose","openspec","implementation","generated","ready","use","change","build","tasks","cli","design",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":43},"01M6CG0S1NP7PBG7SP5WH3WA22","openspec-explore","Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fopenspec-explore\u002FSKILL.md",[],[139,140,122,141,142,126,111,127,130],"openspec explore","explore","thinking partner","think",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":43},"01M6CG0PY7JM5A39ZR8JNNZEE6","openspec-archive-change","Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.","https:\u002F\u002Fgithub.com\u002FOpenNekoPaw\u002Fneko-suite\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fopenspec-archive-change\u002FSKILL.md",[],[127,150,151,122,130,123,126,111,152],"openspec archive change","archive","workflow"]