Redact CLI outputs and manage environment variables to keep secrets out of conversation context.
npx skills add https://github.com/spences10/skills --skill nopeek
Please help me install this Agent Skill. Skill: nopeek Source: https://github.com/spences10/skills/tree/main/nopeek Command: npx skills add https://github.com/spences10/skills --skill nopeek
This Skill ensures that secrets, such as API keys and credentials, are kept secure during agent sessions by preventing their exposure in conversation context or logs.
Run the nopeek init command to scan and migrate your cloud CLI authentication to profile-based auth.
High-intent search queries and answers about installing and using this skill.
To keep API keys and credentials safe in agent sessions, you can redact CLI outputs and manage environment variables so only key names, not values, enter the conversation context.
CLI redaction for secret management prevents sensitive values from being printed by CLI commands during agent sessions, ensuring secrets stay out of conversation logs and context.
Yes, you need jq installed as a dependency to parse and redact CLI outputs, enabling the secure loading and setting of .env secrets during agent sessions.
You can migrate cloud CLI authentication to profile-based auth by running an initialization command that scans your setup and securely transitions credentials away from plain environment variables.
Yes, you can load and set .env secrets safely without exposing values to agents by using environment variable management techniques that restrict conversation context to key names only.
ostsamGuide users to generate, validate, and store a Vapi API key in .env.
interflownexDiagnose missing Google Cloud authentication and restore ADC via gcloud commands.
Cogni-AI-OULoad per-directory environment variables securely without exposing secrets.
Solitude01Manage 1Password CLI secrets and inject credentials in tmux sessions.
