skills.rest
sayalinvidia
sayalinvidiaCOMMUNITY
Explore all skills by this author →
GitHub

nemo-rl-brev-etiquette

Define NeMo-RL workspace layout, cache strategies, and secret handling on Brev instances.

Updated Apr 16, 2026
Search Tags:#workflow#security#environment#secrets#storage#brev#nemo-rl
One-click install
npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill nemo-rl-brev-etiquette
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nemo-rl-brev-etiquette
Source: https://github.com/sayalinvidia/sayali-skills-test/tree/main/skills/nemo-rl-brev-etiquette
Command: npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill nemo-rl-brev-etiquette

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guidance helps NeMo-RL users operate Brev instances safely by clarifying workspace layout, large-file handling, and secret management to prevent workspace bloat and accidental credential exposure.

Core Features & Use Cases

  • Workspace discipline: defines distinct roles for /home/ubuntu/RL and /ephemeral to keep useful data discoverable while avoiding large outputs in the source checkout.
  • Secret handling: treats /home/ubuntu/RL/.env as a local secret store and instructs when to load it for authenticated tasks.
  • Auto-research workflow guidance: recommends patterns for campaigns, artifacts, and log management on Brev.

Quick Start

Load nemo-rl-brev-etiquette to display runtime guidelines and apply the recommended Brev workspace and secret-handling conventions.

Frequently Asked Questions about nemo-rl-brev-etiquette

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

FAQPage Schema
How do I manage secrets and environment variables safely in a Brev workspace?▼

To manage secrets safely in a Brev workspace, use /home/ubuntu/RL/.env as a local secret store and load it only when authenticated tasks require credentials.

What is the recommended directory layout for NeMo-RL experiments on Brev?▼

The recommended layout separates roles by using /home/ubuntu/RL for source code and /ephemeral for large outputs, keeping useful data discoverable while preventing workspace bloat.

How do I prevent disk space issues during long-running NeMo-RL jobs?▼

Prevent disk space issues by directing large-file outputs and caches to /ephemeral storage, avoiding large artifacts in the source checkout, and applying specific cache strategies.

Can I use Brev instances for auto-research campaigns with NeMo-RL?▼

Yes, Brev instances support auto-research campaigns by providing workflow guidance for managing artifacts, logs, and reproducible executions across long-running experiments.

Does NeMo-RL on Brev require specific environment variables for reproducible executions?▼

Yes, reproducible executions require specifying required environment variables and applying workspace guardrails to ensure safe and consistent NeMo-RL workflow operations.

Why should I avoid storing large model outputs in the source checkout directory?▼

Storing large model outputs in the source checkout causes workspace bloat; using /ephemeral instead keeps useful data discoverable and maintains workspace discipline.

Related Skills

Explore More Software Engineering Skills→
NVIDIA-TAONVIDIA-TAO
83

tao-run-on-brev

Automate TAO training, evaluation, and inference jobs on Brev GPU instances via the Brev CLI.

Official
Advanced
rblake2320rblake2320

auto-research

Coordinate NeMo-RL experiment campaigns with git-backed research ledgers and TSV logs.

Community
Advanced
NVIDIA-NeMoNVIDIA-NeMo
58

nemo-files

Manage filesets and upload data within the NeMo platform using the nemo CLI.

Official
Basic
pluginagentmarketplacepluginagentmarketplace
1

deployments

Automate Kubernetes workload deployment and lifecycle management with rollout strategies.

Community
Advanced