# Secrets

> NeMo Platform secret CRUD lifecycle through the platform SDK.

- Skill: `nvidia-nemo/secrets` (Agent Skill)
- Install (CLI): `npx skillmds@latest add nvidia-nemo/secrets`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nvidia-nemo/secrets/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: NVIDIA NeMo (https://skillmd.com/u/nvidia-nemo)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/nvidia-nemo/secrets

---

Secret tasks

- Use `nemo_api` with resource `secrets`, passing
  `workspace="<active request workspace>"` on every call.
- Use `create`, `retrieve`, `list`, `update`, and `delete` actions as needed,
  passing only secret references (`<workspace>/<name>`), names, and metadata in
  JSON `params`, never resolved secret values. Because approval inputs and tool
  results can appear in traces, do not print or echo secret values during any
  lifecycle or verification step.
- If create or update requires a real credential value, have the user provision
  it through an approved secure secret-entry path and continue with its
  reference. Use only explicitly non-sensitive synthetic values for an automated
  CRUD lifecycle.
- Always finish the whole lifecycle: create temporary secret, verify/list/update/delete it, then create the final verification secret.