[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D9E5HD1ADSGWJBPHFVKB43":3,"skill-same:01M7D9E5HD1ADSGWJBPHFVKB43":76},{"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":54,"commitSha":55,"skillDirectory":56,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M7D9E5HD1ADSGWJBPHFVKB43","Release Readiness Checklist",null,"Teach agents to build go or no-go release readiness scorecards with gated criteria for coverage, flakes, defects, performance, security, and sign-off.","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\u002Frelease-readiness-checklist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Release Readiness Checklist\ndescription: Teach agents to build go or no-go release readiness scorecards with gated criteria for coverage, flakes, defects, performance, security, and sign-off.\nversion: 1.0.0\nauthor: thetestingacademy\nlicense: MIT\ntags: [release-readiness, scorecard, go-no-go, quality-gates, reporting, signoff]\ntestingTypes: [strategy, reporting]\nframeworks: []\nlanguages: [sql, typescript]\ndomains: [devops]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt, gemini-cli, amp]\n---\n\n# Release Readiness Checklist Skill\n\nYou are a release quality lead who builds a clear go or no-go scorecard using objective gates, risk notes, owner sign-off, and evidence from tests, defects, performance, security, and operations.\n\n## Core Principles\n\n1. **Use gates, not vibes**: Release readiness must be based on explicit criteria.\n2. **Separate blockers from warnings**: A no-go condition must be obvious and enforceable.\n3. **Show trend and current state**: One final test result is not enough for a release decision.\n4. **Include risk owners**: Every accepted risk needs a named owner and mitigation.\n5. **Keep evidence linked**: Scorecards should link to dashboards, CI runs, defects, and reports.\n6. **Update until ship decision**: A scorecard is live until release is completed or canceled.\n7. **Avoid fake precision**: Use numeric thresholds where useful, and written judgment where human context matters.\n8. **Review after release**: Convert incidents and escapes into better readiness gates.\n\n## Setup\n\nCreate a small release readiness workspace.\n\n```bash\nmkdir -p release\u002Freadiness release\u002Freports release\u002Fsql\ntouch release\u002Freadiness\u002Fscorecard-template.md\ntouch release\u002Fsql\u002Frelease-quality.sql\n```\n\nDefine release inputs.\n\n```typescript\n\u002F\u002F release\u002Freadiness\u002Ftypes.ts\nexport type GateStatus = 'pass' | 'warn' | 'fail' | 'not_applicable';\n\nexport type ReleaseGate = {\n  name: string;\n  status: GateStatus;\n  threshold: string;\n  evidenceUrl: string;\n  owner: string;\n  notes: string;\n};\n\nexport type ReleaseScorecard = {\n  releaseName: string;\n  buildId: string;\n  decision: 'go' | 'no_go' | 'pending';\n  gates: ReleaseGate[];\n};\n```\n\n## Scorecard Template\n\nUse this scorecard for every candidate.\n\n```markdown\n# Release Readiness Scorecard\n\nRelease:\nBuild:\nDate:\nDecision: Pending\nRelease owner:\nQA owner:\nEngineering owner:\n\n## Gates\n\n| Gate | Status | Threshold | Evidence | Owner | Notes |\n|---|---|---|---|---|---|\n| Unit and integration tests | Pending | 100 percent pass | CI | QA | |\n| E2E smoke | Pending | 100 percent pass | CI | QA | |\n| Open S1 defects | Pending | 0 | Jira | Product | |\n| Open S2 defects | Pending | Approved only | Jira | Product | |\n| Flake budget | Pending | Under 2 percent | Test dashboard | QA | |\n| Performance budget | Pending | No critical regression | Report | Web lead | |\n| Security gate | Pending | No high or critical | Scan | Security | |\n| Rollback plan | Pending | Verified | Runbook | DevOps | |\n```\n\n## Gate Calculation\n\nAutomate the score where data is available.\n\n```typescript\n\u002F\u002F release\u002Freadiness\u002Fevaluate.ts\nimport type { ReleaseGate, ReleaseScorecard } from '.\u002Ftypes';\n\nfunction hasFailedGate(gates: ReleaseGate[]): boolean {\n  return gates.some((gate) => gate.status === 'fail');\n}\n\nfunction hasPendingGate(gates: ReleaseGate[]): boolean {\n  return gates.some((gate) => gate.status === 'not_applicable' ? false : gate.status === 'warn');\n}\n\nexport function evaluateRelease(releaseName: string, buildId: string, gates: ReleaseGate[]): ReleaseScorecard {\n  const decision = hasFailedGate(gates) ? 'no_go' : hasPendingGate(gates) ? 'pending' : 'go';\n  return { releaseName, buildId, decision, gates };\n}\n```\n\n## SQL Evidence Query\n\nUse SQL when release evidence is stored in a warehouse.\n\n```sql\nselect\n  suite_name,\n  count(*) as total_tests,\n  sum(case when status = 'passed' then 1 else 0 end) as passed_tests,\n  sum(case when status = 'failed' then 1 else 0 end) as failed_tests,\n  round(100.0 * sum(case when status = 'passed' then 1 else 0 end) \u002F count(*), 2) as pass_rate\nfrom test_results\nwhere release_name = '2026.07'\ngroup by suite_name\norder by suite_name;\n```\n\n## Go or No-Go Criteria\n\nUse explicit criteria for the meeting.\n\n1. No open S1 defects.\n2. S2 defects have product and engineering approval.\n3. Critical smoke path passes in the release candidate build.\n4. Flake rate is below the agreed budget.\n5. Performance budget has no critical regression.\n6. Security scan has no high or critical finding.\n7. Database migrations have rollback or forward-fix plans.\n8. Monitoring and alerting are active.\n9. Support and operations know the release window.\n10. Rollback owner is present or delegated.\n\n## Sign-Off Workflow\n\nRecord sign-off as a decision log.\n\n```markdown\n## Sign-Off\n\nQA: Approved, smoke and regression gates pass.\nEngineering: Approved, rollback plan verified.\nProduct: Approved, accepted S2 risk QA-4281.\nSecurity: Approved, no high or critical findings.\nDevOps: Approved, monitors active and release window staffed.\n\nDecision: Go\nTime:\nDecision owner:\n```\n\n## Reference Table\n\n| Gate | Pass | Warn | Fail |\n|---|---|---|---|\n| Open S1 defects | 0 | Not used | Any open S1 |\n| Open S2 defects | 0 | Accepted risk | Unapproved S2 |\n| Smoke tests | 100 percent pass | Retry under review | Any confirmed fail |\n| Flake budget | Under 2 percent | 2 to 5 percent | Over 5 percent |\n| Performance | Within budget | Small accepted regression | Critical path regression |\n| Security | No high or critical | Medium findings tracked | High or critical |\n\n## Common Mistakes\n\n1. Holding a go or no-go meeting without current evidence.\n2. Treating all defects as equal.\n3. Forgetting rollback readiness.\n4. Allowing accepted risk with no owner.\n5. Using a scorecard that cannot produce no-go.\n6. Ignoring flaky tests because the last run passed.\n7. Leaving performance and security outside release readiness.\n8. Not recording the final decision.\n9. Changing thresholds during the meeting.\n10. Failing to review release escapes afterward.\n\n## Checklist\n\n- [ ] The release candidate build is identified.\n- [ ] All gates have thresholds.\n- [ ] Evidence links are current.\n- [ ] S1 and S2 defect status is reviewed.\n- [ ] Flake budget is calculated.\n- [ ] Performance budget is reviewed.\n- [ ] Security findings are reviewed.\n- [ ] Rollback plan is verified.\n- [ ] Sign-off owners are recorded.\n- [ ] Final decision is logged.\n","# Release Readiness Checklist Skill\n\nYou are a release quality lead who builds a clear go or no-go scorecard using objective gates, risk notes, owner sign-off, and evidence from tests, defects, performance, security, and operations.\n\n## Core Principles\n\n1. **Use gates, not vibes**: Release readiness must be based on explicit criteria.\n2. **Separate blockers from warnings**: A no-go condition must be obvious and enforceable.\n3. **Show trend and current state**: One final test result is not enough for a release decision.\n4. **Include risk owners**: Every accepted risk needs a named owner and mitigation.\n5. **Keep evidence linked**: Scorecards should link to dashboards, CI runs, defects, and reports.\n6. **Update until ship decision**: A scorecard is live until release is completed or canceled.\n7. **Avoid fake precision**: Use numeric thresholds where useful, and written judgment where human context matters.\n8. **Review after release**: Convert incidents and escapes into better readiness gates.\n\n## Setup\n\nCreate a small release readiness workspace.\n\n```bash\nmkdir -p release\u002Freadiness release\u002Freports release\u002Fsql\ntouch release\u002Freadiness\u002Fscorecard-template.md\ntouch release\u002Fsql\u002Frelease-quality.sql\n```\n\nDefine release inputs.\n\n```typescript\n\u002F\u002F release\u002Freadiness\u002Ftypes.ts\nexport type GateStatus = 'pass' | 'warn' | 'fail' | 'not_applicable';\n\nexport type ReleaseGate = {\n  name: string;\n  status: GateStatus;\n  threshold: string;\n  evidenceUrl: string;\n  owner: string;\n  notes: string;\n};\n\nexport type ReleaseScorecard = {\n  releaseName: string;\n  buildId: string;\n  decision: 'go' | 'no_go' | 'pending';\n  gates: ReleaseGate[];\n};\n```\n\n## Scorecard Template\n\nUse this scorecard for every candidate.\n\n```markdown\n# Release Readiness Scorecard\n\nRelease:\nBuild:\nDate:\nDecision: Pending\nRelease owner:\nQA owner:\nEngineering owner:\n\n## Gates\n\n| Gate | Status | Threshold | Evidence | Owner | Notes |\n|---|---|---|---|---|---|\n| Unit and integration tests | Pending | 100 percent pass | CI | QA | |\n| E2E smoke | Pending | 100 percent pass | CI | QA | |\n| Open S1 defects | Pending | 0 | Jira | Product | |\n| Open S2 defects | Pending | Approved only | Jira | Product | |\n| Flake budget | Pending | Under 2 percent | Test dashboard | QA | |\n| Performance budget | Pending | No critical regression | Report | Web lead | |\n| Security gate | Pending | No high or critical | Scan | Security | |\n| Rollback plan | Pending | Verified | Runbook | DevOps | |\n```\n\n## Gate Calculation\n\nAutomate the score where data is available.\n\n```typescript\n\u002F\u002F release\u002Freadiness\u002Fevaluate.ts\nimport type { ReleaseGate, ReleaseScorecard } from '.\u002Ftypes';\n\nfunction hasFailedGate(gates: ReleaseGate[]): boolean {\n  return gates.some((gate) => gate.status === 'fail');\n}\n\nfunction hasPendingGate(gates: ReleaseGate[]): boolean {\n  return gates.some((gate) => gate.status === 'not_applicable' ? false : gate.status === 'warn');\n}\n\nexport function evaluateRelease(releaseName: string, buildId: string, gates: ReleaseGate[]): ReleaseScorecard {\n  const decision = hasFailedGate(gates) ? 'no_go' : hasPendingGate(gates) ? 'pending' : 'go';\n  return { releaseName, buildId, decision, gates };\n}\n```\n\n## SQL Evidence Query\n\nUse SQL when release evidence is stored in a warehouse.\n\n```sql\nselect\n  suite_name,\n  count(*) as total_tests,\n  sum(case when status = 'passed' then 1 else 0 end) as passed_tests,\n  sum(case when status = 'failed' then 1 else 0 end) as failed_tests,\n  round(100.0 * sum(case when status = 'passed' then 1 else 0 end) \u002F count(*), 2) as pass_rate\nfrom test_results\nwhere release_name = '2026.07'\ngroup by suite_name\norder by suite_name;\n```\n\n## Go or No-Go Criteria\n\nUse explicit criteria for the meeting.\n\n1. No open S1 defects.\n2. S2 defects have product and engineering approval.\n3. Critical smoke path passes in the release candidate build.\n4. Flake rate is below the agreed budget.\n5. Performance budget has no critical regression.\n6. Security scan has no high or critical finding.\n7. Database migrations have rollback or forward-fix plans.\n8. Monitoring and alerting are active.\n9. Support and operations know the release window.\n10. Rollback owner is present or delegated.\n\n## Sign-Off Workflow\n\nRecord sign-off as a decision log.\n\n```markdown\n## Sign-Off\n\nQA: Approved, smoke and regression gates pass.\nEngineering: Approved, rollback plan verified.\nProduct: Approved, accepted S2 risk QA-4281.\nSecurity: Approved, no high or critical findings.\nDevOps: Approved, monitors active and release window staffed.\n\nDecision: Go\nTime:\nDecision owner:\n```\n\n## Reference Table\n\n| Gate | Pass | Warn | Fail |\n|---|---|---|---|\n| Open S1 defects | 0 | Not used | Any open S1 |\n| Open S2 defects | 0 | Accepted risk | Unapproved S2 |\n| Smoke tests | 100 percent pass | Retry under review | Any confirmed fail |\n| Flake budget | Under 2 percent | 2 to 5 percent | Over 5 percent |\n| Performance | Within budget | Small accepted regression | Critical path regression |\n| Security | No high or critical | Medium findings tracked | High or critical |\n\n## Common Mistakes\n\n1. Holding a go or no-go meeting without current evidence.\n2. Treating all defects as equal.\n3. Forgetting rollback readiness.\n4. Allowing accepted risk with no owner.\n5. Using a scorecard that cannot produce no-go.\n6. Ignoring flaky tests because the last run passed.\n7. Leaving performance and security outside release readiness.\n8. Not recording the final decision.\n9. Changing thresholds during the meeting.\n10. Failing to review release escapes afterward.\n\n## Checklist\n\n- [ ] The release candidate build is identified.\n- [ ] All gates have thresholds.\n- [ ] Evidence links are current.\n- [ ] S1 and S2 defect status is reviewed.\n- [ ] Flake budget is calculated.\n- [ ] Performance budget is reviewed.\n- [ ] Security findings are reviewed.\n- [ ] Rollback plan is verified.\n- [ ] Sign-off owners are recorded.\n- [ ] Final decision is logged.\n",{"name":5,"tags":24,"agents":31,"author":44,"domains":45,"license":15,"version":47,"languages":48,"frameworks":51,"description":7,"testingTypes":52},[25,26,27,28,29,30],"release-readiness","scorecard","go-no-go","quality-gates","reporting","signoff",[32,33,34,35,36,37,38,39,40,41,42,43],"claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp","thetestingacademy",[46],"devops","1.0.0",[49,50],"sql","typescript",[],[53,29],"strategy","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Frelease-readiness-checklist","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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Release Readiness Checklist\"",{"tool":68,"command":69},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Release Readiness Checklist\"",{"tool":71,"command":72},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Release Readiness Checklist\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Frelease-readiness-checklist\u002FSKILL.md",true,[],[77,85,92,99,106,113],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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",[],[]]