[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D96NGFP93M3N91YP47C0RB":3,"skill-same:01M7D96NGFP93M3N91YP47C0RB":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},"01M7D96NGFP93M3N91YP47C0RB","Playwright Locator filter & Visibility",null,"Teaches the agent to build resilient Playwright locators with .filter (hasText\u002Fhas\u002FhasNot), narrow lists, and reason correctly about visibility, waitFor states, and timeouts.","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\u002Fplaywright-locator-filter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Playwright Locator filter & Visibility\ndescription: Teaches the agent to build resilient Playwright locators with .filter (hasText\u002Fhas\u002FhasNot), narrow lists, and reason correctly about visibility, waitFor states, and timeouts.\nversion: 1.0.0\nauthor: thetestingacademy\nlicense: MIT\ntags: [playwright, locator, filter, visibility, waitfor, hastext, resilient-locators, auto-wait]\ntestingTypes: [e2e, integration]\nframeworks: [playwright]\nlanguages: [typescript]\ndomains: [web]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt, gemini-cli, amp]\n---\n\n# Playwright Locator filter & Visibility\n\nThis skill makes the agent write locators that survive UI churn: role\u002Flabel-first selection, narrowed with `.filter({ hasText, has, hasNot })` instead of brittle CSS\u002FXPath, and correct reasoning about visibility — knowing when to use the auto-waiting `expect(...).toBeVisible()` versus the imperative `isVisible()` \u002F `waitFor()`. The recurring theme: **locators are lazy and re-resolve on every action**, and assertions auto-wait, so explicit sleeps and one-shot `isVisible()` checks are almost always wrong.\n\nUse this skill when a locator is flaky, matches multiple elements, depends on text or a child, or when the agent is tempted to add `waitForTimeout`.\n\n## Core Principles\n\n1. **Locators are lazy.** A `Locator` is a query, not an element. It re-resolves every time you act on it, so it tolerates re-renders. Define it once, use it repeatedly.\n2. **Filter, do not concatenate selectors.** Start from a semantic locator (`getByRole`) and narrow with `.filter({ hasText })`, `.filter({ has })`, or `.filter({ hasNot })` — not a long CSS chain.\n3. **`expect(locator).toBeVisible()` auto-waits; `locator.isVisible()` does not.** The assertion polls until the timeout; `isVisible()` returns a boolean *right now* with no waiting.\n4. **Never assert on a `count()` snapshot for dynamic lists.** Use `await expect(locator).toHaveCount(n)` which retries; `(await loc.count()) === n` is a race.\n5. **Prefer waiting for state over `waitForTimeout`.** `locator.waitFor({ state: 'visible' })` (or just acting on the locator) replaces arbitrary sleeps.\n6. **Scope timeouts at the assertion**, not globally — pass `{ timeout }` to the specific `expect`\u002Faction that genuinely needs longer.\n\n## Workflow \u002F Patterns\n\n### Pattern 1 — `filter({ hasText })` to pick one row out of many\n\nThe classic case: a table\u002Flist where rows share structure but differ by text.\n\n```typescript\nimport { test, expect } from '@playwright\u002Ftest';\n\ntest('acts on the right row via hasText', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Forders');\n\n  \u002F\u002F All rows share the same role; narrow to the one mentioning the order.\n  const row = page.getByRole('row').filter({ hasText: 'ORD-1042' });\n\n  await expect(row).toBeVisible();\n  await row.getByRole('button', { name: 'Cancel' }).click();\n\n  \u002F\u002F hasText accepts a RegExp for partial \u002F case-insensitive matching.\n  const refunded = page.getByRole('row').filter({ hasText: \u002Frefunded\u002Fi });\n  await expect(refunded).toHaveCount(1);\n});\n```\n\n### Pattern 2 — `filter({ has })` and `filter({ hasNot })` to match by descendant\n\nWhen rows can't be told apart by their own text, filter by a child element they contain (or lack).\n\n```typescript\ntest('filters cards by a child element', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Fproducts');\n\n  \u002F\u002F Only cards that CONTAIN a \"Sale\" badge.\n  const onSale = page\n    .getByRole('article')\n    .filter({ has: page.getByRole('img', { name: 'Sale' }) });\n  await expect(onSale.first()).toBeVisible();\n\n  \u002F\u002F Only cards that do NOT contain an \"Out of stock\" label.\n  const buyable = page\n    .getByRole('article')\n    .filter({ hasNot: page.getByText('Out of stock') });\n\n  \u002F\u002F Chain filters: buyable AND mentioning \"Pro\".\n  const target = buyable.filter({ hasText: 'Pro' });\n  await target.getByRole('button', { name: 'Add to cart' }).click();\n});\n```\n\n### Pattern 3 — Build resilient, chained locators (role-first)\n\nPrefer accessible roles\u002Flabels; chain to scope. Avoid index-based and deep CSS selectors.\n\n```typescript\ntest('uses resilient chained locators', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Fsettings');\n\n  \u002F\u002F Scope into a section, then target by role within it.\n  const billing = page.getByRole('region', { name: 'Billing' });\n  await billing.getByRole('button', { name: 'Update card' }).click();\n\n  \u002F\u002F Disambiguate same-named buttons by their surrounding text.\n  const proRow = page.getByTestId('plan-row').filter({ hasText: 'Pro' });\n  await proRow.getByRole('button', { name: 'Select' }).click();\n\n  \u002F\u002F getByText with { exact: true } when substring matches are too greedy.\n  await expect(page.getByText('Plan updated', { exact: true })).toBeVisible();\n});\n```\n\n### Pattern 4 — Visibility: assertion (auto-wait) vs `isVisible()` (instant)\n\nThis is the most common mistake. Use the assertion to *wait*; use `isVisible()` only for branching on current state.\n\n```typescript\ntest('handles visibility correctly', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com');\n\n  \u002F\u002F CORRECT: auto-waits up to the timeout for the toast to appear.\n  await page.getByRole('button', { name: 'Save' }).click();\n  await expect(page.getByRole('status')).toBeVisible({ timeout: 10_000 });\n\n  \u002F\u002F CORRECT use of isVisible(): branch on whether an optional banner exists.\n  const banner = page.getByRole('alert', { name: 'Cookie consent' });\n  if (await banner.isVisible()) {\n    await banner.getByRole('button', { name: 'Accept' }).click();\n  }\n\n  \u002F\u002F WRONG (do not do this): isVisible() does not wait, so this races a fade-in.\n  \u002F\u002F expect(await toast.isVisible()).toBe(true);\n});\n```\n\n### Pattern 5 — `waitFor({ state })` for appearance, detachment, and hiding\n\nUse `waitFor` when you need to block on a state transition without performing an action.\n\n```typescript\ntest('waits for explicit element states', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Fupload');\n\n  const spinner = page.getByRole('progressbar');\n\n  await page.getByRole('button', { name: 'Start upload' }).click();\n  await spinner.waitFor({ state: 'visible' });\n\n  \u002F\u002F Block until the spinner is gone before asserting success.\n  await spinner.waitFor({ state: 'hidden', timeout: 30_000 });\n  await expect(page.getByText('Upload complete')).toBeVisible();\n\n  \u002F\u002F 'attached' \u002F 'detached' for elements added\u002Fremoved from the DOM entirely.\n  const modal = page.getByRole('dialog');\n  await modal.waitFor({ state: 'detached' });\n});\n```\n\n### Pattern 6 — Iterate and assert over a filtered set\n\nCombine `filter` with `all()` \u002F `nth` \u002F `toHaveCount` for list assertions.\n\n```typescript\ntest('asserts across a filtered list', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Finbox');\n\n  const unread = page.getByRole('listitem').filter({ has: page.getByTestId('unread-dot') });\n\n  \u002F\u002F Retrying count assertion — waits for the list to settle.\n  await expect(unread).toHaveCount(3);\n\n  \u002F\u002F Per-item assertions.\n  for (const item of await unread.all()) {\n    await expect(item.getByRole('heading')).toBeVisible();\n  }\n\n  \u002F\u002F Act on the first\u002Flast match of the filtered set.\n  await unread.first().click();\n  await expect(page.getByTestId('unread-dot')).toHaveCount(2);\n});\n```\n\n## Best Practices\n\n1. **Start every locator from `getByRole`\u002F`getByLabel`\u002F`getByText`**, then narrow with `.filter(...)`. Reserve CSS\u002FXPath for cases the accessibility tree can't express.\n2. **Use `.filter({ has })` \u002F `.filter({ hasNot })`** to select by descendant when text alone is ambiguous; chain filters for AND logic.\n3. **Assert visibility with `await expect(locator).toBeVisible()`** so it auto-waits; reserve `isVisible()` for `if` branches on optional UI.\n4. **Use `toHaveCount(n)`** for dynamic lists — it retries — instead of comparing `await locator.count()`.\n5. **Replace `waitForTimeout` with `locator.waitFor({ state })`** or simply acting on the locator (which auto-waits).\n6. **Pass `{ timeout }` to the specific assertion** that needs longer rather than inflating the global timeout.\n7. **Define a locator once as a `const`** and reuse it — it re-resolves on each use, so it stays valid across re-renders.\n\n## Anti-Patterns\n\n1. **`page.locator('.row:nth-child(3) .btn.btn-danger')`.** Index- and class-based; breaks on reorder or restyle. Filter by role + text instead.\n2. **`expect(await loc.isVisible()).toBe(true)`.** No waiting — races animations and async renders. Use `await expect(loc).toBeVisible()`.\n3. **`if ((await loc.count()) === 2) {...}`.** Snapshot count is a race on dynamic lists. Use `toHaveCount`.\n4. **`await page.waitForTimeout(2000)` before clicking.** Arbitrary and flaky. Locators auto-wait; or use `waitFor({ state })`.\n5. **Selecting from a list by raw `.nth(4)`** without filtering — order is data-dependent. Filter to the meaningful item first.\n6. **One mega-CSS selector** stringing together five descendant combinators instead of chaining scoped locators.\n7. **Raising the global `timeout`** to mask one slow screen, slowing every other test's failure feedback.\n\n## When to Trigger This Skill\n\n- \"My locator matches multiple elements \u002F 'strict mode violation'\"\n- \"How do I select the table row that contains this text?\"\n- \"Use `filter` \u002F `hasText` \u002F `has` to narrow a locator\"\n- \"Difference between `isVisible()` and `toBeVisible()`\"\n- \"Wait for a spinner to disappear before asserting\"\n- \"My selector is brittle \u002F breaks when the UI changes\"\n- \"Assert how many items are in a dynamic list\"\n- \"Replace `waitForTimeout` with a proper wait\"\n","# Playwright Locator filter & Visibility\n\nThis skill makes the agent write locators that survive UI churn: role\u002Flabel-first selection, narrowed with `.filter({ hasText, has, hasNot })` instead of brittle CSS\u002FXPath, and correct reasoning about visibility — knowing when to use the auto-waiting `expect(...).toBeVisible()` versus the imperative `isVisible()` \u002F `waitFor()`. The recurring theme: **locators are lazy and re-resolve on every action**, and assertions auto-wait, so explicit sleeps and one-shot `isVisible()` checks are almost always wrong.\n\nUse this skill when a locator is flaky, matches multiple elements, depends on text or a child, or when the agent is tempted to add `waitForTimeout`.\n\n## Core Principles\n\n1. **Locators are lazy.** A `Locator` is a query, not an element. It re-resolves every time you act on it, so it tolerates re-renders. Define it once, use it repeatedly.\n2. **Filter, do not concatenate selectors.** Start from a semantic locator (`getByRole`) and narrow with `.filter({ hasText })`, `.filter({ has })`, or `.filter({ hasNot })` — not a long CSS chain.\n3. **`expect(locator).toBeVisible()` auto-waits; `locator.isVisible()` does not.** The assertion polls until the timeout; `isVisible()` returns a boolean *right now* with no waiting.\n4. **Never assert on a `count()` snapshot for dynamic lists.** Use `await expect(locator).toHaveCount(n)` which retries; `(await loc.count()) === n` is a race.\n5. **Prefer waiting for state over `waitForTimeout`.** `locator.waitFor({ state: 'visible' })` (or just acting on the locator) replaces arbitrary sleeps.\n6. **Scope timeouts at the assertion**, not globally — pass `{ timeout }` to the specific `expect`\u002Faction that genuinely needs longer.\n\n## Workflow \u002F Patterns\n\n### Pattern 1 — `filter({ hasText })` to pick one row out of many\n\nThe classic case: a table\u002Flist where rows share structure but differ by text.\n\n```typescript\nimport { test, expect } from '@playwright\u002Ftest';\n\ntest('acts on the right row via hasText', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Forders');\n\n  \u002F\u002F All rows share the same role; narrow to the one mentioning the order.\n  const row = page.getByRole('row').filter({ hasText: 'ORD-1042' });\n\n  await expect(row).toBeVisible();\n  await row.getByRole('button', { name: 'Cancel' }).click();\n\n  \u002F\u002F hasText accepts a RegExp for partial \u002F case-insensitive matching.\n  const refunded = page.getByRole('row').filter({ hasText: \u002Frefunded\u002Fi });\n  await expect(refunded).toHaveCount(1);\n});\n```\n\n### Pattern 2 — `filter({ has })` and `filter({ hasNot })` to match by descendant\n\nWhen rows can't be told apart by their own text, filter by a child element they contain (or lack).\n\n```typescript\ntest('filters cards by a child element', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Fproducts');\n\n  \u002F\u002F Only cards that CONTAIN a \"Sale\" badge.\n  const onSale = page\n    .getByRole('article')\n    .filter({ has: page.getByRole('img', { name: 'Sale' }) });\n  await expect(onSale.first()).toBeVisible();\n\n  \u002F\u002F Only cards that do NOT contain an \"Out of stock\" label.\n  const buyable = page\n    .getByRole('article')\n    .filter({ hasNot: page.getByText('Out of stock') });\n\n  \u002F\u002F Chain filters: buyable AND mentioning \"Pro\".\n  const target = buyable.filter({ hasText: 'Pro' });\n  await target.getByRole('button', { name: 'Add to cart' }).click();\n});\n```\n\n### Pattern 3 — Build resilient, chained locators (role-first)\n\nPrefer accessible roles\u002Flabels; chain to scope. Avoid index-based and deep CSS selectors.\n\n```typescript\ntest('uses resilient chained locators', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Fsettings');\n\n  \u002F\u002F Scope into a section, then target by role within it.\n  const billing = page.getByRole('region', { name: 'Billing' });\n  await billing.getByRole('button', { name: 'Update card' }).click();\n\n  \u002F\u002F Disambiguate same-named buttons by their surrounding text.\n  const proRow = page.getByTestId('plan-row').filter({ hasText: 'Pro' });\n  await proRow.getByRole('button', { name: 'Select' }).click();\n\n  \u002F\u002F getByText with { exact: true } when substring matches are too greedy.\n  await expect(page.getByText('Plan updated', { exact: true })).toBeVisible();\n});\n```\n\n### Pattern 4 — Visibility: assertion (auto-wait) vs `isVisible()` (instant)\n\nThis is the most common mistake. Use the assertion to *wait*; use `isVisible()` only for branching on current state.\n\n```typescript\ntest('handles visibility correctly', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com');\n\n  \u002F\u002F CORRECT: auto-waits up to the timeout for the toast to appear.\n  await page.getByRole('button', { name: 'Save' }).click();\n  await expect(page.getByRole('status')).toBeVisible({ timeout: 10_000 });\n\n  \u002F\u002F CORRECT use of isVisible(): branch on whether an optional banner exists.\n  const banner = page.getByRole('alert', { name: 'Cookie consent' });\n  if (await banner.isVisible()) {\n    await banner.getByRole('button', { name: 'Accept' }).click();\n  }\n\n  \u002F\u002F WRONG (do not do this): isVisible() does not wait, so this races a fade-in.\n  \u002F\u002F expect(await toast.isVisible()).toBe(true);\n});\n```\n\n### Pattern 5 — `waitFor({ state })` for appearance, detachment, and hiding\n\nUse `waitFor` when you need to block on a state transition without performing an action.\n\n```typescript\ntest('waits for explicit element states', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Fupload');\n\n  const spinner = page.getByRole('progressbar');\n\n  await page.getByRole('button', { name: 'Start upload' }).click();\n  await spinner.waitFor({ state: 'visible' });\n\n  \u002F\u002F Block until the spinner is gone before asserting success.\n  await spinner.waitFor({ state: 'hidden', timeout: 30_000 });\n  await expect(page.getByText('Upload complete')).toBeVisible();\n\n  \u002F\u002F 'attached' \u002F 'detached' for elements added\u002Fremoved from the DOM entirely.\n  const modal = page.getByRole('dialog');\n  await modal.waitFor({ state: 'detached' });\n});\n```\n\n### Pattern 6 — Iterate and assert over a filtered set\n\nCombine `filter` with `all()` \u002F `nth` \u002F `toHaveCount` for list assertions.\n\n```typescript\ntest('asserts across a filtered list', async ({ page }) => {\n  await page.goto('https:\u002F\u002Fexample.com\u002Finbox');\n\n  const unread = page.getByRole('listitem').filter({ has: page.getByTestId('unread-dot') });\n\n  \u002F\u002F Retrying count assertion — waits for the list to settle.\n  await expect(unread).toHaveCount(3);\n\n  \u002F\u002F Per-item assertions.\n  for (const item of await unread.all()) {\n    await expect(item.getByRole('heading')).toBeVisible();\n  }\n\n  \u002F\u002F Act on the first\u002Flast match of the filtered set.\n  await unread.first().click();\n  await expect(page.getByTestId('unread-dot')).toHaveCount(2);\n});\n```\n\n## Best Practices\n\n1. **Start every locator from `getByRole`\u002F`getByLabel`\u002F`getByText`**, then narrow with `.filter(...)`. Reserve CSS\u002FXPath for cases the accessibility tree can't express.\n2. **Use `.filter({ has })` \u002F `.filter({ hasNot })`** to select by descendant when text alone is ambiguous; chain filters for AND logic.\n3. **Assert visibility with `await expect(locator).toBeVisible()`** so it auto-waits; reserve `isVisible()` for `if` branches on optional UI.\n4. **Use `toHaveCount(n)`** for dynamic lists — it retries — instead of comparing `await locator.count()`.\n5. **Replace `waitForTimeout` with `locator.waitFor({ state })`** or simply acting on the locator (which auto-waits).\n6. **Pass `{ timeout }` to the specific assertion** that needs longer rather than inflating the global timeout.\n7. **Define a locator once as a `const`** and reuse it — it re-resolves on each use, so it stays valid across re-renders.\n\n## Anti-Patterns\n\n1. **`page.locator('.row:nth-child(3) .btn.btn-danger')`.** Index- and class-based; breaks on reorder or restyle. Filter by role + text instead.\n2. **`expect(await loc.isVisible()).toBe(true)`.** No waiting — races animations and async renders. Use `await expect(loc).toBeVisible()`.\n3. **`if ((await loc.count()) === 2) {...}`.** Snapshot count is a race on dynamic lists. Use `toHaveCount`.\n4. **`await page.waitForTimeout(2000)` before clicking.** Arbitrary and flaky. Locators auto-wait; or use `waitFor({ state })`.\n5. **Selecting from a list by raw `.nth(4)`** without filtering — order is data-dependent. Filter to the meaningful item first.\n6. **One mega-CSS selector** stringing together five descendant combinators instead of chaining scoped locators.\n7. **Raising the global `timeout`** to mask one slow screen, slowing every other test's failure feedback.\n\n## When to Trigger This Skill\n\n- \"My locator matches multiple elements \u002F 'strict mode violation'\"\n- \"How do I select the table row that contains this text?\"\n- \"Use `filter` \u002F `hasText` \u002F `has` to narrow a locator\"\n- \"Difference between `isVisible()` and `toBeVisible()`\"\n- \"Wait for a spinner to disappear before asserting\"\n- \"My selector is brittle \u002F breaks when the UI changes\"\n- \"Assert how many items are in a dynamic list\"\n- \"Replace `waitForTimeout` with a proper wait\"\n",{"name":5,"tags":24,"agents":33,"author":46,"domains":47,"license":15,"version":49,"languages":50,"frameworks":52,"description":7,"testingTypes":53},[25,26,27,28,29,30,31,32],"playwright","locator","filter","visibility","waitfor","hastext","resilient-locators","auto-wait",[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],"web","1.0.0",[51],"typescript",[25],[54,55],"e2e","integration","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fplaywright-locator-filter","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 \"Playwright Locator filter & Visibility\"",{"tool":70,"command":71},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Playwright Locator filter & Visibility\"",{"tool":73,"command":74},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Playwright Locator filter & Visibility\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fplaywright-locator-filter\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",[],[]]