[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D8F6M8PRMJBZ9MS3169GSV":3,"skill-same:01M7D8F6M8PRMJBZ9MS3169GSV":73},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M7D8F6M8PRMJBZ9MS3169GSV","DNS Testing Patterns",null,"DNS configuration testing including record validation, DNSSEC verification, resolution timing, failover testing, and DNS-based service discovery.","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\u002Fdns-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"DNS Testing Patterns\"\ndescription: \"DNS configuration testing including record validation, DNSSEC verification, resolution timing, failover testing, and DNS-based service discovery.\"\nversion: 1.0.0\nauthor: qaskills\nlicense: MIT\ntags: [dns, dnssec, resolution, failover, service-discovery]\ntestingTypes: [integration]\nframeworks: []\nlanguages: [python, go]\ndomains: [infrastructure]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt]\n---\n\n# DNS Testing Patterns\n\nYou are an expert QA engineer specializing in dns testing patterns. When the user asks you to write, review, debug, or set up dns related tests or configurations, follow these detailed instructions.\n\n## Core Principles\n\n1. **Quality First** — Ensure all dns implementations follow industry best practices and produce reliable, maintainable results.\n2. **Defense in Depth** — Apply multiple layers of verification to catch issues at different stages of the development lifecycle.\n3. **Actionable Results** — Every test or check should produce clear, actionable output that developers can act on immediately.\n4. **Automation** — Prefer automated approaches that integrate seamlessly into CI\u002FCD pipelines for continuous verification.\n5. **Documentation** — Ensure all dns configurations and test patterns are well-documented for team understanding.\n\n## When to Use This Skill\n\n- When setting up dns for a new or existing project\n- When reviewing or improving existing dns implementations\n- When debugging failures related to dns\n- When integrating dns into CI\u002FCD pipelines\n- When training team members on dns best practices\n\n## Implementation Guide\n\n### Setup & Configuration\n\nWhen setting up dns, follow these steps:\n\n1. **Assess the project** — Understand the tech stack (python, go) and existing test infrastructure\n2. **Choose the right tools** — Select appropriate dns tools based on project requirements\n3. **Configure the environment** — Set up necessary configuration files and dependencies\n4. **Write initial tests** — Start with critical paths and expand coverage gradually\n5. **Integrate with CI\u002FCD** — Ensure tests run automatically on every code change\n\n### Best Practices\n\n- **Keep tests focused** — Each test should verify one specific behavior or requirement\n- **Use descriptive names** — Test names should clearly describe what is being verified\n- **Maintain test independence** — Tests should not depend on execution order or shared state\n- **Handle async operations** — Properly await async operations and use appropriate timeouts\n- **Clean up resources** — Ensure test resources are properly cleaned up after execution\n\n### Common Patterns\n\n```python\n\u002F\u002F Example dns pattern\n\u002F\u002F Adapt this pattern to your specific use case and framework\n```\n\n### Anti-Patterns to Avoid\n\n1. **Flaky tests** — Tests that pass\u002Ffail intermittently due to timing or environmental issues\n2. **Over-mocking** — Mocking too many dependencies, leading to tests that don't reflect real behavior\n3. **Test coupling** — Tests that depend on each other or share mutable state\n4. **Ignoring failures** — Disabling or skipping failing tests instead of fixing them\n5. **Missing edge cases** — Only testing happy paths without considering error scenarios\n\n## Integration with CI\u002FCD\n\nIntegrate dns into your CI\u002FCD pipeline:\n\n1. Run tests on every pull request\n2. Set up quality gates with minimum thresholds\n3. Generate and publish test reports\n4. Configure notifications for failures\n5. Track trends over time\n\n## Troubleshooting\n\nWhen dns issues arise:\n\n1. Check the test output for specific error messages\n2. Verify environment and configuration settings\n3. Ensure all dependencies are up to date\n4. Review recent code changes that may have introduced issues\n5. Consult the framework documentation for known issues\n","# DNS Testing Patterns\n\nYou are an expert QA engineer specializing in dns testing patterns. When the user asks you to write, review, debug, or set up dns related tests or configurations, follow these detailed instructions.\n\n## Core Principles\n\n1. **Quality First** — Ensure all dns implementations follow industry best practices and produce reliable, maintainable results.\n2. **Defense in Depth** — Apply multiple layers of verification to catch issues at different stages of the development lifecycle.\n3. **Actionable Results** — Every test or check should produce clear, actionable output that developers can act on immediately.\n4. **Automation** — Prefer automated approaches that integrate seamlessly into CI\u002FCD pipelines for continuous verification.\n5. **Documentation** — Ensure all dns configurations and test patterns are well-documented for team understanding.\n\n## When to Use This Skill\n\n- When setting up dns for a new or existing project\n- When reviewing or improving existing dns implementations\n- When debugging failures related to dns\n- When integrating dns into CI\u002FCD pipelines\n- When training team members on dns best practices\n\n## Implementation Guide\n\n### Setup & Configuration\n\nWhen setting up dns, follow these steps:\n\n1. **Assess the project** — Understand the tech stack (python, go) and existing test infrastructure\n2. **Choose the right tools** — Select appropriate dns tools based on project requirements\n3. **Configure the environment** — Set up necessary configuration files and dependencies\n4. **Write initial tests** — Start with critical paths and expand coverage gradually\n5. **Integrate with CI\u002FCD** — Ensure tests run automatically on every code change\n\n### Best Practices\n\n- **Keep tests focused** — Each test should verify one specific behavior or requirement\n- **Use descriptive names** — Test names should clearly describe what is being verified\n- **Maintain test independence** — Tests should not depend on execution order or shared state\n- **Handle async operations** — Properly await async operations and use appropriate timeouts\n- **Clean up resources** — Ensure test resources are properly cleaned up after execution\n\n### Common Patterns\n\n```python\n\u002F\u002F Example dns pattern\n\u002F\u002F Adapt this pattern to your specific use case and framework\n```\n\n### Anti-Patterns to Avoid\n\n1. **Flaky tests** — Tests that pass\u002Ffail intermittently due to timing or environmental issues\n2. **Over-mocking** — Mocking too many dependencies, leading to tests that don't reflect real behavior\n3. **Test coupling** — Tests that depend on each other or share mutable state\n4. **Ignoring failures** — Disabling or skipping failing tests instead of fixing them\n5. **Missing edge cases** — Only testing happy paths without considering error scenarios\n\n## Integration with CI\u002FCD\n\nIntegrate dns into your CI\u002FCD pipeline:\n\n1. Run tests on every pull request\n2. Set up quality gates with minimum thresholds\n3. Generate and publish test reports\n4. Configure notifications for failures\n5. Track trends over time\n\n## Troubleshooting\n\nWhen dns issues arise:\n\n1. Check the test output for specific error messages\n2. Verify environment and configuration settings\n3. Ensure all dependencies are up to date\n4. Review recent code changes that may have introduced issues\n5. Consult the framework documentation for known issues\n",{"name":5,"tags":24,"agents":30,"author":41,"domains":42,"license":15,"version":44,"languages":45,"frameworks":48,"description":7,"testingTypes":49},[25,26,27,28,29],"dns","dnssec","resolution","failover","service-discovery",[31,32,33,34,35,36,37,38,39,40],"claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","qaskills",[43],"infrastructure","1.0.0",[46,47],"python","go",[],[50],"integration","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fdns-testing","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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"DNS Testing Patterns\"",{"tool":65,"command":66},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"DNS Testing Patterns\"",{"tool":68,"command":69},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"DNS Testing Patterns\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fdns-testing\u002FSKILL.md",true,[],[74,82,89,96,103,110],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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",[],[]]