[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D8S74VBPNEM0R8PBH3GQ0H":3,"skill-same:01M7D8S74VBPNEM0R8PBH3GQ0H":84},{"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":62,"commitSha":63,"skillDirectory":64,"forksCount":14,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M7D8S74VBPNEM0R8PBH3GQ0H","Kafka Event-Driven Testing",null,"Test Kafka-based event-driven systems, producer and consumer integration tests with Testcontainers, schema compatibility gates, idempotency and ordering verification, dead-letter handling, and end-to-end event flow assertions.","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\u002Fkafka-event-driven-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Kafka Event-Driven Testing\ndescription: Test Kafka-based event-driven systems, producer and consumer integration tests with Testcontainers, schema compatibility gates, idempotency and ordering verification, dead-letter handling, and end-to-end event flow assertions.\nversion: 1.0.0\nauthor: thetestingacademy\nlicense: MIT\ntags: [kafka, event-driven, testcontainers, schema-registry, idempotency, ordering, dead-letter-queue, integration-testing, consumers]\ntestingTypes: [integration, contract, regression]\nframeworks: [kafka, testcontainers]\nlanguages: [java, python, typescript]\ndomains: [backend, api, infrastructure]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt, gemini-cli, amp]\n---\n\n# Kafka Event-Driven Testing Skill\n\nYou are an expert backend QA engineer specializing in event-driven systems on Kafka. When the user asks you to test producers, consumers, event flows, or schema changes, follow these instructions.\n\n## Core Principles\n\n1. **Test against real Kafka, not mocks of the client.** Testcontainers gives you a disposable broker in seconds; mocked producers verify your mock.\n2. **At-least-once is the contract.** Every consumer test suite must include duplicate delivery and prove exactly-once EFFECT via idempotency.\n3. **Ordering is per-partition only.** Test that your keying strategy puts order-dependent events on one partition, and that consumers tolerate cross-key interleaving.\n4. **Schemas are the API.** Compatibility checks in CI are the contract tests of event systems.\n5. **Failure paths are the product.** Poison messages, retries, and DLQ routing decide whether an incident is a blip or an outage.\n\n## Test Infrastructure (Testcontainers)\n\n```java\n\u002F\u002F JUnit 5 + Testcontainers (same pattern exists for Python and Node)\n@Testcontainers\nclass OrderEventsIT {\n  @Container\n  static KafkaContainer kafka = new KafkaContainer(\n      DockerImageName.parse(\"confluentinc\u002Fcp-kafka:7.6.0\"));\n\n  KafkaProducer\u003CString, String> producer;\n  KafkaConsumer\u003CString, String> consumer;\n\n  @BeforeEach\n  void setup() {\n    producer = new KafkaProducer\u003C>(Map.of(\n        BOOTSTRAP_SERVERS_CONFIG, kafka.getBootstrapServers(),\n        KEY_SERIALIZER_CLASS_CONFIG, StringSerializer.class,\n        VALUE_SERIALIZER_CLASS_CONFIG, StringSerializer.class,\n        ACKS_CONFIG, \"all\"));                      \u002F\u002F test with prod-like acks\n  }\n}\n```\n\nRules: unique topic per test (or per class) to kill cross-test pollution; prod-like configs for acks, retries, and auto.offset.reset; never assert with sleep(), poll with a deadline:\n\n```java\nstatic List\u003CConsumerRecord\u003CString, String>> pollUntil(\n    KafkaConsumer\u003CString, String> c, int expected, Duration timeout) {\n  var out = new ArrayList\u003CConsumerRecord\u003CString, String>>();\n  long deadline = System.nanoTime() + timeout.toNanos();\n  while (out.size() \u003C expected && System.nanoTime() \u003C deadline) {\n    c.poll(Duration.ofMillis(200)).forEach(out::add);\n  }\n  return out;   \u002F\u002F assert size AFTER, with a useful message\n}\n```\n\n## The Five Consumer Tests Every Topic Needs\n\n```text\n1. HAPPY PATH: publish OrderPlaced -> consumer creates the order projection\n2. DUPLICATE: publish the SAME event (same event_id) twice\n   -> projection updated once, side effect (email, charge) fired once\n3. OUT OF ORDER: publish OrderUpdated(v2) then OrderCreated(v1) for one key\n   -> final state reflects v2; no crash, no v1 overwrite\n4. POISON MESSAGE: publish malformed payload\n   -> consumer does NOT crash-loop; message lands in DLQ with error headers;\n      offset advances; subsequent good messages still processed\n5. REPLAY: reset consumer group to earliest, reprocess the whole topic\n   -> end state identical (proves idempotency at scale)\n```\n\nTest 4 is where most real systems fail review: a poison message that blocks the partition is an outage generator. Assert both the DLQ record (payload + error metadata headers) AND continued consumption.\n\n## Idempotency and Ordering Assertions\n\n```python\n# Python example: duplicate delivery proves exactly-once effect\nproducer.produce(\"orders\", key=\"order-42\", value=order_placed_v1)  # same event_id\nproducer.produce(\"orders\", key=\"order-42\", value=order_placed_v1)\nproducer.flush()\n\nwait_until(lambda: db.orders.exists(\"order-42\"), timeout=10)\nassert db.orders.count(id=\"order-42\") == 1\nassert email_spy.sent_count(\"order-42\") == 1        # side effect exactly once\n\n# keying strategy test: same aggregate -> same partition\nmd1 = producer.produce(\"orders\", key=\"order-42\", value=e1).get(10)\nmd2 = producer.produce(\"orders\", key=\"order-42\", value=e2).get(10)\nassert md1.partition() == md2.partition()\n```\n\n## Schema Compatibility Gate (CI)\n\nWith Schema Registry (Avro\u002FProtobuf\u002FJSON Schema), every schema change gets a CI check BEFORE merge:\n\n```bash\n# maven: io.confluent kafka-schema-registry-maven-plugin\nmvn schema-registry:test-compatibility\n# or REST, per subject:\ncurl -s -X POST \"$REGISTRY\u002Fcompatibility\u002Fsubjects\u002Forders-value\u002Fversions\u002Flatest\" \\\n  -H 'Content-Type: application\u002Fvnd.schemaregistry.v1+json' \\\n  -d @new-schema.json          # {\"is_compatible\": true} required\n```\n\nPolicy: BACKWARD compatibility minimum (new consumers read old events); adding required fields or renaming fields fails the gate by design. Pair with a consumer-side test that deserializes a FIXTURE of the oldest schema version still in the topic's retention window.\n\n## End-to-End Flow Tests (Choreography)\n\nFor sagas spanning services (OrderPlaced -> PaymentCaptured -> OrderShipped): spin the involved services against one Testcontainers broker (compose or test harness), publish the triggering event, assert the TERMINAL event and projections with a deadline poll, then inject the failure variant (payment service down) and assert compensation (OrderCancelled) rather than silence. Keep these to a handful of critical sagas; the five consumer tests carry the bulk load.\n\n## Common Mistakes\n\n- Mocking KafkaProducer\u002FConsumer classes; you test serialization and rebalancing behavior only against a real broker\n- sleep(5000) instead of deadline polling; slow AND flaky simultaneously\n- One shared topic across the suite; test pollution masquerading as ordering bugs\n- Testing only schema WRITE compatibility while old events still live in retention\n- No DLQ assertions; teams discover their DLQ topic name during the first incident\n- Ignoring consumer group rebalancing: at least one test kills and restarts a consumer mid-stream and asserts no loss, no double-effect\n\n## Checklist\n\n- [ ] Testcontainers broker per suite; unique topics per test; prod-like producer configs\n- [ ] Five consumer tests (happy, duplicate, out-of-order, poison->DLQ, replay) per topic\n- [ ] Keying strategy asserted for order-dependent aggregates\n- [ ] Schema compatibility gate in CI + oldest-retained-version deserialization fixture\n- [ ] Critical sagas covered end-to-end incl. compensation path; rebalance test present\n","# Kafka Event-Driven Testing Skill\n\nYou are an expert backend QA engineer specializing in event-driven systems on Kafka. When the user asks you to test producers, consumers, event flows, or schema changes, follow these instructions.\n\n## Core Principles\n\n1. **Test against real Kafka, not mocks of the client.** Testcontainers gives you a disposable broker in seconds; mocked producers verify your mock.\n2. **At-least-once is the contract.** Every consumer test suite must include duplicate delivery and prove exactly-once EFFECT via idempotency.\n3. **Ordering is per-partition only.** Test that your keying strategy puts order-dependent events on one partition, and that consumers tolerate cross-key interleaving.\n4. **Schemas are the API.** Compatibility checks in CI are the contract tests of event systems.\n5. **Failure paths are the product.** Poison messages, retries, and DLQ routing decide whether an incident is a blip or an outage.\n\n## Test Infrastructure (Testcontainers)\n\n```java\n\u002F\u002F JUnit 5 + Testcontainers (same pattern exists for Python and Node)\n@Testcontainers\nclass OrderEventsIT {\n  @Container\n  static KafkaContainer kafka = new KafkaContainer(\n      DockerImageName.parse(\"confluentinc\u002Fcp-kafka:7.6.0\"));\n\n  KafkaProducer\u003CString, String> producer;\n  KafkaConsumer\u003CString, String> consumer;\n\n  @BeforeEach\n  void setup() {\n    producer = new KafkaProducer\u003C>(Map.of(\n        BOOTSTRAP_SERVERS_CONFIG, kafka.getBootstrapServers(),\n        KEY_SERIALIZER_CLASS_CONFIG, StringSerializer.class,\n        VALUE_SERIALIZER_CLASS_CONFIG, StringSerializer.class,\n        ACKS_CONFIG, \"all\"));                      \u002F\u002F test with prod-like acks\n  }\n}\n```\n\nRules: unique topic per test (or per class) to kill cross-test pollution; prod-like configs for acks, retries, and auto.offset.reset; never assert with sleep(), poll with a deadline:\n\n```java\nstatic List\u003CConsumerRecord\u003CString, String>> pollUntil(\n    KafkaConsumer\u003CString, String> c, int expected, Duration timeout) {\n  var out = new ArrayList\u003CConsumerRecord\u003CString, String>>();\n  long deadline = System.nanoTime() + timeout.toNanos();\n  while (out.size() \u003C expected && System.nanoTime() \u003C deadline) {\n    c.poll(Duration.ofMillis(200)).forEach(out::add);\n  }\n  return out;   \u002F\u002F assert size AFTER, with a useful message\n}\n```\n\n## The Five Consumer Tests Every Topic Needs\n\n```text\n1. HAPPY PATH: publish OrderPlaced -> consumer creates the order projection\n2. DUPLICATE: publish the SAME event (same event_id) twice\n   -> projection updated once, side effect (email, charge) fired once\n3. OUT OF ORDER: publish OrderUpdated(v2) then OrderCreated(v1) for one key\n   -> final state reflects v2; no crash, no v1 overwrite\n4. POISON MESSAGE: publish malformed payload\n   -> consumer does NOT crash-loop; message lands in DLQ with error headers;\n      offset advances; subsequent good messages still processed\n5. REPLAY: reset consumer group to earliest, reprocess the whole topic\n   -> end state identical (proves idempotency at scale)\n```\n\nTest 4 is where most real systems fail review: a poison message that blocks the partition is an outage generator. Assert both the DLQ record (payload + error metadata headers) AND continued consumption.\n\n## Idempotency and Ordering Assertions\n\n```python\n# Python example: duplicate delivery proves exactly-once effect\nproducer.produce(\"orders\", key=\"order-42\", value=order_placed_v1)  # same event_id\nproducer.produce(\"orders\", key=\"order-42\", value=order_placed_v1)\nproducer.flush()\n\nwait_until(lambda: db.orders.exists(\"order-42\"), timeout=10)\nassert db.orders.count(id=\"order-42\") == 1\nassert email_spy.sent_count(\"order-42\") == 1        # side effect exactly once\n\n# keying strategy test: same aggregate -> same partition\nmd1 = producer.produce(\"orders\", key=\"order-42\", value=e1).get(10)\nmd2 = producer.produce(\"orders\", key=\"order-42\", value=e2).get(10)\nassert md1.partition() == md2.partition()\n```\n\n## Schema Compatibility Gate (CI)\n\nWith Schema Registry (Avro\u002FProtobuf\u002FJSON Schema), every schema change gets a CI check BEFORE merge:\n\n```bash\n# maven: io.confluent kafka-schema-registry-maven-plugin\nmvn schema-registry:test-compatibility\n# or REST, per subject:\ncurl -s -X POST \"$REGISTRY\u002Fcompatibility\u002Fsubjects\u002Forders-value\u002Fversions\u002Flatest\" \\\n  -H 'Content-Type: application\u002Fvnd.schemaregistry.v1+json' \\\n  -d @new-schema.json          # {\"is_compatible\": true} required\n```\n\nPolicy: BACKWARD compatibility minimum (new consumers read old events); adding required fields or renaming fields fails the gate by design. Pair with a consumer-side test that deserializes a FIXTURE of the oldest schema version still in the topic's retention window.\n\n## End-to-End Flow Tests (Choreography)\n\nFor sagas spanning services (OrderPlaced -> PaymentCaptured -> OrderShipped): spin the involved services against one Testcontainers broker (compose or test harness), publish the triggering event, assert the TERMINAL event and projections with a deadline poll, then inject the failure variant (payment service down) and assert compensation (OrderCancelled) rather than silence. Keep these to a handful of critical sagas; the five consumer tests carry the bulk load.\n\n## Common Mistakes\n\n- Mocking KafkaProducer\u002FConsumer classes; you test serialization and rebalancing behavior only against a real broker\n- sleep(5000) instead of deadline polling; slow AND flaky simultaneously\n- One shared topic across the suite; test pollution masquerading as ordering bugs\n- Testing only schema WRITE compatibility while old events still live in retention\n- No DLQ assertions; teams discover their DLQ topic name during the first incident\n- Ignoring consumer group rebalancing: at least one test kills and restarts a consumer mid-stream and asserts no loss, no double-effect\n\n## Checklist\n\n- [ ] Testcontainers broker per suite; unique topics per test; prod-like producer configs\n- [ ] Five consumer tests (happy, duplicate, out-of-order, poison->DLQ, replay) per topic\n- [ ] Keying strategy asserted for order-dependent aggregates\n- [ ] Schema compatibility gate in CI + oldest-retained-version deserialization fixture\n- [ ] Critical sagas covered end-to-end incl. compensation path; rebalance test present\n",{"name":5,"tags":24,"agents":34,"author":47,"domains":48,"license":15,"version":52,"languages":53,"frameworks":57,"description":7,"testingTypes":58},[25,26,27,28,29,30,31,32,33],"kafka","event-driven","testcontainers","schema-registry","idempotency","ordering","dead-letter-queue","integration-testing","consumers",[35,36,37,38,39,40,41,42,43,44,45,46],"claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp","thetestingacademy",[49,50,51],"backend","api","infrastructure","1.0.0",[54,55,56],"java","python","typescript",[25,27],[59,60,61],"integration","contract","regression","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fkafka-event-driven-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":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Kafka Event-Driven Testing\"",{"tool":76,"command":77},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Kafka Event-Driven Testing\"",{"tool":79,"command":80},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Kafka Event-Driven Testing\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fkafka-event-driven-testing\u002FSKILL.md",true,[],[85,93,100,107,114,121],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"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",[],[]]