credentials

Verifies API keys in .env files and prompts users to add missing credentials safely.

1|Updated Aug 31, 2026
One-click install
npx skills add https://github.com/nguyenhungtran18/skill-and-tool-tracker --skill credentials-nguyenhungtran18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: credentials
Source: https://github.com/nguyenhungtran18/skill-and-tool-tracker/tree/main/skills/credentials
Command: npx skills add https://github.com/nguyenhungtran18/skill-and-tool-tracker --skill credentials-nguyenhungtran18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Skills that call external APIs often fail silently or leak secrets when credentials are missing or mishandled. This Skill defines a safe protocol for checking whether required API keys exist in a .env file and prompting the user to add them without ever exposing secret values in the chat or terminal output. ## Core Features & Use Cases - Leak-Free Verification: Uses grep in quiet mode (grep -sq) to confirm a credential exists in ~/.env without printing or reading its value into context. - Secure Prompting Templates: Generates a terminal command using read -s so the user can type the credential with hidden input, appending it to the .env file and creating the file if needed. - Automatic Loading: Explains that helper scripts load credentials via dotenv, so no manual exporting or CLI argument passing is required. - Use Case: When a skill requires ALPHAGENOME_API_KEY, the agent first runs grep -sq "^ALPHAGENOME_API_KEY=" ~/.env; if it fails, it immediately gives the user a hidden-input command plus the registration link instead of attempting the API call. ## Quick Start Check whether the required API key is present in my .env file and, if it is missing, give me a safe terminal command to add it without revealing the value.

Frequently Asked Questions about credentials

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if an API key exists in a .env file without printing it?▼

Use grep in quiet, suppress-errors mode: grep -sq "^CREDENTIAL_NAME=" ~/.env. Exit code 0 means the credential is present; any non-zero code means it is missing or the file does not exist, and the value is never displayed.

How to prompt a user for a credential without leaking it into chat?▼

Generate a terminal command using printf and read -s so the user's typing is hidden, then append the result to the .env file. Never ask the user to paste the secret into the conversation, since that would leak it into context and history.

Can scripts load API keys from .env automatically?▼

Yes, helper scripts load credentials automatically from the .env file using dotenv. Once presence is verified with the safe grep check, you can run the script directly without exporting variables or passing keys as CLI arguments.

What commands should never be used to check credentials?▼

Never run cat ~/.env, grep without the -q flag, echo $VAR, or printenv to inspect credentials. These commands print secret values to the terminal or agent context, defeating the purpose of the safe verification protocol.

What happens if the .env file does not exist yet?▼

The grep -s flag suppresses errors when ~/.env is missing, so the check simply returns a non-zero exit code. The prompting template then creates the .env file automatically when the user runs the provided command to save their credential.