Use when updating environment secrets like GITHUB_TOKEN, NPM_TOKEN, or API keys on the user's machine
Scanned 9/12/2026
Install to Claude Code
npx -y skills add aibot88/sec_skill_store --skill env-update-secrets --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Env Update Secrets?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aibot88-env-update-secrets)More formats (shields.io, HTML) on the badges page.
---
name: env-update-secrets
description: Use when updating environment secrets like GITHUB_TOKEN, NPM_TOKEN, or API keys on the user's machine
---
# Updating Environment Secrets
## Location
All secrets live in: `~/.config/fish/config.secrets.fish`
This file is sourced by `~/.config/fish/config.fish` on shell startup.
## Format
```fish
export VAR_NAME='value'
```
## Current Secrets
| Variable | Purpose |
|----------|---------|
| `GITHUB_TOKEN` | GitHub CLI and API authentication |
| `NPM_TOKEN` | npm registry authentication |
| `NPM_PUBLISH_TOKEN` | npm package publishing |
## Workflow
1. Read `~/.config/fish/config.secrets.fish`
2. Edit the relevant `export` line with new value
3. Tell user to reload: `source ~/.config/fish/config.fish`
## Adding New Secrets
Add new `export` lines to the same file. Keep secrets consolidated here rather than scattered across dotfiles.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。