.claude/skills/secrets/SKILL.md
Manage encrypted secrets between the master vault and projects using SOPS/Age.
npx skillsauth add khamel83/oneshot secretsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage encrypted secrets between the master vault and projects.
Location: ~/github/oneshot/secrets/
Encryption: SOPS + Age (config in ~/github/oneshot/.sops.yaml)
The secrets CLI (at ~/.local/bin/secrets) works from any directory.
# Read a single key
secrets get EXA_API_KEY
# List all vault files and their keys
secrets list
# Decrypt a full file to stdout
secrets decrypt research_keys
# Add/update a key (non-interactive, no commit)
secrets set research_keys 'NEW_KEY=value'
# Add/update + commit + push
secrets set research_keys 'NEW_KEY=value' --commit
# Bootstrap .env in a project from the vault
cd ~/github/myproject && secrets init services
.env.example or imports)secrets init <namespace> to write .env from the vaultsecrets set <namespace> 'KEY=value'secrets set <namespace> 'KEY=value' --commit# Find which vault file contains a key
secrets list | grep -i brave
# Extract a key for use in a script
BRAVE_KEY=$(secrets get BRAVE_API_KEY)
# View all keys in a namespace
secrets decrypt research_keys
~/github/oneshot/secrets/*.encryptedsecrets get searches all vault files for the keysecrets set decrypts the file, merges the new key, re-encryptssecrets init decrypts a vault file to .env in the current directory~/.age/key.txt.env is in .gitignore before writing.env files without encryption| Problem | Fix |
|---------|-----|
| no matching creation rules found | Input file must end in .encrypted (handled by the CLI automatically) |
| key not found in any vault file | Key doesn't exist in any vault — add it with secrets set |
| file not found | Check secrets list for available namespaces |
development
Smart visual analysis for websites and images using Playwright screenshots and AI vision.
development
--- name: tdd description: Test-driven development with mandatory RED-GREEN-REFACTOR cycle. Enforces writing failing tests before production code. Use when implementing new features, fixing bugs with test coverage, or when the user wants TDD discipline. Trigger keywords: tdd, test first, test driven, red green refactor, add tests, coverage, write a test, failing test. --- # /tdd — Test-Driven Development RED-GREEN-REFACTOR cycle. No production code without a failing test shown first. ## Usage
tools
Quick iterations on existing projects. Load context, ask what's next, execute in burn-down mode.
documentation
Restore context from a handoff document and continue work.