nanogptlisted
Install: claude install-skill arpanmukherjee1/skills
# NanoGPT
Every generation call spends the user's real balance. Treat each paid call as spending their money, and never make one before the pre-flight in section 2 is complete and approved.
## 1. The credential: `nanogpt.key`
The key lives in a file named `nanogpt.key`. Scripts look for it in two places, in this order:
1. The directory containing this SKILL.md (claude.ai uploads and manual installs).
2. `~/.config/nanogpt/nanogpt.key` (Claude Code plugin installs, whose skill directory is replaced on every update).
- **Never read it.** No `cat`, `head`, `tail`, `less`, `view`, `grep`, `sed`, `strings`, `xxd`, `base64`, no `python -c` that prints it, no recursive search/listing-with-contents of the skill directory or `~/.config/nanogpt/` unless the key file is excluded. Never copy, move, rename, archive or upload it, and never place it under the outputs directory.
- **Only scripts use it.** A script you write opens the file, holds the value in memory, and puts it into the HTTP auth header. Nothing else. The script must never print, log, return, interpolate into a URL/filename/error, or pass it on the command line or through an environment variable you set in a visible command.
- If the script finds no usable key file (missing, unreadable, empty or still the placeholder in both places), it exits with a message that does not contain the key. Tell the user to save their key as `~/.config/nanogpt/nanogpt.key`, or on claude.ai to put `nanogpt.key` in the skill folder and upload