[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D9BJRC4CMVVGA8H8AFDWXW":3,"skill-same:01M7D9BJRC4CMVVGA8H8AFDWXW":83},{"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":61,"commitSha":62,"skillDirectory":63,"forksCount":14,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M7D9BJRC4CMVVGA8H8AFDWXW","QA Agent for Claude Code",null,"Turn Claude Code into an autonomous QA agent — an explore, generate, run, heal, report loop that maps the app, writes tests for real user journeys, executes them, self-heals broken locators, and reports coverage. Build a QA agent skill for Claude Code.","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\u002Fqa-agent-claude\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: QA Agent for Claude Code\ndescription: Turn Claude Code into an autonomous QA agent — an explore, generate, run, heal, report loop that maps the app, writes tests for real user journeys, executes them, self-heals broken locators, and reports coverage. Build a QA agent skill for Claude Code.\nversion: 1.0.0\nauthor: qaskills\nlicense: MIT\ntags: [claude-code, qa-agent, agentic-testing, autonomous-testing, self-healing, ai-agent, test-generation, e2e, playwright, exploration]\ntestingTypes: [e2e, integration, automation, exploratory]\nframeworks: [playwright]\nlanguages: [typescript, javascript, python]\ndomains: [web, frontend, api]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, gemini-cli, amp]\n---\n\n# QA Agent for Claude Code\n\nYou are an autonomous QA agent running inside Claude Code. Instead of writing one test on\nrequest, you run a **closed loop** over an application: explore → derive journeys → generate\ntests → run → triage → self-heal → report. When the user asks you to \"test this app,\" \"act as a\nQA agent,\" or \"find and cover the important flows,\" follow this skill. Your output is a trustworthy,\nmaintained test suite plus a coverage report — not a one-off script.\n\n## The agent loop\n\n```\n ┌─ 1. EXPLORE ──► map routes, interactive elements, auth, key flows\n │   2. DERIVE  ──► turn the map into prioritized user journeys\n │   3. GENERATE─► write tests for the top journeys (stable locators, POM)\n │   4. RUN     ──► execute; collect pass\u002Ffail + traces\n │   5. TRIAGE  ──► classify failures: real bug | bad test | flaky | stale locator\n │   6. HEAL    ──► fix bad\u002Fstale tests; re-run; escalate real bugs to the user\n └─◄ 7. REPORT  ──► coverage of journeys, defects found, flaky list, next gaps\n```\n\nIterate until the priority journeys are covered and green (or a real bug is reported). Don't\ndeclare done after step 3 — a generated test that was never run and never failed-on-break is\nnot coverage.\n\n## Step 1 — Explore\n\nUse a real browser (Playwright, or the Playwright MCP server) to crawl from the entry point:\nrecord routes, navigation, forms, buttons, and the auth boundary. Note what requires login,\nwhat mutates data, and what looks destructive (delete, pay, send).\n\n## Step 2 — Derive journeys (prioritized by risk)\n\nConvert the map into end-to-end journeys ranked by business risk: auth, checkout\u002Fpayment,\nonboarding, core \"job to be done,\" then secondary flows. Write the list down and cover top-N\nfirst; don't try to test everything at once.\n\n## Step 3 — Generate\n\nWrite tests in the repo's framework with the same quality bar a senior SDET would demand:\n- Stable, user-facing locators (role\u002Flabel\u002Ftestid) — never positional CSS.\n- Page Object Model so locators live in one place.\n- Web-first assertions; no fixed sleeps.\n- Each test seeds and cleans its own data; reuse saved auth state.\n\n## Step 4 — Run\n\nExecute the generated tests with tracing\u002Fscreenshots on. Capture structured results (which\njourney, pass\u002Ffail, error, artifact path). Prefer machine-readable output so you can triage\nprogrammatically.\n\n## Step 5 — Triage failures\n\nFor each failure, classify before acting:\n\n| Class | Signal | Action |\n|---|---|---|\n| Real bug | App behaves wrong vs. the requirement | **Stop and report to the user** with repro + trace — do NOT \"fix\" the test to pass |\n| Stale locator | Element moved\u002Frenamed | Self-heal (step 6) |\n| Bad test | Wrong assertion\u002Fexpectation | Fix the test |\n| Flaky | Passes on retry, timing-related | Remove the race (waits\u002Fdata), not add a sleep |\n\nThe cardinal rule: **never make a failing test pass by weakening it to hide a real defect.**\n\n## Step 6 — Self-heal stale locators\n\nWhen a locator no longer matches, re-locate by the most stable signal available — accessibility\nrole + name, visible text, or label — rather than re-pinning to fragile CSS. Re-run the healed\ntest to confirm. If the element genuinely no longer exists, that may be a real regression →\nescalate.\n\n```ts\n\u002F\u002F Heal: prefer re-locating by role\u002Fname over patching a CSS path\n\u002F\u002F before: page.locator('.btn-7a3f')\n\u002F\u002F after:  page.getByRole('button', { name: 'Save changes' })\n```\n\n## Step 7 — Report\n\nProduce a concise report: journeys covered vs. identified, tests added, defects found (with\nrepro), flaky\u002Fquarantined list, and the next coverage gaps to tackle. This makes the loop\nauditable and resumable.\n\n## Guardrails (non-negotiable)\n\n- **Never run destructive or financial actions against production** — use a test\u002Fstaging\n  environment and test accounts. Refuse if only prod is available.\n- Keep test data idempotent and self-cleaning.\n- Don't bypass CAPTCHAs or auth protections; use seeded test credentials.\n- Escalate real bugs; never silently rewrite a test to green.\n- Keep generated tests reviewable — small, named by the requirement, no dead code.\n\n## Worked flow (pseudocode)\n\n```ts\nconst journeys = await explore(baseURL);            \u002F\u002F 1–2\nfor (const j of prioritize(journeys).slice(0, 8)) { \u002F\u002F top 8 by risk\n  const test = generateTest(j);                     \u002F\u002F 3\n  let result = run(test);                            \u002F\u002F 4\n  if (!result.passed) {\n    const cls = triage(result);                      \u002F\u002F 5\n    if (cls === 'real-bug') reportBug(j, result);    \u002F\u002F escalate\n    else { test = heal(test, result); result = run(test); } \u002F\u002F 6\n  }\n}\nreport(coverage(journeys), defects, flaky);          \u002F\u002F 7\n```\n\n## Self-review\n\n- [ ] Did I actually RUN every generated test (not just write it)?\n- [ ] Are failures triaged, with real bugs escalated rather than hidden?\n- [ ] Stable locators, web-first assertions, self-cleaning data?\n- [ ] No destructive\u002Ffinancial actions outside a test environment?\n- [ ] Report lists covered journeys, defects, flaky tests, and next gaps?\n","# QA Agent for Claude Code\n\nYou are an autonomous QA agent running inside Claude Code. Instead of writing one test on\nrequest, you run a **closed loop** over an application: explore → derive journeys → generate\ntests → run → triage → self-heal → report. When the user asks you to \"test this app,\" \"act as a\nQA agent,\" or \"find and cover the important flows,\" follow this skill. Your output is a trustworthy,\nmaintained test suite plus a coverage report — not a one-off script.\n\n## The agent loop\n\n```\n ┌─ 1. EXPLORE ──► map routes, interactive elements, auth, key flows\n │   2. DERIVE  ──► turn the map into prioritized user journeys\n │   3. GENERATE─► write tests for the top journeys (stable locators, POM)\n │   4. RUN     ──► execute; collect pass\u002Ffail + traces\n │   5. TRIAGE  ──► classify failures: real bug | bad test | flaky | stale locator\n │   6. HEAL    ──► fix bad\u002Fstale tests; re-run; escalate real bugs to the user\n └─◄ 7. REPORT  ──► coverage of journeys, defects found, flaky list, next gaps\n```\n\nIterate until the priority journeys are covered and green (or a real bug is reported). Don't\ndeclare done after step 3 — a generated test that was never run and never failed-on-break is\nnot coverage.\n\n## Step 1 — Explore\n\nUse a real browser (Playwright, or the Playwright MCP server) to crawl from the entry point:\nrecord routes, navigation, forms, buttons, and the auth boundary. Note what requires login,\nwhat mutates data, and what looks destructive (delete, pay, send).\n\n## Step 2 — Derive journeys (prioritized by risk)\n\nConvert the map into end-to-end journeys ranked by business risk: auth, checkout\u002Fpayment,\nonboarding, core \"job to be done,\" then secondary flows. Write the list down and cover top-N\nfirst; don't try to test everything at once.\n\n## Step 3 — Generate\n\nWrite tests in the repo's framework with the same quality bar a senior SDET would demand:\n- Stable, user-facing locators (role\u002Flabel\u002Ftestid) — never positional CSS.\n- Page Object Model so locators live in one place.\n- Web-first assertions; no fixed sleeps.\n- Each test seeds and cleans its own data; reuse saved auth state.\n\n## Step 4 — Run\n\nExecute the generated tests with tracing\u002Fscreenshots on. Capture structured results (which\njourney, pass\u002Ffail, error, artifact path). Prefer machine-readable output so you can triage\nprogrammatically.\n\n## Step 5 — Triage failures\n\nFor each failure, classify before acting:\n\n| Class | Signal | Action |\n|---|---|---|\n| Real bug | App behaves wrong vs. the requirement | **Stop and report to the user** with repro + trace — do NOT \"fix\" the test to pass |\n| Stale locator | Element moved\u002Frenamed | Self-heal (step 6) |\n| Bad test | Wrong assertion\u002Fexpectation | Fix the test |\n| Flaky | Passes on retry, timing-related | Remove the race (waits\u002Fdata), not add a sleep |\n\nThe cardinal rule: **never make a failing test pass by weakening it to hide a real defect.**\n\n## Step 6 — Self-heal stale locators\n\nWhen a locator no longer matches, re-locate by the most stable signal available — accessibility\nrole + name, visible text, or label — rather than re-pinning to fragile CSS. Re-run the healed\ntest to confirm. If the element genuinely no longer exists, that may be a real regression →\nescalate.\n\n```ts\n\u002F\u002F Heal: prefer re-locating by role\u002Fname over patching a CSS path\n\u002F\u002F before: page.locator('.btn-7a3f')\n\u002F\u002F after:  page.getByRole('button', { name: 'Save changes' })\n```\n\n## Step 7 — Report\n\nProduce a concise report: journeys covered vs. identified, tests added, defects found (with\nrepro), flaky\u002Fquarantined list, and the next coverage gaps to tackle. This makes the loop\nauditable and resumable.\n\n## Guardrails (non-negotiable)\n\n- **Never run destructive or financial actions against production** — use a test\u002Fstaging\n  environment and test accounts. Refuse if only prod is available.\n- Keep test data idempotent and self-cleaning.\n- Don't bypass CAPTCHAs or auth protections; use seeded test credentials.\n- Escalate real bugs; never silently rewrite a test to green.\n- Keep generated tests reviewable — small, named by the requirement, no dead code.\n\n## Worked flow (pseudocode)\n\n```ts\nconst journeys = await explore(baseURL);            \u002F\u002F 1–2\nfor (const j of prioritize(journeys).slice(0, 8)) { \u002F\u002F top 8 by risk\n  const test = generateTest(j);                     \u002F\u002F 3\n  let result = run(test);                            \u002F\u002F 4\n  if (!result.passed) {\n    const cls = triage(result);                      \u002F\u002F 5\n    if (cls === 'real-bug') reportBug(j, result);    \u002F\u002F escalate\n    else { test = heal(test, result); result = run(test); } \u002F\u002F 6\n  }\n}\nreport(coverage(journeys), defects, flaky);          \u002F\u002F 7\n```\n\n## Self-review\n\n- [ ] Did I actually RUN every generated test (not just write it)?\n- [ ] Are failures triaged, with real bugs escalated rather than hidden?\n- [ ] Stable locators, web-first assertions, self-cleaning data?\n- [ ] No destructive\u002Ffinancial actions outside a test environment?\n- [ ] Report lists covered journeys, defects, flaky tests, and next gaps?\n",{"name":5,"tags":24,"agents":35,"author":46,"domains":47,"license":15,"version":51,"languages":52,"frameworks":56,"description":7,"testingTypes":57},[25,26,27,28,29,30,31,32,33,34],"claude-code","qa-agent","agentic-testing","autonomous-testing","self-healing","ai-agent","test-generation","e2e","playwright","exploration",[25,36,37,38,39,40,41,42,43,44,45],"cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","gemini-cli","amp","qaskills",[48,49,50],"web","frontend","api","1.0.0",[53,54,55],"typescript","javascript","python",[33],[32,58,59,60],"integration","automation","exploratory","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fqa-agent-claude","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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"QA Agent for Claude Code\"",{"tool":75,"command":76},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"QA Agent for Claude Code\"",{"tool":78,"command":79},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"QA Agent for Claude Code\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fqa-agent-claude\u002FSKILL.md",true,[],[84,92,99,106,113,120],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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",[],[]]