← ClaudeAtlas

shadok-secretslisted

Store a credential you OBTAINED yourself (a CLI login, a provisioned key, an API token you just created) in shadok-ai's secret vault, so the next agent doesn't have to obtain it again. Use when you end a task holding a credential that outlives the session. Never for a secret the user typed in the chat.
shadok-ai/shadok-ai · ★ 14 · AI & Automation · score 76
Install: claude install-skill shadok-ai/shadok-ai
# shadok-secrets You sometimes finish a task **holding a credential**: you ran `gh auth login`, provisioned a database, created an API key with a vendor CLI. That credential dies with your session, and the next agent starts from nothing — in a container, where there is no OS keyring, it may not be able to start at all. Put it in the vault instead. Only works inside a shadok-ai agent — it needs `SHADOK_PORT` in the env (set automatically). If it is missing, say so rather than improvising. ## Store it ```bash gh auth token | node ~/.claude/skills/shadok-secrets/scripts/secret.mjs set GITHUB_TOKEN --stdin node ~/.claude/skills/shadok-secrets/scripts/secret.mjs list ``` ## Keep it for yourself — attach it to your profile A stored secret reaches nobody until it is attached to a profile. You can attach a secret **you stored yourself** to **your own** profile, and then reload to get it: ```bash gh auth token | node ~/.claude/skills/shadok-secrets/scripts/secret.mjs set GITHUB_TOKEN --stdin --attach node ~/.claude/skills/shadok-reload/reload.mjs # comes back with it in the env ``` It is injected as an environment variable **at your next reload**, not into the process you are running now — the environment of a live process cannot change. Two limits, and they are not bugs to work around: - **Only a secret you created.** Any other name — one a human typed, one another role stored — is refused. You never held that value, and the vault is shared by every profile on this