credentials
Instructions for handling API keys and credentials safely, verifying their presence, and prompting the user to add them if missing using a safe protocol.
Install / Use
npx skills add google-deepmind/science-skills --skill credentialsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of credentials
credentials scores 87/100 on our quality scale, 2135th of 4,698 Development & Engineering skills we index (top 46%).
Its SKILL.md is 4.1 KB long, split into 6 sections with 2 code examples: a solid amount of guidance for an agent.
With 3,137 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so credentials is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
credentials compared with similar skills
All 4 of these similar skills score higher than credentials; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| credentials (this skill)by google-deepmind | 87 | 3.1k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
Frequently asked questions
- How do I install credentials?
- Run
npx skills add google-deepmind/science-skills --skill credentials. The install tabs above show the steps for each supported agent. - Which AI agents does credentials work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is credentials safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is credentials still maintained?
- The repository was last updated about 2 months ago, so credentials is actively maintained.
Skill content
View source on GitHubname: credentials description: >- Instructions for handling API keys and credentials safely, verifying their presence, and prompting the user to add them if missing using a safe protocol.
Safe Credentials Protocol
Many skills require API keys or other credentials to function or to access higher rate limits. This skill defines the standard safe credentials protocol for verifying and prompting for these credentials without leaking sensitive keys into the agent context or the conversation history.
Safe Verification (No Leaks)
As soon as a skill that requires a credential or API key looks relevant to the
user's request, you MUST immediately verify if the credential is present in
the .env file (typically located in your home directory ~/.env or the
project root) — before doing any other work for that skill.
CRITICAL: You must verify the presence of the credential without printing its value to the terminal or reading it into your context.
How to verify:
Use grep in quiet and suppress-errors mode (-sq) to check if the variable is
defined in ~/.env. The -s flag ensures the command works cleanly even if
~/.env does not exist yet.
grep -sq "^CREDENTIAL_NAME=" ~/.env
Replace CREDENTIAL_NAME with the actual credential name required by the
calling skill (e.g., ALPHAGENOME_API_KEY or USER_EMAIL).
- If the command succeeds (exit code 0), the credential is present. You can proceed.
- If the command fails (any non-zero exit code — whether the credential is
missing or the
.envfile does not exist yet), the credential is missing. You MUST IMMEDIATELY stop and prompt the user to add it using the instructions in Prompting the User to Add Credentials before attempting to run any scripts or tools. Do not conclude the turn by simply stating that the key is missing.
[!CRITICAL] If verification fails (any non-zero exit code), you MUST NOT attempt to execute any tools or scripts from the calling skill, nor should you conclude the turn by simply reporting the missing key. You MUST IMMEDIATELY generate the appropriate terminal command from the templates below and prompt the user to run it. The template command will create the
.envfile if it does not already exist.
NEVER run cat ~/.env, grep "VAR" ~/.env (without -q), echo $VAR, or
printenv to check for credentials.
Prompting the User to Add Credentials
If a credential is missing, do NOT ask the user to paste it into the chat. This would leak the value into the agent's context and the conversation history.
Instead, you MUST generate a specific command for the user to run in their terminal by replacing the placeholders in one of the templates below.
CRITICAL: Before presenting the command to the user, you MUST replace:
CREDENTIAL_NAMEwith the actual variable name needed (e.g.,ALPHAGENOME_API_KEY,USER_EMAIL).ENV_FILEwith the resolved literal path to the.envfile (usually~/.env).
Template
All credentials are treated as sensitive. The read -s flag hides the user's
typing. You MUST inform the user that their typing will be hidden.
CRITICAL: When requesting a credential, you MUST also provide the user with the appropriate registration link or instructions provided by the calling skill so they know how to obtain the value if they do not have one.
printf "Enter CREDENTIAL_NAME (typing hidden): " && read -s val && echo && echo "CREDENTIAL_NAME=$val" >> "ENV_FILE" && echo "Saved."
Running scripts requiring credentials
All helper scripts inside the calling skills load these credentials
automatically from the .env file using dotenv.
You do NOT need to manually read the keys, export them to the shell
environment, or pass them as CLI arguments, when calling the helper scripts that
require them. As long as you have verified the key is present in .env using
the safe protocol above, simply run the script directly — the script will load
the credential automatically.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
