RepoAI
Browse MCPs

Credentials

100TrustedInstructions only

Standardized methods for checking and storing private keys without chat history exposure.

What it does

Installing this skill changes how an assistant handles sensitive authentication data. Instead of asking for API keys in the conversation window, the assistant initiates a secure protocol that directs the user to input keys directly into a local .env file. This prevents sensitive information from being saved in chat logs or memory.

The skill provides a structured way to confirm that a required key exists before executing any task. It acts as a gatekeeper that ensures the assistant never attempts to process operations that depend on external services until the environment is configured correctly.

When it earns its place

Reach for it when…

Use this skill when your environment requires API keys or authentication tokens to perform specific tasks, and you want to keep those values out of the chat history.

Look elsewhere when…

This is not for managing general application configuration or file storage. Do not use this to bypass authentication requirements or to handle public project settings that can safely exist in code repositories.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • How can I set up my API keys for this tool?
  • Check if I have the correct environment variables.
  • Add my authentication token safely.
  • Verify the credentials for the new skill I installed.

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch main https://github.com/google-deepmind/science-skills.git /tmp/science-skills
mkdir -p ~/.claude/skills
cp -r /tmp/science-skills/skills/credentials ~/.claude/skills/credentials

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/science-skills/skills/credentials .claude/skills/credentials

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

Credentials changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →