Claude Skill

secrets-manager

Handle secrets safely via env vars, Vault, AWS Secrets Manager, or encrypted stores - never paste keys into chat, commits, or logs. Use when configuring APIs, CI, or cloud credentials.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_secrets-manager-e9c73a3.zip · 0 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 4d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/secrets-manager

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Secrets Manager

Overview

Secrets stay in secret stores or environment variables. Chat history and git are not vaults.

Preferred patterns

Read from env (os.environ / shell env) already configured on the host
Reference Vault / AWS SM / 1Password CLI paths - fetch at runtime, do not cache in markdown
Use provider Settings in Navin WebUI for API keys when available
For CI: repository secrets / OIDC - not hardcoded values

Workflow

Identify which secret is needed and which store holds it.
Confirm it is not already in the repo (grep for key-shaped strings).
Wire the tool/config to the env var name - do not print the value.
Redact any accidental exposure in your reply (sk-***, AKIA***).
If a secret leaked into chat or git, tell the user to rotate it.

Forbidden

Committing .env with real values
Putting tokens in SKILL.md or memory files
Echoing full secrets in tool arguments visible to the user when avoidable

Files (navin)

SKILL.md 1.2 KB

---
name: secrets-manager
description: Handle secrets safely via env vars, Vault, AWS Secrets Manager, or encrypted stores - never paste keys into chat, commits, or logs. Use when configuring APIs, CI, or cloud credentials.
metadata: {"navin":{"emoji":"🔐","category":"security"}}
---

# Secrets Manager

## Overview

Secrets stay in secret stores or environment variables. Chat history and git are not vaults.

## Preferred patterns

1. Read from env (`os.environ` / shell env) already configured on the host
2. Reference Vault / AWS SM / 1Password CLI paths - fetch at runtime, do not cache in markdown
3. Use provider Settings in Navin WebUI for API keys when available
4. For CI: repository secrets / OIDC - not hardcoded values

## Workflow

1. Identify which secret is needed and which store holds it.
2. Confirm it is **not** already in the repo (`grep` for key-shaped strings).
3. Wire the tool/config to the env var name - do not print the value.
4. Redact any accidental exposure in your reply (`sk-***`, `AKIA***`).
5. If a secret leaked into chat or git, tell the user to **rotate** it.

## Forbidden

- Committing `.env` with real values
- Putting tokens in `SKILL.md` or memory files
- Echoing full secrets in tool arguments visible to the user when avoidable