[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FZ1PPRS0V75Y8SPGTNK6MJ":3,"skill-same:01M6FZ1PPRS0V75Y8SPGTNK6MJ":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6FZ1PPRS0V75Y8SPGTNK6MJ","n8n-cli",null,"Use this skill when the user needs to manage n8n workflows — list, pull, push, test, verify, convert, or debug workflow executions via the n8nac CLI.","javimosch\u002Fsupercli","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M6D3F2EBNWNJ358Q90P5YQR1",57,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fn8n-cli\u002Fskills\u002Fquickstart\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"cli","n8n","n8n cli","workflow","test","workflows","debug","pull","push","verify","convert","list","user","use","manage","via","2026-11-10 10:12:30",false,"---\nname: n8n-cli\ndescription: Use this skill when the user needs to manage n8n workflows — list, pull, push, test, verify, convert, or debug workflow executions via the n8nac CLI.\n---\n\n# n8n CLI — n8n Workflow Management for AI Agents\n\nWrapper around [n8n-as-code](https:\u002F\u002Fgithub.com\u002FEtienneLescot\u002Fn8n-as-code) (n8nac CLI v2.2.1). Manage n8n workflows programmatically from the terminal.\n\n## Quick Start\n\n```bash\n# 1. Start n8n if not running:\ndocker run -d --name n8n --restart unless-stopped -p 5678:5678 \\\n  -e N8N_SECURE_COOKIE=false \\\n  -v ~\u002F.n8n:\u002Fhome\u002Fnode\u002F.n8n n8nio\u002Fn8n:latest\n\n# 2. Create owner account at http:\u002F\u002Flocalhost:5678\n#    Or via API:\ncurl -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Fowner\u002Fsetup \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\":\"admin@local.dev\",\"firstName\":\"Admin\",\"lastName\":\"User\",\"password\":\"Password123!\"}'\n\n# 3. Login to get session cookie:\ncurl -c \u002Ftmp\u002Fn8n-cookies.txt -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Flogin \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"emailOrLdapLoginId\":\"admin@local.dev\",\"password\":\"Password123!\"}'\n\n# 4. Create API key:\ncurl -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Fapi-keys \\\n  -H \"Content-Type: application\u002Fjson\" -b \u002Ftmp\u002Fn8n-cookies.txt \\\n  -d '{\"label\":\"n8n-cli\",\"scopes\":[\"workflow:list\",\"workflow:read\",\"workflow:create\",\"workflow:update\"],\"expiresAt\":null}'\n\n# 5. Configure n8nac workspace:\necho \"\u003CrawApiKey>\" | npx n8nac env add local \\\n  --base-url http:\u002F\u002Flocalhost:5678 \\\n  --sync-folder ~\u002Fn8n-workspace\u002Fworkflows --api-key-stdin\n\n# 6. Use the plugin:\nsc n8n-cli self version        # Verify version\nsc n8n-cli workflow list       # List all workflows\nsc n8n-cli workflow pull \u003Cid>  # Download workflow\n```\n\n## Commands\n\n### Instance & Config\n- `sc n8n-cli self version` — Print n8nac version\n- `sc n8n-cli self setup` — Configure n8n workspace (interactive — runs `n8nac setup`)\n- `sc n8n-cli self mcp` — Register MCP server in ~\u002F.supercli\u002Fmcp.json\n\n### Workflow Management\n- `sc n8n-cli workflow list` — List all workflows with status (tracked, remote-only, conflicts)\n- `sc n8n-cli workflow pull \u003Cid>` — Download workflow from n8n to local (uses bash wrapper to capture stderr)\n- `sc n8n-cli workflow push \u003Cpath>` — Upload local workflow to n8n\n\n### Passthrough (advanced, use raw n8nac flags)\n- `sc n8n-cli find \u003Cquery>` — Search workflows by name or ID\n- `sc n8n-cli test \u003Cid>` — Trigger workflow via webhook and report outcome\n- `sc n8n-cli verify \u003Cid>` — Validate workflow nodes against local schema\n- `sc n8n-cli convert \u003Cfile>` — Convert between JSON and TypeScript formats\n- `sc n8n-cli credentials` — Manage credential readiness inventory\n- `sc n8n-cli execution \u003Cid>` — Inspect workflow executions for debugging\n- `sc n8n-cli skills` — AI tools: search nodes, docs, validate workflows\n\n## Setting Up an n8n Instance\n\n### Docker (quickest)\n```bash\ndocker run -d --name n8n --restart unless-stopped -p 5678:5678 \\\n  -e N8N_SECURE_COOKIE=false \\\n  -v ~\u002F.n8n:\u002Fhome\u002Fnode\u002F.n8n n8nio\u002Fn8n:latest\n```\n\n### First-Time Setup\n1. Open http:\u002F\u002Flocalhost:5678\n2. Create owner account (email + password)\n3. Go to Settings → API Keys → Create API key with workflow scopes\n4. Or use the API (see Quick Start above)\n\n### Reset Owner (if needed)\n```bash\ndocker exec n8n n8n user-management:reset\ndocker restart n8n\n```\nThen recreate the owner account.\n\n## MCP Integration\n\nRegister the MCP server so agents can talk to n8n directly:\n```bash\nsc n8n-cli self mcp\n```\nThis adds a stdio MCP server to `~\u002F.supercli\u002Fmcp.json` running `npx n8nac mcp`.\nAgents get direct MCP tools for n8n operations without going through the CLI.\n\n## Working with Workflows\n\n### Creating a Workflow via API\n```bash\ncurl -s -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Fworkflows \\\n  -H \"Content-Type: application\u002Fjson\" -b \u002Ftmp\u002Fn8n-cookies.txt \\\n  -d '{\"name\":\"My Workflow\",\"nodes\":[{\"id\":\"1\",\"name\":\"Manual\",\"type\":\"n8n-nodes-base.manualTrigger\",\"typeVersion\":1,\"position\":[250,300]}],\"connections\":{},\"active\":false}'\n```\n\n### Pulling Workflows\n```bash\nsc n8n-cli workflow pull \u003Cworkflow-id>\n```\nAfter pulling, the workflow appears as TRACKED in `workflow list`. Files are saved to the sync folder.\n\n### Telegram Workflow Example\nCreate a workflow with Manual Trigger → Telegram node:\n```bash\ncurl -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Fworkflows \\\n  -H \"Content-Type: application\u002Fjson\" -b \u002Ftmp\u002Fn8n-cookies.txt \\\n  -d '{\"name\":\"Telegram Notif\",\"nodes\":[{\"id\":\"t1\",\"name\":\"Manual\",\"type\":\"n8n-nodes-base.manualTrigger\",\"typeVersion\":1,\"position\":[250,300]},{\"id\":\"t2\",\"name\":\"Send Telegram\",\"type\":\"n8n-nodes-base.telegram\",\"typeVersion\":1,\"position\":[550,300],\"parameters\":{\"resource\":\"message\",\"operation\":\"sendMessage\",\"chatId\":{\"value\":\"\"},\"text\":{\"value\":\"=Hello from n8n at {{ $now }}\"}},\"credentials\":{\"telegramApi\":{\"id\":null,\"name\":\"Telegram Bot\"}}}],\"connections\":{\"Manual\":{\"main\":[[{\"node\":\"Send Telegram\",\"type\":\"main\",\"index\":0}]]}},\"active\":false}'\n```\nThen configure the Telegram bot token in the n8n UI under Credentials.\n\n## Caveats & Pitfalls\n\n### 1. n8nac Output Goes to stderr\nAll n8nac commands (pull, push, list) output progress to **stderr**, not stdout. The plugin uses a bash wrapper with `2>&1` for pull\u002Fpush to capture it. Other commands may show empty `data.raw` if executed without the wrapper — use `workflow list` afterward to verify changes.\n\n### 2. n8nac Has No --json Flag\nn8nac does not support machine-readable output. All output is human-readable with ANSI escape codes. The `parseJson: false` adapter setting preserves raw text.\n\n### 3. Demo\u002FAI Agent Workflows May Fail to Pull\nSome pre-installed demo workflows (like \"My first AI Agent in n8n\") may return \"not found on remote\" when pulling. This is an upstream n8n-as-code issue with project-scoped workflows. Create your own workflows for reliable pull testing.\n\n### 4. Workspace Environment Required\nn8nac requires a configured workspace environment. Without it, commands fail with \"CLI not configured\". Use `n8nac env add` to set one up. The default env name is `local` — use `--env local` for commands that need it.\n\n### 5. API Key Creation Requires Specific Fields\nThe n8n API expects `label`, `scopes` (array), and `expiresAt` (null for no expiry) when creating API keys. Valid workflow scopes: `workflow:list`, `workflow:read`, `workflow:create`, `workflow:update`.\n\n### 6. n8n Owner Reset\nIf you forget the password or get locked out, use `docker exec n8n n8n user-management:reset && docker restart n8n` to reset the owner state.\n\n### 7. MCP Server Requires Running n8n\nThe n8n-as-code MCP server (`npx n8nac mcp`) requires the n8n instance to be reachable. It does not start n8n automatically — start n8n first with Docker.\n\n## Environment Detection\nThe n8nac config is stored globally (in `~\u002F.config\u002Fn8n-as-code\u002F`). The default environment is marked with `*` in `n8nac env list`. Commands that don't specify `--env` use the default.\n\n## Best Practices\n\n1. Use `workflow list` to discover workflow IDs before pulling\n2. Pull workflows before editing locally, push after changes\n3. Use `verify` to check node schemas before pushing to avoid runtime errors\n4. Combine with playwright-mcp for browser-based n8n testing\n5. Keep n8n and n8nac versions in sync — node schemas are built against the latest stable n8n release\n","# n8n CLI — n8n Workflow Management for AI Agents\n\nWrapper around [n8n-as-code](https:\u002F\u002Fgithub.com\u002FEtienneLescot\u002Fn8n-as-code) (n8nac CLI v2.2.1). Manage n8n workflows programmatically from the terminal.\n\n## Quick Start\n\n```bash\n# 1. Start n8n if not running:\ndocker run -d --name n8n --restart unless-stopped -p 5678:5678 \\\n  -e N8N_SECURE_COOKIE=false \\\n  -v ~\u002F.n8n:\u002Fhome\u002Fnode\u002F.n8n n8nio\u002Fn8n:latest\n\n# 2. Create owner account at http:\u002F\u002Flocalhost:5678\n#    Or via API:\ncurl -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Fowner\u002Fsetup \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\":\"admin@local.dev\",\"firstName\":\"Admin\",\"lastName\":\"User\",\"password\":\"Password123!\"}'\n\n# 3. Login to get session cookie:\ncurl -c \u002Ftmp\u002Fn8n-cookies.txt -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Flogin \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"emailOrLdapLoginId\":\"admin@local.dev\",\"password\":\"Password123!\"}'\n\n# 4. Create API key:\ncurl -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Fapi-keys \\\n  -H \"Content-Type: application\u002Fjson\" -b \u002Ftmp\u002Fn8n-cookies.txt \\\n  -d '{\"label\":\"n8n-cli\",\"scopes\":[\"workflow:list\",\"workflow:read\",\"workflow:create\",\"workflow:update\"],\"expiresAt\":null}'\n\n# 5. Configure n8nac workspace:\necho \"\u003CrawApiKey>\" | npx n8nac env add local \\\n  --base-url http:\u002F\u002Flocalhost:5678 \\\n  --sync-folder ~\u002Fn8n-workspace\u002Fworkflows --api-key-stdin\n\n# 6. Use the plugin:\nsc n8n-cli self version        # Verify version\nsc n8n-cli workflow list       # List all workflows\nsc n8n-cli workflow pull \u003Cid>  # Download workflow\n```\n\n## Commands\n\n### Instance & Config\n- `sc n8n-cli self version` — Print n8nac version\n- `sc n8n-cli self setup` — Configure n8n workspace (interactive — runs `n8nac setup`)\n- `sc n8n-cli self mcp` — Register MCP server in ~\u002F.supercli\u002Fmcp.json\n\n### Workflow Management\n- `sc n8n-cli workflow list` — List all workflows with status (tracked, remote-only, conflicts)\n- `sc n8n-cli workflow pull \u003Cid>` — Download workflow from n8n to local (uses bash wrapper to capture stderr)\n- `sc n8n-cli workflow push \u003Cpath>` — Upload local workflow to n8n\n\n### Passthrough (advanced, use raw n8nac flags)\n- `sc n8n-cli find \u003Cquery>` — Search workflows by name or ID\n- `sc n8n-cli test \u003Cid>` — Trigger workflow via webhook and report outcome\n- `sc n8n-cli verify \u003Cid>` — Validate workflow nodes against local schema\n- `sc n8n-cli convert \u003Cfile>` — Convert between JSON and TypeScript formats\n- `sc n8n-cli credentials` — Manage credential readiness inventory\n- `sc n8n-cli execution \u003Cid>` — Inspect workflow executions for debugging\n- `sc n8n-cli skills` — AI tools: search nodes, docs, validate workflows\n\n## Setting Up an n8n Instance\n\n### Docker (quickest)\n```bash\ndocker run -d --name n8n --restart unless-stopped -p 5678:5678 \\\n  -e N8N_SECURE_COOKIE=false \\\n  -v ~\u002F.n8n:\u002Fhome\u002Fnode\u002F.n8n n8nio\u002Fn8n:latest\n```\n\n### First-Time Setup\n1. Open http:\u002F\u002Flocalhost:5678\n2. Create owner account (email + password)\n3. Go to Settings → API Keys → Create API key with workflow scopes\n4. Or use the API (see Quick Start above)\n\n### Reset Owner (if needed)\n```bash\ndocker exec n8n n8n user-management:reset\ndocker restart n8n\n```\nThen recreate the owner account.\n\n## MCP Integration\n\nRegister the MCP server so agents can talk to n8n directly:\n```bash\nsc n8n-cli self mcp\n```\nThis adds a stdio MCP server to `~\u002F.supercli\u002Fmcp.json` running `npx n8nac mcp`.\nAgents get direct MCP tools for n8n operations without going through the CLI.\n\n## Working with Workflows\n\n### Creating a Workflow via API\n```bash\ncurl -s -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Fworkflows \\\n  -H \"Content-Type: application\u002Fjson\" -b \u002Ftmp\u002Fn8n-cookies.txt \\\n  -d '{\"name\":\"My Workflow\",\"nodes\":[{\"id\":\"1\",\"name\":\"Manual\",\"type\":\"n8n-nodes-base.manualTrigger\",\"typeVersion\":1,\"position\":[250,300]}],\"connections\":{},\"active\":false}'\n```\n\n### Pulling Workflows\n```bash\nsc n8n-cli workflow pull \u003Cworkflow-id>\n```\nAfter pulling, the workflow appears as TRACKED in `workflow list`. Files are saved to the sync folder.\n\n### Telegram Workflow Example\nCreate a workflow with Manual Trigger → Telegram node:\n```bash\ncurl -X POST http:\u002F\u002Flocalhost:5678\u002Frest\u002Fworkflows \\\n  -H \"Content-Type: application\u002Fjson\" -b \u002Ftmp\u002Fn8n-cookies.txt \\\n  -d '{\"name\":\"Telegram Notif\",\"nodes\":[{\"id\":\"t1\",\"name\":\"Manual\",\"type\":\"n8n-nodes-base.manualTrigger\",\"typeVersion\":1,\"position\":[250,300]},{\"id\":\"t2\",\"name\":\"Send Telegram\",\"type\":\"n8n-nodes-base.telegram\",\"typeVersion\":1,\"position\":[550,300],\"parameters\":{\"resource\":\"message\",\"operation\":\"sendMessage\",\"chatId\":{\"value\":\"\"},\"text\":{\"value\":\"=Hello from n8n at {{ $now }}\"}},\"credentials\":{\"telegramApi\":{\"id\":null,\"name\":\"Telegram Bot\"}}}],\"connections\":{\"Manual\":{\"main\":[[{\"node\":\"Send Telegram\",\"type\":\"main\",\"index\":0}]]}},\"active\":false}'\n```\nThen configure the Telegram bot token in the n8n UI under Credentials.\n\n## Caveats & Pitfalls\n\n### 1. n8nac Output Goes to stderr\nAll n8nac commands (pull, push, list) output progress to **stderr**, not stdout. The plugin uses a bash wrapper with `2>&1` for pull\u002Fpush to capture it. Other commands may show empty `data.raw` if executed without the wrapper — use `workflow list` afterward to verify changes.\n\n### 2. n8nac Has No --json Flag\nn8nac does not support machine-readable output. All output is human-readable with ANSI escape codes. The `parseJson: false` adapter setting preserves raw text.\n\n### 3. Demo\u002FAI Agent Workflows May Fail to Pull\nSome pre-installed demo workflows (like \"My first AI Agent in n8n\") may return \"not found on remote\" when pulling. This is an upstream n8n-as-code issue with project-scoped workflows. Create your own workflows for reliable pull testing.\n\n### 4. Workspace Environment Required\nn8nac requires a configured workspace environment. Without it, commands fail with \"CLI not configured\". Use `n8nac env add` to set one up. The default env name is `local` — use `--env local` for commands that need it.\n\n### 5. API Key Creation Requires Specific Fields\nThe n8n API expects `label`, `scopes` (array), and `expiresAt` (null for no expiry) when creating API keys. Valid workflow scopes: `workflow:list`, `workflow:read`, `workflow:create`, `workflow:update`.\n\n### 6. n8n Owner Reset\nIf you forget the password or get locked out, use `docker exec n8n n8n user-management:reset && docker restart n8n` to reset the owner state.\n\n### 7. MCP Server Requires Running n8n\nThe n8n-as-code MCP server (`npx n8nac mcp`) requires the n8n instance to be reachable. It does not start n8n automatically — start n8n first with Docker.\n\n## Environment Detection\nThe n8nac config is stored globally (in `~\u002F.config\u002Fn8n-as-code\u002F`). The default environment is marked with `*` in `n8nac env list`. Commands that don't specify `--env` use the default.\n\n## Best Practices\n\n1. Use `workflow list` to discover workflow IDs before pulling\n2. Pull workflows before editing locally, push after changes\n3. Use `verify` to check node schemas before pushing to avoid runtime errors\n4. Combine with playwright-mcp for browser-based n8n testing\n5. Keep n8n and n8nac versions in sync — node schemas are built against the latest stable n8n release\n",{"name":5,"description":7},"master","18c32f4b7197d246bdedcc9eca5d0403eaac0bc2","plugins\u002Fn8n-cli\u002Fskills\u002Fquickstart",5,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli","https:\u002F\u002Fjavimosch.github.io\u002Fsupercli\u002F","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-11-02 18:24:17",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add javimosch\u002Fsupercli --skill n8n-cli",{"tool":61,"command":62},"bunx","bunx skills add javimosch\u002Fsupercli --skill n8n-cli",{"tool":64,"command":65},"pnpm","pnpm dlx skills add javimosch\u002Fsupercli --skill n8n-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fn8n-cli\u002Fskills\u002Fquickstart\u002FSKILL.md",true,[],[70,79,98,110,122,129],{"skillNo":71,"name":72,"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":73,"categories":74,"keywords":76,"publishedAt":40},"01M6G7YFZVHRYAY51J0YG9SDNJ","sc-machin-mcp","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fsupercli-machin-cli\u002Fskills\u002Fsc-machin-mcp\u002FSKILL.md",[75],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[77,78],"sc machin mcp","MCP",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":86,"publishedAt":40},"01M6G7YB179MQMSHZBJDC8TZA8","supercli.quickstart","SuperCLI capability router — discover and execute CLI commands through namespace.resource.action interface","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fskills\u002Fsupercli\u002FSKILL.md",[85],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[87,88,24,89,90,91,92,93,94,95,96,97],"supercli quickstart","quickstart","capability router","plugin","discovery","execute","router","discover","commands","interface","supercli,cli,plugin,capability,discovery,agent",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":40},"01M6G7Y734QS3793YMS5PR146J","zzdoc","Use this skill to compile scdoc manpages with a fast Zig-based compiler.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fzzdoc\u002Fskills\u002Fquickstart\u002FSKILL.md",[],[100,105,37,106,107,108,109],"with","zig","fast","compiler","compile",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":40},"01M6G7Y2WX56K2QJQ9RV2ZKEV7","zx","Use this skill when the user wants to a tool for writing better scripts using node.js.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fzx\u002Fskills\u002Fquickstart\u002FSKILL.md",[],[112,117,37,36,118,119,120,121],"scripts","node","tool","js","writing",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":40},"01M6G7Y0M792DGW31HN4TEQT10","zvm","Use this skill when the user wants to manage multiple Zig compiler versions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fzvm\u002Fskills\u002Fquickstart\u002FSKILL.md",[],[124,106,38,37,36,108],{"skillNo":130,"name":88,"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":131,"categories":132,"keywords":133,"publishedAt":40},"01M6G7XX51W5HJW09DYXBK92TJ","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fzstdmt\u002Fskills\u002Fquickstart\u002FSKILL.md",[],[88]]