output-credentials-init

Included with Lifetime

$97 forever

Initialize encrypted credentials for an Output.ai project. Use when setting up credentials for the first time, adding environment-specific credentials, or adding per-workflow credentials.

General

What this skill does


# Initializing Credentials

## When to Use This Skill

- First time setting up credentials for a project
- Adding production/staging environment-specific credentials
- Adding per-workflow credentials that override global ones
- Re-initializing credentials after losing a key file

## Overview

The `npx output credentials init` command generates two files:
- A **key file** (`.key`) — the decryption secret. **Never commit this.**
- An **encrypted YAML file** (`.yml.enc`) — the credentials store. Safe to commit.

## Commands

```bash
# Global credentials (most common)
npx output credentials init

# Environment-specific
npx output credentials init -e production
npx output credentials init -e staging

# Per-workflow credentials (overrides globals for that workflow)
npx output credentials init -w my_workflow

# Force overwrite existing files
npx output credentials init --force
```

## What Gets Created

### Global (default)

```
config/
├── credentials.key        ← Add to .gitignore
└── credentials.yml.enc    ← Safe to commit
```

### Environment-specific

```
config/credentials/
├── production.key         ← Add to .gitignore
└── production.yml.enc     ← Safe to commit
```

### Per-workflow

```
src/workflows/{name}/
├── credentials.key        ← Add to .gitignore
└── credentials.yml.enc    ← Safe to commit
```

## Default Template

After init, the encrypted YAML contains this template:

```yaml
anthropic:
  api_key: ""
openai:
  api_key: ""
_env:
  ANTHROPIC_API_KEY: anthropic.api_key
  OPENAI_API_KEY: openai.api_key
```

The `_env` section wires credentials to environment variables automatically at worker startup. See `output-credentials-env-vars` for details.

## After Init: Add Your Secrets

```bash
npx output credentials edit          # Opens $EDITOR with decrypted YAML
```

Fill in the empty values, save, and close. The file is re-encrypted automatically.

## Gitignore Setup

```bash
echo "*.key" >> .gitignore
echo "config/credentials.key" >> .gitignore
```

Or add to your `.gitignore`:

```
# Credentials decryption keys — never commit
*.key
config/credentials.key
config/credentials/*.key
src/workflows/*/credentials.key
```

## CI/CD: Key Distribution

In CI/CD pipelines, pass the key as an environment variable instead of committing the file:

```bash
# Set in your CI/CD environment
OUTPUT_CREDENTIALS_KEY=<key-value>

# Environment-specific
OUTPUT_CREDENTIALS_KEY_PRODUCTION=<key-value>

# Per-workflow
OUTPUT_CREDENTIALS_KEY_MY_WORKFLOW=<key-value>
```

The key value is the contents of the `.key` file.

## Verification Checklist

- [ ] `config/credentials.key` created (or env-specific variant)
- [ ] `config/credentials.yml.enc` created
- [ ] `.key` files added to `.gitignore`
- [ ] `npx output credentials edit` run to fill in secret values
- [ ] `npx output credentials show` verifies decryption works

## Related Skills

- `output-credentials-edit` — Fill in and manage credential values
- `output-credentials-env-vars` — Wire credentials to environment variables
- `output-dev-credentials` — Full credentials system reference

Files: 1

Size: 3.3 KB

Complexity: 12/100

Category: General

Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-credentials-init

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts