[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D8WRX2KWZGSW467J205V0R":3,"skill-same:01M7D8WRX2KWZGSW467J205V0R":78},{"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":56,"commitSha":57,"skillDirectory":58,"forksCount":14,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M7D8WRX2KWZGSW467J205V0R","Maestro Mobile Testing",null,"Black-box mobile UI testing with Maestro YAML flows - launchApp, tapOn, inputText, assertVisible, reusable runFlow subflows, environment parameters, JUnit reporting, and emulator-based CI pipelines.","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\u002Fmaestro-mobile\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Maestro Mobile Testing\ndescription: Black-box mobile UI testing with Maestro YAML flows - launchApp, tapOn, inputText, assertVisible, reusable runFlow subflows, environment parameters, JUnit reporting, and emulator-based CI pipelines.\nversion: 1.0.0\nauthor: thetestingacademy\nlicense: MIT\ntags: [maestro, mobile, e2e, ios, android, yaml, flows, ui-testing, flutter, react-native]\ntestingTypes: [mobile, e2e]\nframeworks: [appium]\nlanguages: [typescript]\ndomains: [mobile]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt, gemini-cli, amp]\n---\n\n# Maestro Mobile Testing\n\nThis skill makes an AI agent write Maestro flows - declarative YAML files that drive iOS and Android apps black-box style with built-in waiting, no test harness compiled into the app, and no WebDriver session management. Trigger it when a repository contains a `.maestro\u002F` directory or `*.yaml` flows with `appId:` headers, or when the user wants fast, low-maintenance smoke tests for a native, React Native, or Flutter app without the weight of Appium.\n\n## Core Principles\n\n1. **Maestro waits by default; do not teach it to sleep.** Every `tapOn` and `assertVisible` polls until the element appears or a timeout expires. Reach for `extendedWaitUntil` for slow screens; never add fixed delays as a first resort.\n2. **One flow per user-visible behavior.** A flow named `checkout-with-saved-card.yaml` that does exactly that is debuggable. A 200-line `regression.yaml` is not. Compose bigger journeys from subflows with `runFlow`.\n3. **Select by accessibility id first, visible text second.** `tapOn: id: \"submit-button\"` survives copy changes and localization; text selectors are acceptable for stable, single-language labels only.\n4. **Start from a clean, deterministic state.** `launchApp` with `clearState: true` resets the app between flows; tests that inherit the previous flow's logged-in session fail in random orders.\n5. **Parameterize with env, not copies.** Credentials and hosts go in `env:` blocks or `-e KEY=value` CLI arguments so the same flow runs against dev, staging, and CI builds.\n6. **Treat flows as code.** They live in the repo next to the app, run on every PR via emulator CI, and produce JUnit XML that the pipeline understands.\n\n## Setup\n\n```bash\n# Install the Maestro CLI\ncurl -fsSL \"https:\u002F\u002Fget.maestro.mobile.dev\" | bash\nexport PATH=\"$PATH:$HOME\u002F.maestro\u002Fbin\"\nmaestro --version\n\n# Run one flow against the booted simulator\u002Femulator\nmaestro test .maestro\u002Flogin.yaml\n\n# Run the whole suite with JUnit output for CI\nmaestro test .maestro\u002F --format junit --output maestro-report.xml\n\n# Interactive selector explorer while authoring\nmaestro studio\n```\n\n## Patterns\n\n### 1. A complete login flow\n\n```yaml\n# .maestro\u002Flogin.yaml\nappId: com.example.shop\nenv:\n  EMAIL: qa@example.com\n  PASSWORD: Str0ngPass!\n---\n- launchApp:\n    clearState: true\n- tapOn: 'Log in'\n- tapOn:\n    id: 'email-input'\n- inputText: ${EMAIL}\n- tapOn:\n    id: 'password-input'\n- inputText: ${PASSWORD}\n- hideKeyboard\n- tapOn:\n    id: 'login-submit'\n- assertVisible: 'Welcome back'\n- assertNotVisible: 'Invalid email or password'\n- takeScreenshot: logged-in-home\n```\n\n### 2. Subflows with runFlow: compose journeys, handle one-off dialogs\n\n```yaml\n# .maestro\u002Fsubflows\u002Flogin.yaml -- reusable building block\nappId: com.example.shop\n---\n- launchApp:\n    clearState: true\n- tapOn: 'Log in'\n- tapOn:\n    id: 'email-input'\n- inputText: ${EMAIL}\n- tapOn:\n    id: 'password-input'\n- inputText: ${PASSWORD}\n- tapOn:\n    id: 'login-submit'\n- assertVisible:\n    id: 'home-screen'\n```\n\n```yaml\n# .maestro\u002Fcheckout.yaml -- the journey composes the subflow\nappId: com.example.shop\nenv:\n  EMAIL: qa@example.com\n  PASSWORD: Str0ngPass!\n---\n- runFlow: subflows\u002Flogin.yaml\n\n# Dismiss the push-permission prompt only if it appears\n- runFlow:\n    when:\n      visible: 'Allow notifications?'\n    commands:\n      - tapOn: 'Allow'\n\n- tapOn: 'Deals'\n- scrollUntilVisible:\n    element:\n      text: 'Wireless Headphones'\n    direction: DOWN\n    timeout: 20000\n- tapOn: 'Wireless Headphones'\n- tapOn:\n    id: 'add-to-cart'\n- tapOn:\n    id: 'cart-icon'\n- assertVisible: 'Wireless Headphones'\n- assertVisible:\n    text: 'Checkout'\n    enabled: true\n```\n\n### 3. Waiting, repeats, and assertions with conditions\n\n```yaml\n# .maestro\u002Forder-status.yaml\nappId: com.example.shop\n---\n- launchApp\n- tapOn:\n    id: 'tab-orders'\n\n# Wait up to 15s for async content instead of a blind sleep\n- extendedWaitUntil:\n    visible:\n      id: 'orders-list'\n    timeout: 15000\n\n# Pull-to-refresh until the order flips to Shipped, max 5 tries\n- repeat:\n    while:\n      notVisible: 'Shipped'\n    times: 5\n    commands:\n      - swipe:\n          direction: DOWN\n          duration: 400\n\n- assertVisible:\n    text: 'Shipped'\n- copyTextFrom:\n    id: 'order-number'\n- assertTrue: ${maestro.copiedText != ''}\n```\n\n### 4. CI: Android emulator on GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fmaestro-android.yml\nname: maestro-android\non: [pull_request]\n\njobs:\n  flows:\n    runs-on: ubuntu-latest\n    timeout-minutes: 40\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-java@v4\n        with:\n          distribution: temurin\n          java-version: 17\n      - name: Build debug APK\n        run: .\u002Fgradlew assembleDebug\n      - name: Install Maestro\n        run: |\n          curl -fsSL \"https:\u002F\u002Fget.maestro.mobile.dev\" | bash\n          echo \"$HOME\u002F.maestro\u002Fbin\" >> \"$GITHUB_PATH\"\n      - name: Run flows on emulator\n        uses: reactivecircus\u002Fandroid-emulator-runner@v2\n        with:\n          api-level: 34\n          arch: x86_64\n          profile: pixel_7\n          script: |\n            adb install app\u002Fbuild\u002Foutputs\u002Fapk\u002Fdebug\u002Fapp-debug.apk\n            maestro test .maestro\u002F --format junit --output maestro-report.xml \\\n              -e EMAIL=ci-bot@example.com -e PASSWORD=\"${{ secrets.TEST_USER_PASSWORD }}\"\n      - name: Publish report\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: maestro-report\n          path: |\n            maestro-report.xml\n            ~\u002F.maestro\u002Ftests\n```\n\nFor hosted device execution, the same suite uploads unchanged: `maestro cloud --api-key \"$MAESTRO_CLOUD_API_KEY\" app-debug.apk .maestro\u002F` runs every flow on cloud devices and returns a pass\u002Ffail exit code CI can gate on.\n\n## Best Practices\n\n- Use `maestro studio` to discover ids and text before writing selectors by hand; it shows exactly what the accessibility tree exposes.\n- Add accessibility identifiers in app code (`testID` in React Native, `accessibilityIdentifier` on iOS, `contentDescription`\u002F`resource-id` on Android) as part of feature work.\n- Keep shared steps in `subflows\u002F` and one top-level flow per journey; flows read top to bottom like a manual test script, keep them that readable.\n- Tag smoke flows with YAML `tags: [smoke]` and run `maestro test --include-tags smoke` on every PR, the full suite nightly.\n- Capture `takeScreenshot` at journey milestones; screenshots plus the JUnit report make CI failures diagnosable without a local repro.\n- Pin the emulator API level and profile in CI; device drift is the top source of \"passes locally\" mysteries.\n\n## Anti-Patterns\n\n- Sprinkling `- waitForAnimationToEnd` and long `extendedWaitUntil` timeouts everywhere to paper over an app that never settles; fix the spinner, not the test.\n- Selecting by index (`tapOn: point: 50%,30%` or index-based taps) for elements that have ids; coordinate taps break on every screen size.\n- One giant flow covering login, browse, checkout, refunds, and settings: a failure at step 40 costs a full re-run to debug.\n- Hardcoding production credentials in flow files; use `env:` plus CI secrets.\n- Running flows only on a developer's personal device before release instead of an emulator on every PR.\n- Re-implementing Appium-style page objects in JavaScript wrappers around Maestro; the YAML is the abstraction, keep logic out of it.\n\n## When to Trigger This Skill\n\n- A repository contains a `.maestro\u002F` directory, YAML files starting with `appId:`, or `maestro` commands in CI workflows.\n- The user wants mobile UI smoke tests with minimal setup, or asks to test a React Native, Flutter, or native app without Appium infrastructure.\n- An existing Appium suite is too slow or flaky for PR-level smoke coverage and the team wants a lighter black-box layer on top.\n- Mobile onboarding, login, or checkout journeys need regression coverage that designers and QA can read and edit.\n- Choose Maestro for declarative cross-platform flows; recommend Detox when the team needs gray-box React Native synchronization, or Appium when tests must script complex logic in a full programming language.\n","# Maestro Mobile Testing\n\nThis skill makes an AI agent write Maestro flows - declarative YAML files that drive iOS and Android apps black-box style with built-in waiting, no test harness compiled into the app, and no WebDriver session management. Trigger it when a repository contains a `.maestro\u002F` directory or `*.yaml` flows with `appId:` headers, or when the user wants fast, low-maintenance smoke tests for a native, React Native, or Flutter app without the weight of Appium.\n\n## Core Principles\n\n1. **Maestro waits by default; do not teach it to sleep.** Every `tapOn` and `assertVisible` polls until the element appears or a timeout expires. Reach for `extendedWaitUntil` for slow screens; never add fixed delays as a first resort.\n2. **One flow per user-visible behavior.** A flow named `checkout-with-saved-card.yaml` that does exactly that is debuggable. A 200-line `regression.yaml` is not. Compose bigger journeys from subflows with `runFlow`.\n3. **Select by accessibility id first, visible text second.** `tapOn: id: \"submit-button\"` survives copy changes and localization; text selectors are acceptable for stable, single-language labels only.\n4. **Start from a clean, deterministic state.** `launchApp` with `clearState: true` resets the app between flows; tests that inherit the previous flow's logged-in session fail in random orders.\n5. **Parameterize with env, not copies.** Credentials and hosts go in `env:` blocks or `-e KEY=value` CLI arguments so the same flow runs against dev, staging, and CI builds.\n6. **Treat flows as code.** They live in the repo next to the app, run on every PR via emulator CI, and produce JUnit XML that the pipeline understands.\n\n## Setup\n\n```bash\n# Install the Maestro CLI\ncurl -fsSL \"https:\u002F\u002Fget.maestro.mobile.dev\" | bash\nexport PATH=\"$PATH:$HOME\u002F.maestro\u002Fbin\"\nmaestro --version\n\n# Run one flow against the booted simulator\u002Femulator\nmaestro test .maestro\u002Flogin.yaml\n\n# Run the whole suite with JUnit output for CI\nmaestro test .maestro\u002F --format junit --output maestro-report.xml\n\n# Interactive selector explorer while authoring\nmaestro studio\n```\n\n## Patterns\n\n### 1. A complete login flow\n\n```yaml\n# .maestro\u002Flogin.yaml\nappId: com.example.shop\nenv:\n  EMAIL: qa@example.com\n  PASSWORD: Str0ngPass!\n---\n- launchApp:\n    clearState: true\n- tapOn: 'Log in'\n- tapOn:\n    id: 'email-input'\n- inputText: ${EMAIL}\n- tapOn:\n    id: 'password-input'\n- inputText: ${PASSWORD}\n- hideKeyboard\n- tapOn:\n    id: 'login-submit'\n- assertVisible: 'Welcome back'\n- assertNotVisible: 'Invalid email or password'\n- takeScreenshot: logged-in-home\n```\n\n### 2. Subflows with runFlow: compose journeys, handle one-off dialogs\n\n```yaml\n# .maestro\u002Fsubflows\u002Flogin.yaml -- reusable building block\nappId: com.example.shop\n---\n- launchApp:\n    clearState: true\n- tapOn: 'Log in'\n- tapOn:\n    id: 'email-input'\n- inputText: ${EMAIL}\n- tapOn:\n    id: 'password-input'\n- inputText: ${PASSWORD}\n- tapOn:\n    id: 'login-submit'\n- assertVisible:\n    id: 'home-screen'\n```\n\n```yaml\n# .maestro\u002Fcheckout.yaml -- the journey composes the subflow\nappId: com.example.shop\nenv:\n  EMAIL: qa@example.com\n  PASSWORD: Str0ngPass!\n---\n- runFlow: subflows\u002Flogin.yaml\n\n# Dismiss the push-permission prompt only if it appears\n- runFlow:\n    when:\n      visible: 'Allow notifications?'\n    commands:\n      - tapOn: 'Allow'\n\n- tapOn: 'Deals'\n- scrollUntilVisible:\n    element:\n      text: 'Wireless Headphones'\n    direction: DOWN\n    timeout: 20000\n- tapOn: 'Wireless Headphones'\n- tapOn:\n    id: 'add-to-cart'\n- tapOn:\n    id: 'cart-icon'\n- assertVisible: 'Wireless Headphones'\n- assertVisible:\n    text: 'Checkout'\n    enabled: true\n```\n\n### 3. Waiting, repeats, and assertions with conditions\n\n```yaml\n# .maestro\u002Forder-status.yaml\nappId: com.example.shop\n---\n- launchApp\n- tapOn:\n    id: 'tab-orders'\n\n# Wait up to 15s for async content instead of a blind sleep\n- extendedWaitUntil:\n    visible:\n      id: 'orders-list'\n    timeout: 15000\n\n# Pull-to-refresh until the order flips to Shipped, max 5 tries\n- repeat:\n    while:\n      notVisible: 'Shipped'\n    times: 5\n    commands:\n      - swipe:\n          direction: DOWN\n          duration: 400\n\n- assertVisible:\n    text: 'Shipped'\n- copyTextFrom:\n    id: 'order-number'\n- assertTrue: ${maestro.copiedText != ''}\n```\n\n### 4. CI: Android emulator on GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fmaestro-android.yml\nname: maestro-android\non: [pull_request]\n\njobs:\n  flows:\n    runs-on: ubuntu-latest\n    timeout-minutes: 40\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-java@v4\n        with:\n          distribution: temurin\n          java-version: 17\n      - name: Build debug APK\n        run: .\u002Fgradlew assembleDebug\n      - name: Install Maestro\n        run: |\n          curl -fsSL \"https:\u002F\u002Fget.maestro.mobile.dev\" | bash\n          echo \"$HOME\u002F.maestro\u002Fbin\" >> \"$GITHUB_PATH\"\n      - name: Run flows on emulator\n        uses: reactivecircus\u002Fandroid-emulator-runner@v2\n        with:\n          api-level: 34\n          arch: x86_64\n          profile: pixel_7\n          script: |\n            adb install app\u002Fbuild\u002Foutputs\u002Fapk\u002Fdebug\u002Fapp-debug.apk\n            maestro test .maestro\u002F --format junit --output maestro-report.xml \\\n              -e EMAIL=ci-bot@example.com -e PASSWORD=\"${{ secrets.TEST_USER_PASSWORD }}\"\n      - name: Publish report\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: maestro-report\n          path: |\n            maestro-report.xml\n            ~\u002F.maestro\u002Ftests\n```\n\nFor hosted device execution, the same suite uploads unchanged: `maestro cloud --api-key \"$MAESTRO_CLOUD_API_KEY\" app-debug.apk .maestro\u002F` runs every flow on cloud devices and returns a pass\u002Ffail exit code CI can gate on.\n\n## Best Practices\n\n- Use `maestro studio` to discover ids and text before writing selectors by hand; it shows exactly what the accessibility tree exposes.\n- Add accessibility identifiers in app code (`testID` in React Native, `accessibilityIdentifier` on iOS, `contentDescription`\u002F`resource-id` on Android) as part of feature work.\n- Keep shared steps in `subflows\u002F` and one top-level flow per journey; flows read top to bottom like a manual test script, keep them that readable.\n- Tag smoke flows with YAML `tags: [smoke]` and run `maestro test --include-tags smoke` on every PR, the full suite nightly.\n- Capture `takeScreenshot` at journey milestones; screenshots plus the JUnit report make CI failures diagnosable without a local repro.\n- Pin the emulator API level and profile in CI; device drift is the top source of \"passes locally\" mysteries.\n\n## Anti-Patterns\n\n- Sprinkling `- waitForAnimationToEnd` and long `extendedWaitUntil` timeouts everywhere to paper over an app that never settles; fix the spinner, not the test.\n- Selecting by index (`tapOn: point: 50%,30%` or index-based taps) for elements that have ids; coordinate taps break on every screen size.\n- One giant flow covering login, browse, checkout, refunds, and settings: a failure at step 40 costs a full re-run to debug.\n- Hardcoding production credentials in flow files; use `env:` plus CI secrets.\n- Running flows only on a developer's personal device before release instead of an emulator on every PR.\n- Re-implementing Appium-style page objects in JavaScript wrappers around Maestro; the YAML is the abstraction, keep logic out of it.\n\n## When to Trigger This Skill\n\n- A repository contains a `.maestro\u002F` directory, YAML files starting with `appId:`, or `maestro` commands in CI workflows.\n- The user wants mobile UI smoke tests with minimal setup, or asks to test a React Native, Flutter, or native app without Appium infrastructure.\n- An existing Appium suite is too slow or flaky for PR-level smoke coverage and the team wants a lighter black-box layer on top.\n- Mobile onboarding, login, or checkout journeys need regression coverage that designers and QA can read and edit.\n- Choose Maestro for declarative cross-platform flows; recommend Detox when the team needs gray-box React Native synchronization, or Appium when tests must script complex logic in a full programming language.\n",{"name":5,"tags":24,"agents":35,"author":48,"domains":49,"license":15,"version":50,"languages":51,"frameworks":53,"description":7,"testingTypes":55},[25,26,27,28,29,30,31,32,33,34],"maestro","mobile","e2e","ios","android","yaml","flows","ui-testing","flutter","react-native",[36,37,38,39,40,41,42,43,44,45,46,47],"claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp","thetestingacademy",[26],"1.0.0",[52],"typescript",[54],"appium",[26,27],"main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fmaestro-mobile","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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Maestro Mobile Testing\"",{"tool":70,"command":71},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Maestro Mobile Testing\"",{"tool":73,"command":74},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Maestro Mobile Testing\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fmaestro-mobile\u002FSKILL.md",true,[],[79,87,94,101,108,115],{"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":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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",[],[]]