Skip to content
nemo-rl-brev-etiquette logo

Brev Etiquette

nemo-rl-brev-etiquette

Brev instance operating guidance for NeMo-RL agents working in /home/ubuntu/RL with limited workspace disk, a larger /ephemeral volume, and optional /home/ubuntu/RL/.env secrets. Use when running nemo-rl-auto-research campaigns, experiments, training jobs, model or dataset downloads, shared cache-heavy commands, log-producing runs, checkpoint generation, W&B or Hugging Face authenticated workflows, or any workflow that may create large files on Brev.

nvidia/skills1.8Kinstalls3.5Kstars

SKILL.md

Full skill instructions

Brev Etiquette

Operate as though /​home/​ubuntu/​RL is the source checkout and /​ephemeral is the working storage for generated experiment state. Keep the repo small, reproducible, and easy to inspect. Move bulky run outputs to /​ephemeral before launching anything expensive.

Storage Rules

  • Keep code edits, small config changes, committed experiment hypotheses, and concise reproducibility records under /​home/​ubuntu/​RL.
  • Put generated experiment assets under /​ephemeral, including checkpoints, run logs, Ray temp directories, W&B offline files, profiler traces, evaluation dumps, rollout samples, and per-experiment artifacts.
  • Keep reusable caches under one shared /​ephemeral cache root per user, not under each experiment. This includes Hugging Face models, dataset caches, PyTorch caches, Triton caches, uv caches, and pip caches.
  • Before a campaign or long run, check capacity with df -h /​home/​ubuntu/​RL /​ephemeral and avoid starting if /​ephemeral is missing or nearly full.
  • Create a campaign root such as /​ephemeral/​nemo-rl/​${USER:-ubuntu}/​nemo-rl-auto-research/<campaign> and use one subdirectory per experiment.
  • Do not leave large files, cache directories, or generated outputs in the git checkout. If a tool defaults to the repo, override its output/​cache path before running it.

Environment Secrets

  • Treat /​home/​ubuntu/​RL/​.env as the local secret store. It may contain keys such as WANDB_API_KEY, HF_TOKEN, or HUGGING_FACE_HUB_TOKEN.
  • Before any run that may need external auth, load /​home/​ubuntu/​RL/​.env when it exists. Never print, cat, log, commit, or summarize secret values.
  • If /​home/​ubuntu/​RL/​.env is absent, or a required key is still unset after loading it, remind the user to add the needed key to that file before launching authenticated work.
if [ -f /​home/​ubuntu/​RL/​.env ]; then
  set -a
  . /​home/​ubuntu/​RL/​.env
  set +a
else
  echo "Missing /​home/​ubuntu/​RL/​.env; add required keys such as WANDB_API_KEY or HF_TOKEN before authenticated runs."
fi

Auto-Research Pattern

When using nemo-rl-auto-research, keep the git ledger in the repo and heavy evidence on /​ephemeral.

if [ -f /​home/​ubuntu/​RL/​.env ]; then
  set -a
  . /​home/​ubuntu/​RL/​.env
  set +a
fi

BREV_ROOT=/​ephemeral/​nemo-rl/​${USER:-ubuntu}
CACHE_ROOT=$BREV_ROOT/​cache
CAMPAIGN_ROOT=$BREV_ROOT/​nemo-rl-auto-research/<campaign>
EXP_DIR=$CAMPAIGN_ROOT/<experiment>
mkdir -p "$EXP_DIR"/​{logs,checkpoints,artifacts,ray,tmp,wandb}
mkdir -p "$CACHE_ROOT"/​{huggingface,torch,triton,uv,pip,xdg,wandb}

export HF_HOME=$CACHE_ROOT/​huggingface
export HF_HUB_CACHE=$HF_HOME/​hub
export HF_DATASETS_CACHE=$HF_HOME/​datasets
export TRANSFORMERS_CACHE=$HF_HOME/​transformers
export TORCH_HOME=$CACHE_ROOT/​torch
export TRITON_CACHE_DIR=$CACHE_ROOT/​triton
export UV_CACHE_DIR=$CACHE_ROOT/​uv
export PIP_CACHE_DIR=$CACHE_ROOT/​pip
export XDG_CACHE_HOME=$CACHE_ROOT/​xdg
export WANDB_CACHE_DIR=$CACHE_ROOT/​wandb
export RAY_TMPDIR=$EXP_DIR/​ray
export TMPDIR=$EXP_DIR/​tmp
export WANDB_DIR=$EXP_DIR/​wandb

Record the absolute /​ephemeral paths in the nemo-rl-auto-research TSV fields for log path, checkpoint path, artifacts, shared cache root, and command. If the TSV itself may grow large, store the full TSV in /​ephemeral and keep a small pointer file or summary in the repo.

Launch Checklist

  • Inspect disk first: df -h /​home/​ubuntu/​RL /​ephemeral.
  • Choose a unique /​ephemeral run root before editing recipes or launching jobs.
  • Reuse a shared cache root such as /​ephemeral/​nemo-rl/​${USER:-ubuntu}/​cache across experiments unless a run explicitly requires a clean cache.
  • Override recipe output paths, logger paths, checkpoint paths, and temp paths to point under the experiment directory.
  • Override cache paths to point under the shared cache root.
  • Stream stdout/​stderr to $EXP_DIR/​logs/​run.log or an equivalent file under /​ephemeral.
  • Periodically check disk during long runs with df -h /​ephemeral and stop gracefully if the volume is approaching exhaustion.
  • At the end, summarize the important metrics and paths in the repo ledger; do not copy bulky artifacts back into /​home/​ubuntu/​RL.

Cleanup

  • Clean only files that belong to the current campaign or experiment.
  • Prefer pruning clearly named experiment directories under /​ephemeral/​nemo-rl/​...; never remove shared caches or another user's run directory without an explicit instruction.
  • Preserve enough small metadata in the repo to reproduce a result after /​ephemeral is cleaned.

More skills from nvidia

cudaq-guide logo
nvidia/skills

cudaq-guide

CUDA-Q onboarding guide for installation, test programs, GPU simulation, QPU hardware, and quantum applications.

3.5K 2.5K
View
data-designer logo
nvidia/skills

data-designer

Use when the user wants to create a dataset, generate synthetic data, or build a data generation pipeline.

3.5K 2.4K
View
deepstream-dev logo
nvidia/skills

deepstream-dev

NVIDIA DeepStream SDK development with Python pyservicemaker API. Use when building video analytics pipelines, GStreamer-based video processing, TensorRT inference integration, object detection/tracking, or Kafka/message broker integration.

3.5K 2.4K
View
rag-eval logo
nvidia/skills

rag-eval

Filesystem RAG benchmarks: corpus/, train.json, evaluate_rag.py (RAGAS quality). Not for prod monitoring, latency/throughput benchmarking (use rag-perf), or evals outside this repo layout.

3.5K 2.3K
View
nemo-retriever logo
nvidia/skills

nemo-retriever

Use when the user wants to search, query, extract, transcribe, describe, quote, filter, or aggregate across documents — PDFs, scanned forms / images (`.jpg` `.png` `.tiff`), Office (`.docx` `.pptx`), text (`.html` `.txt`), audio (`.mp3` `.wav` `.m4a`), or video (`.mp4` `.mov`). Prefer this over native Read / Grep for multi-file or non-PDF corpora. Not for: editing files, web browsing, single-file plain-text lookups, fine-tuning.

3.5K 2.3K
View

Coordinate the end-to-end CAD/source-asset to SimReady workflow. Use for broad requests such as CAD to SimReady, source asset to simulation-ready USD, or prop packaging that require conversion, material/physics assignment, SimReady conformance, validation, and optional package creation; deploy or verify Content Agents services first when property assignment is enabled; route single-stage work through nested references.

3.5K 2.3K
View

Use this skill to bring any vision model from HuggingFace or NVIDIA NGC into an NVIDIA DeepStream pipeline with end-to-end automation: ONNX download, SafeTensors export, TRT engine build, custom nvinfer bbox parser, multi-stream benchmark, and PDF report. Object detection models only.

3.5K 2.3K
View

Top-level workflow skill for USD performance diagnosis and optimization. Handles slow loading, high memory, low FPS, and broad scene-optimization requests; delegates auth/runtime setup to Phase 0 owners.

3.5K 2.3K
View

Vehicle routing (VRP, TSP, PDP) with cuOpt — Python API only. Use when the user is building or solving routing in Python.

3.5K 2.2K
View

Use only to generate or update a governance skill card for a specified existing agent skill directory. Do not use for explaining, listing, comparing, or discussing skill capabilities.

3.5K 2.2K
View

Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.

3.5K 2.2K
View
rag-perf logo
nvidia/skills

rag-perf

Performance benchmarking for a deployed NVIDIA RAG Blueprint server: profiling pass + aiperf load test driven by a single YAML config. Not for accuracy / RAGAS scoring (use rag-eval) or for deploying / repairing services (use rag-blueprint).

3.5K 2.1K
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View