[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D86VWP1845J2CDY9CSXFF6":3,"skill-same:01M7D86VWP1845J2CDY9CSXFF6":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},"01M7D86VWP1845J2CDY9CSXFF6","CI Test Sharding Parallelization",null,"Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.","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\u002Fci-test-sharding-parallelization\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: CI Test Sharding Parallelization\ndescription: Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.\nversion: 1.0.0\nauthor: thetestingacademy\nlicense: MIT\ntags: [ci, sharding, parallelization, playwright, jest, pytest, test-performance]\ntestingTypes: [e2e, regression, performance]\nframeworks: [playwright, jest, pytest]\nlanguages: [typescript, python]\ndomains: [devops]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt, gemini-cli, amp]\n---\n\n# CI Test Sharding Parallelization Skill\n\nYou are a test infrastructure engineer who reduces CI wall-clock time by sharding and parallelizing test suites while preserving deterministic results, useful reports, and clear failure ownership.\n\n## Core Principles\n\n1. **Optimize wall-clock, not only CPU**: The goal is faster feedback for developers.\n2. **Shard deterministically**: The same commit and shard config should run the same test distribution unless balancing is intentional.\n3. **Merge reports reliably**: Parallel jobs must produce one readable result for humans and machines.\n4. **Keep setup cost visible**: Too many shards can waste time on repeated install and boot steps.\n5. **Balance long tests**: Historical timing can prevent one slow shard from dominating.\n6. **Fail clearly**: A failure should identify shard, test file, project, and artifact.\n7. **Avoid hidden order dependencies**: Sharding exposes tests that rely on shared state.\n8. **Tune gradually**: Increase shard count only after measuring queue time and overhead.\n\n## Setup\n\nCreate scripts for each framework.\n\n```bash\nnpm install --save-dev @playwright\u002Ftest jest jest-junit\npython -m venv .venv\n. .venv\u002Fbin\u002Factivate\npip install pytest pytest-xdist pytest-json-report\nmkdir -p test-results merged-reports\n```\n\nUse consistent environment variables.\n\n```bash\nexport SHARD_INDEX=1\nexport SHARD_TOTAL=4\nexport CI_NODE_INDEX=1\nexport CI_NODE_TOTAL=4\n```\n\n## Project Structure\n\n```text\nci\u002F\n  sharding\u002F\n    playwright.yml\n    jest.yml\n    pytest.yml\nscripts\u002F\n  run-playwright-shard.sh\n  run-jest-shard.ts\n  run-pytest-shard.sh\n  merge-reports.sh\ntest-results\u002F\nmerged-reports\u002F\n```\n\n## Playwright Sharding\n\nUse the built-in Playwright shard flag.\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\n: \"${SHARD_INDEX:?SHARD_INDEX is required}\"\n: \"${SHARD_TOTAL:?SHARD_TOTAL is required}\"\n\nnpx playwright test \\\n  --shard=\"${SHARD_INDEX}\u002F${SHARD_TOTAL}\" \\\n  --reporter=blob \\\n  --output=\"test-results\u002Fplaywright-${SHARD_INDEX}\"\n```\n\nMerge Playwright blob reports after all shards finish.\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\nmkdir -p merged-reports\u002Fplaywright\nnpx playwright merge-reports --reporter html .\u002Fblob-report\n```\n\n## Jest Sharding\n\nUse Jest shard support when available.\n\n```typescript\n\u002F\u002F scripts\u002Frun-jest-shard.ts\nimport { spawnSync } from 'node:child_process';\n\nconst shardIndex = process.env.SHARD_INDEX || '1';\nconst shardTotal = process.env.SHARD_TOTAL || '1';\n\nconst result = spawnSync(\n  'npx',\n  [\n    'jest',\n    `--shard=${shardIndex}\u002F${shardTotal}`,\n    '--runInBand',\n    '--ci',\n    '--reporters=default',\n    '--reporters=jest-junit',\n  ],\n  { stdio: 'inherit' },\n);\n\nprocess.exit(result.status ?? 1);\n```\n\n## Pytest Parallelization\n\nUse xdist for process-level parallelism and CI matrix for sharding.\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\nPYTEST_WORKERS=\"${PYTEST_WORKERS:-auto}\"\nREPORT_FILE=\"test-results\u002Fpytest-${SHARD_INDEX:-1}.json\"\n\npytest tests \\\n  -n \"$PYTEST_WORKERS\" \\\n  --json-report \\\n  --json-report-file=\"$REPORT_FILE\"\n```\n\n## GitHub Actions Matrix\n\nUse matrix jobs for Playwright shards.\n\n```yaml\nname: sharded-tests\non:\n  pull_request:\njobs:\n  playwright:\n    runs-on: ubuntu-latest\n    strategy:\n      fail-fast: false\n      matrix:\n        shard: [1, 2, 3, 4]\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: 20\n      - run: npm ci\n      - run: npx playwright install --with-deps\n      - run: bash scripts\u002Frun-playwright-shard.sh\n        env:\n          SHARD_INDEX: ${{ matrix.shard }}\n          SHARD_TOTAL: 4\n      - uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: playwright-blob-${{ matrix.shard }}\n          path: blob-report\n```\n\n## Tuning Workflow\n\nMeasure before and after.\n\n1. Capture current test duration by suite and file.\n2. Identify setup time, test time, and queue time.\n3. Start with two or four shards.\n4. Compare total wall-clock time.\n5. Inspect slowest shard.\n6. Split slow files or rebalance.\n7. Check report merge quality.\n8. Confirm failure artifacts are still visible.\n9. Update branch protection names if required.\n10. Revisit shard count monthly.\n\n## Reference Table\n\n| Framework | Sharding Method | Report Merge |\n|---|---|---|\n| Playwright | `--shard=1\u002F4` | Blob report merge |\n| Jest | `--shard=1\u002F4` | JUnit aggregation |\n| pytest | Matrix plus xdist | JSON or JUnit merge |\n| Cypress | Dashboard or spec split | Dashboard report |\n| Large monorepo | Package filters | Per-package reports |\n| Slow E2E | Historical timing split | Custom manifest |\n\n## Common Mistakes\n\n1. Increasing shard count without measuring setup overhead.\n2. Losing artifacts from failing shards.\n3. Using fail-fast and canceling useful failure evidence.\n4. Forgetting to merge reports.\n5. Hiding order-dependent tests instead of fixing them.\n6. Running every shard against the same mutable account.\n7. Making branch protection require old job names.\n8. Creating more shards than available runners.\n9. Ignoring the slowest shard.\n10. Mixing parallel workers with unsafe shared database state.\n\n## Checklist\n\n- [ ] Baseline wall-clock time is recorded.\n- [ ] Shard count is justified by measurements.\n- [ ] Test data is safe for parallel runs.\n- [ ] Playwright shards use blob reports.\n- [ ] Jest or pytest reports are merged.\n- [ ] Artifacts include shard identifiers.\n- [ ] Fail-fast is disabled where evidence matters.\n- [ ] Slow shard is monitored.\n- [ ] Branch protection uses the correct checks.\n- [ ] Shard strategy is reviewed regularly.\n","# CI Test Sharding Parallelization Skill\n\nYou are a test infrastructure engineer who reduces CI wall-clock time by sharding and parallelizing test suites while preserving deterministic results, useful reports, and clear failure ownership.\n\n## Core Principles\n\n1. **Optimize wall-clock, not only CPU**: The goal is faster feedback for developers.\n2. **Shard deterministically**: The same commit and shard config should run the same test distribution unless balancing is intentional.\n3. **Merge reports reliably**: Parallel jobs must produce one readable result for humans and machines.\n4. **Keep setup cost visible**: Too many shards can waste time on repeated install and boot steps.\n5. **Balance long tests**: Historical timing can prevent one slow shard from dominating.\n6. **Fail clearly**: A failure should identify shard, test file, project, and artifact.\n7. **Avoid hidden order dependencies**: Sharding exposes tests that rely on shared state.\n8. **Tune gradually**: Increase shard count only after measuring queue time and overhead.\n\n## Setup\n\nCreate scripts for each framework.\n\n```bash\nnpm install --save-dev @playwright\u002Ftest jest jest-junit\npython -m venv .venv\n. .venv\u002Fbin\u002Factivate\npip install pytest pytest-xdist pytest-json-report\nmkdir -p test-results merged-reports\n```\n\nUse consistent environment variables.\n\n```bash\nexport SHARD_INDEX=1\nexport SHARD_TOTAL=4\nexport CI_NODE_INDEX=1\nexport CI_NODE_TOTAL=4\n```\n\n## Project Structure\n\n```text\nci\u002F\n  sharding\u002F\n    playwright.yml\n    jest.yml\n    pytest.yml\nscripts\u002F\n  run-playwright-shard.sh\n  run-jest-shard.ts\n  run-pytest-shard.sh\n  merge-reports.sh\ntest-results\u002F\nmerged-reports\u002F\n```\n\n## Playwright Sharding\n\nUse the built-in Playwright shard flag.\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\n: \"${SHARD_INDEX:?SHARD_INDEX is required}\"\n: \"${SHARD_TOTAL:?SHARD_TOTAL is required}\"\n\nnpx playwright test \\\n  --shard=\"${SHARD_INDEX}\u002F${SHARD_TOTAL}\" \\\n  --reporter=blob \\\n  --output=\"test-results\u002Fplaywright-${SHARD_INDEX}\"\n```\n\nMerge Playwright blob reports after all shards finish.\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\nmkdir -p merged-reports\u002Fplaywright\nnpx playwright merge-reports --reporter html .\u002Fblob-report\n```\n\n## Jest Sharding\n\nUse Jest shard support when available.\n\n```typescript\n\u002F\u002F scripts\u002Frun-jest-shard.ts\nimport { spawnSync } from 'node:child_process';\n\nconst shardIndex = process.env.SHARD_INDEX || '1';\nconst shardTotal = process.env.SHARD_TOTAL || '1';\n\nconst result = spawnSync(\n  'npx',\n  [\n    'jest',\n    `--shard=${shardIndex}\u002F${shardTotal}`,\n    '--runInBand',\n    '--ci',\n    '--reporters=default',\n    '--reporters=jest-junit',\n  ],\n  { stdio: 'inherit' },\n);\n\nprocess.exit(result.status ?? 1);\n```\n\n## Pytest Parallelization\n\nUse xdist for process-level parallelism and CI matrix for sharding.\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\nPYTEST_WORKERS=\"${PYTEST_WORKERS:-auto}\"\nREPORT_FILE=\"test-results\u002Fpytest-${SHARD_INDEX:-1}.json\"\n\npytest tests \\\n  -n \"$PYTEST_WORKERS\" \\\n  --json-report \\\n  --json-report-file=\"$REPORT_FILE\"\n```\n\n## GitHub Actions Matrix\n\nUse matrix jobs for Playwright shards.\n\n```yaml\nname: sharded-tests\non:\n  pull_request:\njobs:\n  playwright:\n    runs-on: ubuntu-latest\n    strategy:\n      fail-fast: false\n      matrix:\n        shard: [1, 2, 3, 4]\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: 20\n      - run: npm ci\n      - run: npx playwright install --with-deps\n      - run: bash scripts\u002Frun-playwright-shard.sh\n        env:\n          SHARD_INDEX: ${{ matrix.shard }}\n          SHARD_TOTAL: 4\n      - uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: playwright-blob-${{ matrix.shard }}\n          path: blob-report\n```\n\n## Tuning Workflow\n\nMeasure before and after.\n\n1. Capture current test duration by suite and file.\n2. Identify setup time, test time, and queue time.\n3. Start with two or four shards.\n4. Compare total wall-clock time.\n5. Inspect slowest shard.\n6. Split slow files or rebalance.\n7. Check report merge quality.\n8. Confirm failure artifacts are still visible.\n9. Update branch protection names if required.\n10. Revisit shard count monthly.\n\n## Reference Table\n\n| Framework | Sharding Method | Report Merge |\n|---|---|---|\n| Playwright | `--shard=1\u002F4` | Blob report merge |\n| Jest | `--shard=1\u002F4` | JUnit aggregation |\n| pytest | Matrix plus xdist | JSON or JUnit merge |\n| Cypress | Dashboard or spec split | Dashboard report |\n| Large monorepo | Package filters | Per-package reports |\n| Slow E2E | Historical timing split | Custom manifest |\n\n## Common Mistakes\n\n1. Increasing shard count without measuring setup overhead.\n2. Losing artifacts from failing shards.\n3. Using fail-fast and canceling useful failure evidence.\n4. Forgetting to merge reports.\n5. Hiding order-dependent tests instead of fixing them.\n6. Running every shard against the same mutable account.\n7. Making branch protection require old job names.\n8. Creating more shards than available runners.\n9. Ignoring the slowest shard.\n10. Mixing parallel workers with unsafe shared database state.\n\n## Checklist\n\n- [ ] Baseline wall-clock time is recorded.\n- [ ] Shard count is justified by measurements.\n- [ ] Test data is safe for parallel runs.\n- [ ] Playwright shards use blob reports.\n- [ ] Jest or pytest reports are merged.\n- [ ] Artifacts include shard identifiers.\n- [ ] Fail-fast is disabled where evidence matters.\n- [ ] Slow shard is monitored.\n- [ ] Branch protection uses the correct checks.\n- [ ] Shard strategy is reviewed regularly.\n",{"name":5,"tags":24,"agents":32,"author":45,"domains":46,"license":15,"version":48,"languages":49,"frameworks":52,"description":7,"testingTypes":53},[25,26,27,28,29,30,31],"ci","sharding","parallelization","playwright","jest","pytest","test-performance",[33,34,35,36,37,38,39,40,41,42,43,44],"claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp","thetestingacademy",[47],"devops","1.0.0",[50,51],"typescript","python",[28,29,30],[54,55,56],"e2e","regression","performance","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fci-test-sharding-parallelization","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 \"CI Test Sharding Parallelization\"",{"tool":71,"command":72},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"CI Test Sharding Parallelization\"",{"tool":74,"command":75},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"CI Test Sharding Parallelization\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fci-test-sharding-parallelization\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",[],[]]