pikku-config

Centralize secrets, environment variables, and OAuth2 credentials for Pikku apps.

56|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/pikkujs/pikku --skill pikku-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pikku-config
Source: https://github.com/pikkujs/pikku/tree/main/.claude/skills/pikku-config
Command: npx skills add https://github.com/pikkujs/pikku --skill pikku-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing secrets, environment variables, config, and OAuth2 credentials inside Pikku apps without using process.env, with typed access and safe patterns.

Core Features & Use Cases

  • Centralized secret and config management using wireSecret, wireVariable, and wireOAuth2Credential
  • Typed access to secrets and variables via services, enabling safer, more predictable code
  • OAuth2 credential handling and cross-environment config for dev/stage/prod
  • Real-world use: securely connect to external APIs and toggle features without leaking secrets

Quick Start

Configure your Pikku app to wireSecret, wireVariable, and wireOAuth2Credential, then read them via the typed services in your functions.

Frequently Asked Questions about pikku-config

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

FAQPage Schema
How do I manage secrets and environment variables in Pikku apps without using process.env?

To manage secrets without process.env in Pikku apps, use wireSecret and wireVariable. These functions provide typed access to credentials via services, enforcing safe patterns for secure config retrieval across development, staging, and production environments.

What is the best way to handle OAuth2 credentials in a Pikku application?

The best way to handle OAuth2 credentials in a Pikku app is using wireOAuth2Credential. It centralizes OAuth2 credential management, providing typed access through services to securely connect to external APIs without leaking secrets across environments.

How do I securely access environment configuration across dev, staging, and production?

Secure cross-environment configuration is achieved by wiring variables and secrets centrally. Typed services read these wired values, allowing you to safely toggle features and access config predictably without handling environment variables inside functions.

Why should I avoid directly accessing process.env inside my application functions?

Accessing process.env directly in functions is unsafe and untyped. Pikku enforces safe patterns by centralizing config retrieval through wired services, preventing secret leaks and ensuring predictable, typed access to credentials and environment variables.

Can I use typed services to securely connect to external APIs and toggle features?

Yes, you can use typed services to securely connect to external APIs and toggle features. By wiring secrets, variables, and OAuth2 credentials, your functions gain typed access to config, enabling safe external connections without leaking secrets.