NemoClaw Community Example Catalog
Examples are organized first by artifact type. Reusable recipes are organized
again by contributor provenance.
| Example |
Description |
| Developer Community Chief of Staff |
Synthesizes Slack, Outlook, GitHub, and mirrored community signals into operating briefs, gaps, priorities, and follow-up recommendations. |
| Kubernetes GPU Autoscaling |
Runs a CPU-only NemoClaw/OpenClaw sandbox through OpenShell on Kubernetes and autoscales authenticated, GPU-backed Ollama inference pods from DCGM utilization. |
| NV Tech Assistant |
Answers NVIDIA technical questions with cited evidence from allowlisted NVIDIA, GitHub, and arXiv sources. |
| Payment Operations Hermes Assistant |
Demonstrates constrained payment screening, evidence preparation, and a platform-enforced human release boundary. |
| PR Review Advisor |
Reviews exact pull request heads with a constrained Hermes workflow, produces attested artifacts, and publishes only through a separate maintainer action. |
| Contributor |
Example |
Description |
| BlueTier |
x402 Payment Gate |
Releases an agent's x402 payments through a maker/checker boundary: the sandboxed agent can only submit payment intents, and a host-side gate outside the sandbox re-screens each one with pre-signature GO/HOLD/STOP verdicts (counterparty reputation, price anomaly, OFAC sanctions) before anything is signed or settled. |
| HPE |
Retail Assistant |
Provides role-aware retail operations through Telegram, FastAPI, PostgreSQL, Docker Compose, and Helm. |
| Tavily |
Watchtower |
Runs scheduled, cited web monitoring with persistent deduplication and auditable outputs. |
Future independent contributions without formal organizational provenance
belong under recipes/community/.
| Environment |
Example |
Description |
| Brev |
Hermes |
Provides a notebook path from a fresh Brev CPU instance to a NemoClaw-managed Hermes sandbox. |
| Example |
Description |
| Harness Engineering Playground |
Provides an experimental CLI for eval-driven harness profile optimization. It is not an OpenShell blueprint. |
Read CONTRIBUTING.md and the canonical
example taxonomy and naming policy.
Examples must remain independently deployable and must document their
prerequisites, credentials, policies, startup behavior, verification, and
teardown behavior.