[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DA0R672K2R2DC8N44W6GTS":3,"skill-same:01M7DA0R672K2R2DC8N44W6GTS":79},{"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":57,"commitSha":58,"skillDirectory":59,"forksCount":14,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M7DA0R672K2R2DC8N44W6GTS","Vitest Migration & Config",null,"Teaches the agent to migrate a Jest suite to Vitest — vi.mock and the globals shim, vitest.config workspaces\u002Fprojects, coverage, browser mode, and Vitest v4 breaking changes.","GrupoANDevelopment-m\u002Falberto-ai","GrupoANDevelopment-m","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257455179?v=4","01M7D69X2N2KEVN0SJF6WGM6SH","Antônio  Ndombe","01M7D69X3P5JTT8H8S904N3888",0,"MIT","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fvitest-migration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Vitest Migration & Config\ndescription: Teaches the agent to migrate a Jest suite to Vitest — vi.mock and the globals shim, vitest.config workspaces\u002Fprojects, coverage, browser mode, and Vitest v4 breaking changes.\nversion: 1.0.0\nauthor: thetestingacademy\nlicense: MIT\ntags: [vitest, migration, jest, vi-mock, config, coverage, browser-mode, projects]\ntestingTypes: [unit, integration]\nframeworks: [vitest, jest]\nlanguages: [typescript]\ndomains: [web, api]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt, gemini-cli, amp]\n---\n\n# Vitest Migration & Config\n\nThis skill makes the agent migrate a Jest test suite to Vitest correctly and configure Vitest from scratch. Vitest is mostly Jest-compatible, but the differences bite: the `vi` namespace replaces `jest`, `vi.mock` hoisting needs `vi.hoisted`, ESM is first-class, and Vitest v4 removed `workspace` files in favor of inline `projects`. The agent should produce a config that runs fast, types cleanly, and reports coverage.\n\nUse this skill when migrating from Jest, setting up `vitest.config.ts`, splitting unit vs browser tests, or resolving v4 upgrade breakage.\n\n## Core Principles\n\n1. **`vi` replaces `jest`.** `jest.fn` -> `vi.fn`, `jest.mock` -> `vi.mock`, `jest.spyOn` -> `vi.spyOn`, `jest.useFakeTimers` -> `vi.useFakeTimers`. The assertion API (`expect`, matchers) is unchanged.\n2. **Mocks must reset explicitly.** Set `test.clearMocks`\u002F`restoreMocks` in config or call `vi.clearAllMocks()` in `beforeEach` — Vitest does not reset by default.\n3. **`vi.mock` is hoisted; use `vi.hoisted` for shared values.** Variables the factory needs must be created via `vi.hoisted(() => ...)`, since the factory runs before imports.\n4. **Decide on globals up front.** Either enable `globals: true` (Jest-like, no imports) or import `{ describe, it, expect, vi }` from `vitest`. Pick one and add `types: ['vitest\u002Fglobals']` if using globals.\n5. **v4 uses `projects`, not `workspace`.** The standalone `vitest.workspace.ts` file is removed; declare multiple environments via the inline `projects` array.\n6. **Browser mode replaces jsdom for real-DOM tests.** Use `browser.instances` (v4) to run component tests in a real browser engine via Playwright.\n\n## Workflow \u002F Patterns\n\n### Pattern 1 — Mechanical Jest -> Vitest swap\n\nMost test bodies migrate with a namespace rename. With `globals: true`, even the imports can stay as-is.\n\n```typescript\n\u002F\u002F Before (Jest):\n\u002F\u002F   const fn = jest.fn();\n\u002F\u002F   jest.spyOn(obj, 'method');\n\u002F\u002F   jest.useFakeTimers();\n\n\u002F\u002F After (Vitest) — explicit imports (recommended, ESM-safe):\nimport { describe, it, expect, vi, beforeEach } from 'vitest';\n\ndescribe('cart', () => {\n  beforeEach(() => vi.clearAllMocks());\n\n  it('adds an item', () => {\n    const onChange = vi.fn();\n    const cart = createCart(onChange);\n    cart.add({ sku: 'A1', qty: 2 });\n\n    expect(cart.total).toBe(2);\n    expect(onChange).toHaveBeenCalledWith(expect.objectContaining({ sku: 'A1' }));\n  });\n});\n```\n\n### Pattern 2 — `vi.mock` with `vi.hoisted` (the hoisting fix)\n\nIn Jest you prefix variables with `mock`. In Vitest, wrap them in `vi.hoisted` so they exist when the hoisted factory runs.\n\n```typescript\nimport { vi, test, expect, beforeEach } from 'vitest';\nimport { getUser } from '.\u002Fuser-service';\nimport axios from 'axios';\n\n\u002F\u002F Create the spy in a hoisted block so the factory below can reference it.\nconst { mockGet } = vi.hoisted(() => ({ mockGet: vi.fn() }));\n\nvi.mock('axios', () => ({\n  default: { get: mockGet }, \u002F\u002F note: ESM default export shape\n}));\n\nbeforeEach(() => vi.clearAllMocks());\n\ntest('resolves user from API', async () => {\n  mockGet.mockResolvedValue({ data: { id: 1, name: 'Ada' } });\n\n  const user = await getUser(1);\n\n  expect(user).toEqual({ id: 1, name: 'Ada' });\n  expect(axios.get).toHaveBeenCalledWith('\u002Fapi\u002Fusers\u002F1');\n});\n```\n\n### Pattern 3 — Partial mock with `importActual`\n\nThe Vitest equivalent of `jest.requireActual`. The factory is async.\n\n```typescript\nvi.mock('.\u002Fconfig', async (importOriginal) => {\n  const actual = await importOriginal\u003Ctypeof import('.\u002Fconfig')>();\n  return {\n    ...actual,\n    isProduction: vi.fn(() => false), \u002F\u002F override one export, keep the rest real\n  };\n});\n```\n\n### Pattern 4 — A complete `vitest.config.ts`\n\nCovers globals, environment, setup files, and coverage. This replaces `jest.config.js`.\n\n```typescript\nimport { defineConfig } from 'vitest\u002Fconfig';\n\nexport default defineConfig({\n  test: {\n    globals: true, \u002F\u002F Jest-like; otherwise import from 'vitest'\n    environment: 'node', \u002F\u002F 'jsdom' for component DOM tests\n    setupFiles: ['.\u002Ftest\u002Fsetup.ts'],\n    clearMocks: true, \u002F\u002F reset vi.fn() call data before each test\n    restoreMocks: true, \u002F\u002F restore spies to original impl\n    coverage: {\n      provider: 'v8', \u002F\u002F fast, no instrumentation step\n      reporter: ['text', 'html', 'lcov'],\n      include: ['src\u002F**\u002F*.ts'],\n      exclude: ['src\u002F**\u002F*.d.ts', 'src\u002F**\u002Findex.ts'],\n      thresholds: { lines: 80, functions: 80, branches: 75 },\n    },\n  },\n});\n```\n\nIf using `globals: true`, add to `tsconfig.json`:\n\n```json\n{ \"compilerOptions\": { \"types\": [\"vitest\u002Fglobals\"] } }\n```\n\n### Pattern 5 — Multiple environments via `projects` (v4)\n\nThe v4 replacement for `vitest.workspace.ts`. Run Node unit tests and jsdom component tests in one command, each with its own config.\n\n```typescript\nimport { defineConfig } from 'vitest\u002Fconfig';\n\nexport default defineConfig({\n  test: {\n    coverage: { provider: 'v8' },\n    projects: [\n      {\n        \u002F\u002F Fast pure-logic tests in Node.\n        test: {\n          name: 'unit',\n          environment: 'node',\n          include: ['src\u002F**\u002F*.unit.test.ts'],\n        },\n      },\n      {\n        \u002F\u002F DOM\u002Fcomponent tests in jsdom.\n        test: {\n          name: 'dom',\n          environment: 'jsdom',\n          setupFiles: ['.\u002Ftest\u002Fdom-setup.ts'],\n          include: ['src\u002F**\u002F*.dom.test.ts'],\n        },\n      },\n    ],\n  },\n});\n```\n\n### Pattern 6 — Browser mode (real engine, v4 `instances`)\n\nFor component tests that need a real browser. v4 replaced the singular `browser.name` with a `browser.instances` array.\n\n```typescript\nimport { defineConfig } from 'vitest\u002Fconfig';\n\nexport default defineConfig({\n  test: {\n    browser: {\n      enabled: true,\n      provider: 'playwright',\n      headless: true,\n      instances: [\n        { browser: 'chromium' },\n        { browser: 'firefox' },\n      ],\n    },\n  },\n});\n```\n\n```typescript\n\u002F\u002F component.browser.test.ts — runs in a real browser\nimport { render } from 'vitest-browser-react';\nimport { expect, test } from 'vitest';\nimport { Counter } from '.\u002FCounter';\n\ntest('increments in a real browser', async () => {\n  const screen = render(\u003CCounter \u002F>);\n  await screen.getByRole('button', { name: 'Increment' }).click();\n  await expect.element(screen.getByText('Count: 1')).toBeVisible();\n});\n```\n\n### Pattern 7 — package.json scripts and the runner\n\n```json\n{\n  \"scripts\": {\n    \"test\": \"vitest run\",\n    \"test:watch\": \"vitest\",\n    \"test:ui\": \"vitest --ui\",\n    \"coverage\": \"vitest run --coverage\"\n  }\n}\n```\n\n## Best Practices\n\n1. **Choose globals vs imports once** and apply it suite-wide. If `globals: true`, add `types: ['vitest\u002Fglobals']` so TypeScript knows `expect`\u002F`vi`.\n2. **Set `clearMocks` and `restoreMocks` in config** — Vitest does not auto-reset, so omitting them recreates Jest's \"leaky mock\" bug.\n3. **Use `vi.hoisted` for any value a `vi.mock` factory references.** This is the single most common migration failure.\n4. **Mock ESM default exports as `{ default: ... }`** in the factory — the shape differs from Jest's CJS interop.\n5. **Use the `v8` coverage provider** for speed; reserve `istanbul` only if you need its specific report nuances.\n6. **Split slow DOM\u002Fbrowser tests into a separate `project`** so the fast Node unit tests give quick feedback.\n7. **On v4 upgrade, replace `vitest.workspace.ts` with inline `projects`** and convert `browser.name` to `browser.instances`.\n\n## Anti-Patterns\n\n1. **Search-replacing `jest` -> `vi` and assuming you're done.** Mock hoisting and ESM default shapes still need `vi.hoisted` and `{ default }`.\n2. **Forgetting mocks reset** because Vitest, unlike a default Jest setup, won't clear them for you.\n3. **Referencing an outer variable in `vi.mock` without `vi.hoisted`.** It is `undefined` when the hoisted factory executes.\n4. **Keeping `vitest.workspace.ts` on v4.** It is removed; the suite silently ignores it or errors. Use `projects`.\n5. **Enabling `globals: true` but not adding `vitest\u002Fglobals` types**, producing a flood of \"cannot find name 'expect'\" TS errors.\n6. **Running everything in jsdom** when most tests are pure logic — jsdom is slower and unnecessary. Default to `node`.\n7. **Mixing `@jest\u002Fglobals` imports into Vitest files** — import from `vitest` instead.\n\n## When to Trigger This Skill\n\n- \"Migrate my Jest tests to Vitest\"\n- \"Set up `vitest.config.ts`\" \u002F \"configure Vitest coverage\"\n- \"`vi.mock` isn't working \u002F variable is undefined in the factory\"\n- \"How do I mock a default ESM export in Vitest?\"\n- \"Run component tests in a real browser with Vitest\"\n- \"Vitest v4 broke my `workspace` \u002F `browser.name` config\"\n- \"Split unit and DOM tests into projects\"\n- \"Jest `requireActual` equivalent in Vitest\"\n","# Vitest Migration & Config\n\nThis skill makes the agent migrate a Jest test suite to Vitest correctly and configure Vitest from scratch. Vitest is mostly Jest-compatible, but the differences bite: the `vi` namespace replaces `jest`, `vi.mock` hoisting needs `vi.hoisted`, ESM is first-class, and Vitest v4 removed `workspace` files in favor of inline `projects`. The agent should produce a config that runs fast, types cleanly, and reports coverage.\n\nUse this skill when migrating from Jest, setting up `vitest.config.ts`, splitting unit vs browser tests, or resolving v4 upgrade breakage.\n\n## Core Principles\n\n1. **`vi` replaces `jest`.** `jest.fn` -> `vi.fn`, `jest.mock` -> `vi.mock`, `jest.spyOn` -> `vi.spyOn`, `jest.useFakeTimers` -> `vi.useFakeTimers`. The assertion API (`expect`, matchers) is unchanged.\n2. **Mocks must reset explicitly.** Set `test.clearMocks`\u002F`restoreMocks` in config or call `vi.clearAllMocks()` in `beforeEach` — Vitest does not reset by default.\n3. **`vi.mock` is hoisted; use `vi.hoisted` for shared values.** Variables the factory needs must be created via `vi.hoisted(() => ...)`, since the factory runs before imports.\n4. **Decide on globals up front.** Either enable `globals: true` (Jest-like, no imports) or import `{ describe, it, expect, vi }` from `vitest`. Pick one and add `types: ['vitest\u002Fglobals']` if using globals.\n5. **v4 uses `projects`, not `workspace`.** The standalone `vitest.workspace.ts` file is removed; declare multiple environments via the inline `projects` array.\n6. **Browser mode replaces jsdom for real-DOM tests.** Use `browser.instances` (v4) to run component tests in a real browser engine via Playwright.\n\n## Workflow \u002F Patterns\n\n### Pattern 1 — Mechanical Jest -> Vitest swap\n\nMost test bodies migrate with a namespace rename. With `globals: true`, even the imports can stay as-is.\n\n```typescript\n\u002F\u002F Before (Jest):\n\u002F\u002F   const fn = jest.fn();\n\u002F\u002F   jest.spyOn(obj, 'method');\n\u002F\u002F   jest.useFakeTimers();\n\n\u002F\u002F After (Vitest) — explicit imports (recommended, ESM-safe):\nimport { describe, it, expect, vi, beforeEach } from 'vitest';\n\ndescribe('cart', () => {\n  beforeEach(() => vi.clearAllMocks());\n\n  it('adds an item', () => {\n    const onChange = vi.fn();\n    const cart = createCart(onChange);\n    cart.add({ sku: 'A1', qty: 2 });\n\n    expect(cart.total).toBe(2);\n    expect(onChange).toHaveBeenCalledWith(expect.objectContaining({ sku: 'A1' }));\n  });\n});\n```\n\n### Pattern 2 — `vi.mock` with `vi.hoisted` (the hoisting fix)\n\nIn Jest you prefix variables with `mock`. In Vitest, wrap them in `vi.hoisted` so they exist when the hoisted factory runs.\n\n```typescript\nimport { vi, test, expect, beforeEach } from 'vitest';\nimport { getUser } from '.\u002Fuser-service';\nimport axios from 'axios';\n\n\u002F\u002F Create the spy in a hoisted block so the factory below can reference it.\nconst { mockGet } = vi.hoisted(() => ({ mockGet: vi.fn() }));\n\nvi.mock('axios', () => ({\n  default: { get: mockGet }, \u002F\u002F note: ESM default export shape\n}));\n\nbeforeEach(() => vi.clearAllMocks());\n\ntest('resolves user from API', async () => {\n  mockGet.mockResolvedValue({ data: { id: 1, name: 'Ada' } });\n\n  const user = await getUser(1);\n\n  expect(user).toEqual({ id: 1, name: 'Ada' });\n  expect(axios.get).toHaveBeenCalledWith('\u002Fapi\u002Fusers\u002F1');\n});\n```\n\n### Pattern 3 — Partial mock with `importActual`\n\nThe Vitest equivalent of `jest.requireActual`. The factory is async.\n\n```typescript\nvi.mock('.\u002Fconfig', async (importOriginal) => {\n  const actual = await importOriginal\u003Ctypeof import('.\u002Fconfig')>();\n  return {\n    ...actual,\n    isProduction: vi.fn(() => false), \u002F\u002F override one export, keep the rest real\n  };\n});\n```\n\n### Pattern 4 — A complete `vitest.config.ts`\n\nCovers globals, environment, setup files, and coverage. This replaces `jest.config.js`.\n\n```typescript\nimport { defineConfig } from 'vitest\u002Fconfig';\n\nexport default defineConfig({\n  test: {\n    globals: true, \u002F\u002F Jest-like; otherwise import from 'vitest'\n    environment: 'node', \u002F\u002F 'jsdom' for component DOM tests\n    setupFiles: ['.\u002Ftest\u002Fsetup.ts'],\n    clearMocks: true, \u002F\u002F reset vi.fn() call data before each test\n    restoreMocks: true, \u002F\u002F restore spies to original impl\n    coverage: {\n      provider: 'v8', \u002F\u002F fast, no instrumentation step\n      reporter: ['text', 'html', 'lcov'],\n      include: ['src\u002F**\u002F*.ts'],\n      exclude: ['src\u002F**\u002F*.d.ts', 'src\u002F**\u002Findex.ts'],\n      thresholds: { lines: 80, functions: 80, branches: 75 },\n    },\n  },\n});\n```\n\nIf using `globals: true`, add to `tsconfig.json`:\n\n```json\n{ \"compilerOptions\": { \"types\": [\"vitest\u002Fglobals\"] } }\n```\n\n### Pattern 5 — Multiple environments via `projects` (v4)\n\nThe v4 replacement for `vitest.workspace.ts`. Run Node unit tests and jsdom component tests in one command, each with its own config.\n\n```typescript\nimport { defineConfig } from 'vitest\u002Fconfig';\n\nexport default defineConfig({\n  test: {\n    coverage: { provider: 'v8' },\n    projects: [\n      {\n        \u002F\u002F Fast pure-logic tests in Node.\n        test: {\n          name: 'unit',\n          environment: 'node',\n          include: ['src\u002F**\u002F*.unit.test.ts'],\n        },\n      },\n      {\n        \u002F\u002F DOM\u002Fcomponent tests in jsdom.\n        test: {\n          name: 'dom',\n          environment: 'jsdom',\n          setupFiles: ['.\u002Ftest\u002Fdom-setup.ts'],\n          include: ['src\u002F**\u002F*.dom.test.ts'],\n        },\n      },\n    ],\n  },\n});\n```\n\n### Pattern 6 — Browser mode (real engine, v4 `instances`)\n\nFor component tests that need a real browser. v4 replaced the singular `browser.name` with a `browser.instances` array.\n\n```typescript\nimport { defineConfig } from 'vitest\u002Fconfig';\n\nexport default defineConfig({\n  test: {\n    browser: {\n      enabled: true,\n      provider: 'playwright',\n      headless: true,\n      instances: [\n        { browser: 'chromium' },\n        { browser: 'firefox' },\n      ],\n    },\n  },\n});\n```\n\n```typescript\n\u002F\u002F component.browser.test.ts — runs in a real browser\nimport { render } from 'vitest-browser-react';\nimport { expect, test } from 'vitest';\nimport { Counter } from '.\u002FCounter';\n\ntest('increments in a real browser', async () => {\n  const screen = render(\u003CCounter \u002F>);\n  await screen.getByRole('button', { name: 'Increment' }).click();\n  await expect.element(screen.getByText('Count: 1')).toBeVisible();\n});\n```\n\n### Pattern 7 — package.json scripts and the runner\n\n```json\n{\n  \"scripts\": {\n    \"test\": \"vitest run\",\n    \"test:watch\": \"vitest\",\n    \"test:ui\": \"vitest --ui\",\n    \"coverage\": \"vitest run --coverage\"\n  }\n}\n```\n\n## Best Practices\n\n1. **Choose globals vs imports once** and apply it suite-wide. If `globals: true`, add `types: ['vitest\u002Fglobals']` so TypeScript knows `expect`\u002F`vi`.\n2. **Set `clearMocks` and `restoreMocks` in config** — Vitest does not auto-reset, so omitting them recreates Jest's \"leaky mock\" bug.\n3. **Use `vi.hoisted` for any value a `vi.mock` factory references.** This is the single most common migration failure.\n4. **Mock ESM default exports as `{ default: ... }`** in the factory — the shape differs from Jest's CJS interop.\n5. **Use the `v8` coverage provider** for speed; reserve `istanbul` only if you need its specific report nuances.\n6. **Split slow DOM\u002Fbrowser tests into a separate `project`** so the fast Node unit tests give quick feedback.\n7. **On v4 upgrade, replace `vitest.workspace.ts` with inline `projects`** and convert `browser.name` to `browser.instances`.\n\n## Anti-Patterns\n\n1. **Search-replacing `jest` -> `vi` and assuming you're done.** Mock hoisting and ESM default shapes still need `vi.hoisted` and `{ default }`.\n2. **Forgetting mocks reset** because Vitest, unlike a default Jest setup, won't clear them for you.\n3. **Referencing an outer variable in `vi.mock` without `vi.hoisted`.** It is `undefined` when the hoisted factory executes.\n4. **Keeping `vitest.workspace.ts` on v4.** It is removed; the suite silently ignores it or errors. Use `projects`.\n5. **Enabling `globals: true` but not adding `vitest\u002Fglobals` types**, producing a flood of \"cannot find name 'expect'\" TS errors.\n6. **Running everything in jsdom** when most tests are pure logic — jsdom is slower and unnecessary. Default to `node`.\n7. **Mixing `@jest\u002Fglobals` imports into Vitest files** — import from `vitest` instead.\n\n## When to Trigger This Skill\n\n- \"Migrate my Jest tests to Vitest\"\n- \"Set up `vitest.config.ts`\" \u002F \"configure Vitest coverage\"\n- \"`vi.mock` isn't working \u002F variable is undefined in the factory\"\n- \"How do I mock a default ESM export in Vitest?\"\n- \"Run component tests in a real browser with Vitest\"\n- \"Vitest v4 broke my `workspace` \u002F `browser.name` config\"\n- \"Split unit and DOM tests into projects\"\n- \"Jest `requireActual` equivalent in Vitest\"\n",{"name":5,"tags":24,"agents":33,"author":46,"domains":47,"license":15,"version":50,"languages":51,"frameworks":53,"description":7,"testingTypes":54},[25,26,27,28,29,30,31,32],"vitest","migration","jest","vi-mock","config","coverage","browser-mode","projects",[34,35,36,37,38,39,40,41,42,43,44,45],"claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp","thetestingacademy",[48,49],"web","api","1.0.0",[52],"typescript",[25,27],[55,56],"unit","integration","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fvitest-migration","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m","https:\u002F\u002Fid-preview--d5bef06d-6c9e-4563-a3d4-a855b9d61610.lovable.app\u002F","Eu sou Antonio B. B. Ndombe \r\nEu sou um Pesquisador e desenvolvedor de sistema autonomia cognitivos, fundador de sistemas ODCs ( organismos digital conscientes)","2026-11-04 06:53:39",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Vitest Migration & Config\"",{"tool":71,"command":72},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Vitest Migration & Config\"",{"tool":74,"command":75},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Vitest Migration & Config\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fvitest-migration\u002FSKILL.md",true,[],[80,88,95,102,109,116],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DASC6FSCJP49JZBSK0NY1Z","nemoclaw-user-reference","Describes the NemoClaw integration layer and blueprint architecture and how they orchestrate compatible agent sandboxes. Use when looking up architecture, agent integration, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw agent architecture, nemoclaw plugin blueprint structure, nemoclaw vs openshell, which cli, nemoclaw cli, openshell cli, sandbox commands, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-reference\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7DAS5S79VK33XFGVAM2TFWF","nemoclaw-user-overview","Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-overview\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7DAS0PQEMET5MNGZ1ABSZVS","nemoclaw-user-monitor-sandbox","Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-monitor-sandbox\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7DARQYGF7E9A69VH6S3CGN9","nemoclaw-user-manage-sandboxes","Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-sandboxes\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7DARH8BRTG51TRCAB7YWDJ4","nemoclaw-user-manage-policy","Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access. Trigger keywords - customize nemoclaw network policy, sandbox egress policy configuration, nemoclaw integration policy examples, post-install policy setup, openshell approval workflow, policy preset, nemoclaw approve network requests, sandbox egress approval tui.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-policy\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7DARAT62M2VR37590VCZ5NS","nemoclaw-user-get-started","Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-get-started\u002FSKILL.md",[],[]]