Env Update Secrets

Name: Env Update Secrets
Author: aibot88

ASecurity

Use when updating environment secrets like GITHUB_TOKEN, NPM_TOKEN, or API keys on the user's machine

4 stars
0 votes
0 copies
2 views
Added September 12, 2026

securityshellgitapi

Works with

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add aibot88/sec_skill_store --skill env-update-secrets --agent claude-code

Installs 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 with every re-scan.

Security grade badge for Env Update Secrets

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aibot88-env-update-secrets/badge)](https://www.skillsdirectory.com/skills/aibot88-env-update-secrets)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
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.