nemoclaw-user-manage-policy

Add, remove, and adjust NemoClaw sandbox network endpoints via OpenShell policy commands.

Updated May 29, 2026
One-click install
npx skills add https://github.com/rblake2320/vigil --skill nemoclaw-user-manage-policy-rblake2320
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-user-manage-policy
Source: https://github.com/rblake2320/vigil/tree/main/.claude/skills/nemoclaw-user-manage-policy
Command: npx skills add https://github.com/rblake2320/vigil --skill nemoclaw-user-manage-policy-rblake2320

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Operators need a reliable way to customize and enforce sandbox network policy for NemoClaw/OpenShell, ensuring least-privilege access while enabling necessary integrations.

Core Features & Use Cases

  • Manage allowed endpoints by adding, removing, or modifying network policies for NemoClaw sandboxes.
  • Apply static or dynamic changes using onboard/policy-add and policy-list/policy-remove workflows; reflect changes in the sandbox registry for auditability.
  • Validate and test policy changes using OpenShell TUI or policy-list outputs to ensure intended integrations work without broad exposure.

Quick Start

Onboard a NemoClaw sandbox and apply a policy preset with policy-add, then verify the active presets with policy-list.

Frequently Asked Questions about nemoclaw-user-manage-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure sandbox network access for NemoClaw?

Configure NemoClaw sandbox network access by adding or removing endpoints via OpenShell policy-add and policy-remove commands. This modifies live sandbox policies or creates persistent presets to enforce least-privilege egress for your integrations.

What is the best way to restrict egress traffic in an OpenShell sandbox?

Restrict egress traffic in an OpenShell sandbox by applying least-privilege network policies. Use policy-list to verify active presets and ensure only specified third-party services are allowed without broad network exposure.

Can I use NemoClaw policy commands to onboard new third-party integrations?

Yes, you can onboard new third-party integrations by adding specific endpoints to the sandbox policy. Use policy-add workflows to enable necessary services and validate changes using OpenShell TUI outputs before deploying across environments.

How do I test sandbox policy changes before applying them to production?

Test sandbox policy changes by validating them with OpenShell TUI or policy-list outputs. This ensures intended integrations function correctly and maintain least-privilege access before applying presets across development, staging, or production sandboxes.

How do I remove an allowed endpoint from a NemoClaw network policy?

Remove an allowed endpoint from a NemoClaw network policy by using the policy-remove workflow. Reflecting these changes in the sandbox registry ensures your egress rules remain auditable and strictly enforced.

Do I need OpenShell tooling to manage NemoClaw sandbox egress rules?

Yes, OpenShell policy tooling is required to manage NemoClaw sandbox egress rules. It provides the necessary policy-add, policy-list, and policy-remove commands to modify live policies and create persistent presets.