Agent skill

Output Credentials Env Vars

Wire encrypted credentials to environment variables using the credential: convention.

Apache-2.0Auto-check: notesAI & LLM Engineering

Install Output Credentials Env Vars

skills CLI

$ npx skills add growthxai/output --skill output-credentials-env-vars -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install growthxai/output output-credentials-env-vars --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars .claude/skills/output-credentials-env-vars && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "output-credentials-env-vars" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars into .claude/skills/output-credentials-env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-credentials-env-vars", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add growthxai/output --skill output-credentials-env-vars -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install growthxai/output output-credentials-env-vars --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .agents/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars .agents/skills/output-credentials-env-vars && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "output-credentials-env-vars" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars into .agents/skills/output-credentials-env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-credentials-env-vars", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add growthxai/output --skill output-credentials-env-vars -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install growthxai/output output-credentials-env-vars --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars .cursor/skills/output-credentials-env-vars && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "output-credentials-env-vars" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars into .cursor/skills/output-credentials-env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-credentials-env-vars", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/growthxai/output.git --path coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add growthxai/output --skill output-credentials-env-vars -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install growthxai/output output-credentials-env-vars --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars .gemini/skills/output-credentials-env-vars && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "output-credentials-env-vars" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars into .gemini/skills/output-credentials-env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-credentials-env-vars", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install growthxai/output output-credentials-env-vars

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add growthxai/output --skill output-credentials-env-vars -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .github/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars .github/skills/output-credentials-env-vars && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "output-credentials-env-vars" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars into .github/skills/output-credentials-env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-credentials-env-vars", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add growthxai/output --skill output-credentials-env-vars -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install growthxai/output output-credentials-env-vars --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars .opencode/skills/output-credentials-env-vars && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "output-credentials-env-vars" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars into .opencode/skills/output-credentials-env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-credentials-env-vars", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: output-credentials-env-vars
GitHub stars: 442
Token cost: ~930 tokens
SKILL.md length: 296 words
Files: 1
Skills in repo: 50
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Wire encrypted credentials to environment variables using the credential: convention.

Works in 3 steps: Initialize credentials (if not done) → Update .env → Verify
Setting up LLM provider keys (ANTHROPICAPIKEY
SKILL.md covers When to Use This Skill, The credential: Convention, How It Works and Precedence Rules, plus 3 more sections
Calls npx; needs ANTHROPIC_API_KEY and OPENAI_API_KEY

What it does

Output Credentials Env Vars is an agent skill from growthxai/output. Wire encrypted credentials to environment variables using the credential: convention. Use when setting up LLM provider keys (ANTHROPICAPIKEY, OPENAIAPIKEY) or any env var that should come from encrypted credentials.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering LLM API integration and Secrets management. It works with Anthropic API and OpenAI. The repository describes itself as: The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code describe what you want, Claude builds it, with all the best practices already… The licence is Apache-2.0.

When your agent uses it

Setting up LLM provider keys (ANTHROPICAPIKEY
Any env var that should come from encrypted credentials

Example prompts

“/output-credentials-env-vars”

Requirements

Node.js
A credential in ANTHROPIC_API_KEY
A credential in OPENAI_API_KEY
Pre-approved tools (allowed-tools): Read, Edit, Bash, Glob

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Initialize credentials (if not done)
Update .env
Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 99ee298. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Edit
- Bash
- Glob
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- ANTHROPIC_API_KEY
- OPENAI_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Output Credentials Env Vars loads about 930 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 296 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~62
When it runs · the whole SKILL.md, loaded when a task matches: ~930

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:13

- Migrating from plaintext `.env` secrets to encrypted credentials

NoteMentions a .env fileSKILL.md:24
```
### Example `.env`
```
NoteMentions a .env fileSKILL.md:81
```
### Step 2: Update `.env`
```

NoteMentions a .env fileSKILL.md:102

- [ ] `.env` uses `credential:<path>` values for the relevant env vars

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Edit, Bash, Glob
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from growthxai/output at commit 99ee298, republished under its Apache-2.0 licence (© growthxai). 296 words, ~930 tokens.

Download SKILL.mdSave it as .claude/skills/output-credentials-env-vars/SKILL.md (or your agent's skills folder).

name: output-credentials-env-vars
description: Wire encrypted credentials to environment variables using the credential: convention. Use when setting up LLM provider keys (ANTHROPIC_API_KEY, OPENAI_API_KEY) or any env var that should come from encrypted credentials.
allowed-tools: Read, Edit, Bash, Glob

Credentials as Environment Variables

When to Use This Skill

Setting up ANTHROPIC_API_KEY or OPENAI_API_KEY from encrypted credentials
Wiring any credential path to a process.env variable automatically
Migrating from plaintext .env secrets to encrypted credentials
Understanding why an env var is being resolved at worker startup

The `credential:` Convention

Any env var whose value starts with credential: is resolved from encrypted credentials at worker startup. The format is:

ENV_VAR_NAME=credential:<dot.path>

Example `.env`

bash

# These are resolved automatically from the global credentials
ANTHROPIC_API_KEY=credential:anthropic.api_key
OPENAI_API_KEY=credential:openai.api_key

# Any credential path works
MY_SERVICE_TOKEN=credential:my_service.token
DATABASE_URL=credential:postgres.url

Encrypted credentials (`config/credentials.yml.enc`)

yaml

anthropic:
  api_key: sk-ant-...        # → resolves ANTHROPIC_API_KEY

openai:
  api_key: sk-...            # → resolves OPENAI_API_KEY

my_service:
  token: tok_live_...        # → resolves MY_SERVICE_TOKEN

postgres:
  url: postgres://...        # → resolves DATABASE_URL

How It Works

When the worker starts, every env var set to credential:<path> is replaced with the decrypted value at that path. By the time a workflow runs, ANTHROPIC_API_KEY holds the real key and LLM SDKs read it as usual.

Values come from the global credentials for the current environment: config/credentials/<NODE_ENV>.yml.enc when it exists, otherwise config/credentials.yml.enc. Workflow-scoped credentials are never used for env vars, so keep these paths in the global file.

Precedence Rules

Real env var values always take precedence. If ANTHROPIC_API_KEY is already set to a non-credential: value (e.g. from the shell or a CI secret), it is never overwritten:

bash

# Real value - never replaced
ANTHROPIC_API_KEY=sk-ant-real-override

# Placeholder — gets replaced at startup
ANTHROPIC_API_KEY=credential:anthropic.api_key

This means you can override any credential ref at deploy time without changing files.

Setting Up the Convention

Step 1: Initialize credentials (if not done)

bash

npx output credentials init
npx output credentials edit   # Add anthropic.api_key, openai.api_key

Step 2: Update `.env`

bash

# Replace plaintext secrets with credential references
ANTHROPIC_API_KEY=credential:anthropic.api_key
OPENAI_API_KEY=credential:openai.api_key

Step 3: Verify

Start the worker and look for the log line:

[info] Credentials: Resolved credential env vars { vars: [ "ANTHROPIC_API_KEY", "OPENAI_API_KEY" ] }

If the log line lists your env vars, credentials are wired correctly.

Verification Checklist

config/credentials.yml.enc contains the target credential paths
.env uses credential:<path> values for the relevant env vars
Worker startup log shows Resolved credential env vars listing the expected env vars
First LLM workflow run succeeds (confirming ANTHROPIC_API_KEY is set correctly)
Setting a real env var in the shell overrides the credential ref

output-credentials-init — Create the encrypted credentials file
output-credentials-edit — Add/update credential values
output-dev-credentials — Full credentials system reference

Files

Just SKILL.md in coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars of growthxai/output.

Open the folder on GitHubat commit 99ee298

Compare with similar skills

Output Credentials Env Vars next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Output Credentials Env Vars compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Output Credentials Env Vars this skillgrowthxai/output	442	—	~930	Automated safety check: Notes	Apache-2.0	yesterday
ModLens Image Vision Bridgeliustack/modlens	4.2k	—	~1.3k	Automated safety check: Notes	MIT	7 days ago
Claude APIKocoro-lab/Kocoro	414	7 repos	~4.5k	Automated safety check: Pass	Apache-2.0	1 mo ago
Using Ccproxy Inspectorstarbaser/ccproxy	350	—	~2.7k	Automated safety check: Pass	Custom licence	2 mo ago
Using Ccproxy APIstarbaser/ccproxy	350	—	~4k	Automated safety check: Pass	Custom licence	2 mo ago
Update Libstingly-dev/tingly-box	351	—	~830	Automated safety check: Pass	MPL-2.0	today

Similar skills

ModLens Image Vision Bridge
liustack/modlens
Gives text-only models sight by running the modlens CLI on an image path or URL and returning structured JSON evidence with transcribed text, layout and semantics.
4.2k GitHub stars~1.3k tokensUpdated 7 days ago
AI & LLM EngineeringAuto-check: notes
Claude API
Kocoro-lab/Kocoro
Build apps with the Claude API or Anthropic SDK. An agent skill from Kocoro-lab/Kocoro.
414 GitHub starsUsed in 7 repos~4.5k tokens
AI & LLM EngineeringAuto-check passed
Using Ccproxy Inspector
starbaser/ccproxy
Operates the ccproxy inspector MITM system for intercepting, inspecting, and transforming LLM API traffic.
350 GitHub stars~2.7k tokensUpdated 2 mo ago
AI & LLM EngineeringAuto-check passed
Using Ccproxy API
starbaser/ccproxy
Guides users through ccproxy as an OpenAI-compatible and Anthropic-compatible LLM API server with SDK integration, OAuth authentication, sentinel key substitution, model routing, and troubleshooting.
350 GitHub stars~4k tokensUpdated 2 mo ago
AI & LLM EngineeringAuto-check passed
Update Libs
tingly-dev/tingly-box
Update the libs/ SDK submodules (openai-go, anthropic-sdk-go, go-genai) to new upstream/fork versions, adapt tingly-box to API changes, and verify with build + vet + tests.
351 GitHub stars~830 tokensUpdated today
AI & LLM EngineeringAuto-check passed
Get API Docs
sudomakes/backroad
A skill your agent uses when you need documentation for a third-party library, SDK, or API before writing code that uses it — for example, "use the OpenAI API", "call the Stripe API", "use the…
162 GitHub stars~1k tokensUpdated 3 mo ago
AI & LLM EngineeringAuto-check passed

Questions about Output Credentials Env Vars

What does Output Credentials Env Vars do?

Wire encrypted credentials to environment variables using the credential: convention. Output Credentials Env Vars is an agent skill from growthxai/output. Wire encrypted credentials to environment variables using the credential: convention.

When should I use Output Credentials Env Vars?

Output Credentials Env Vars fits situations like: setting up LLM provider keys (ANTHROPICAPIKEY; any env var that should come from encrypted credentials.

How do I install Output Credentials Env Vars in Claude Code?

Run `npx skills add growthxai/output --skill output-credentials-env-vars -a claude-code`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars in growthxai/output) into .claude/skills/output-credentials-env-vars in your project. Claude Code loads it when a task matches its description.

How do I install Output Credentials Env Vars in Codex?

Run `npx skills add growthxai/output --skill output-credentials-env-vars -a codex`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-credentials-env-vars in growthxai/output) into .agents/skills/output-credentials-env-vars in your project. Codex loads it when a task matches its description.

Can I use Output Credentials Env Vars in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthxai/output --skill output-credentials-env-vars -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/output-credentials-env-vars, .gemini/skills/output-credentials-env-vars, .github/skills/output-credentials-env-vars and .opencode/skills/output-credentials-env-vars in your project.

What does Output Credentials Env Vars need to run?

Going by SKILL.md and its folder, Output Credentials Env Vars needs the command-line tools its instructions call (npx) and credentials named ANTHROPIC_API_KEY and OPENAI_API_KEY. Our summary lists: Node.js; A credential in ANTHROPIC_API_KEY; A credential in OPENAI_API_KEY. Its frontmatter pre-approves these tools: Read, Edit, Bash, Glob.

Does Output Credentials Env Vars access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Output Credentials Env Vars safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Output Credentials Env Vars use?

Output Credentials Env Vars is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Output Credentials Env Vars use?

About 930 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Output Credentials Env Vars?

Skills that share tags, products or a category with Output Credentials Env Vars: ModLens Image Vision Bridge (liustack/modlens, 4.2k stars), Claude API (Kocoro-lab/Kocoro, 414 stars), Using Ccproxy Inspector (starbaser/ccproxy, 350 stars) and Using Ccproxy API (starbaser/ccproxy, 350 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Output Credentials Env Vars?

growthxai (a GitHub organization) maintains it in growthxai/output, which has 442 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.

Source: growthxai/output on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Output Credentials Env Vars

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Credentials as Environment Variables

When to Use This Skill

The credential: Convention

Example .env

Encrypted credentials (config/credentials.yml.enc)

How It Works

Precedence Rules

Setting Up the Convention

Step 1: Initialize credentials (if not done)

Step 2: Update .env

Step 3: Verify

Verification Checklist

Related Skills

Files

Compare with similar skills

Similar skills

More from growthxai/output

Related

Questions about Output Credentials Env Vars

The `credential:` Convention

Example `.env`

Encrypted credentials (`config/credentials.yml.enc`)

Step 2: Update `.env`