credential-setup

Guide interactive credential setup with tiered secure storage.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill credential-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: credential-setup
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packs/credential-brokers/.apm/skills/credential-setup
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill credential-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires credbroker, pytest, cryptography, argon2, and includes scripts (resource) components.

What problem does it solve?

This Skill removes the friction of manually setting up secrets for other skills by guiding users through the required credential entries and storing them in the safest available location.

Core Features & Use Cases

  • Interactive credential collection: Prompts for each required key from a skill's credential schema.
  • Tiered secure storage: Writes credentials to the OS keyring when available, or falls back to an encrypted vault or protected dotfile on lower-capability systems.
  • Validation and guardrails: Rejects reserved namespaces, requires an interactive terminal, and validates that the schema matches the requested namespace.
  • Use case: A user installs a credentialed integration skill and then runs this Skill to enter API tokens once, without exposing them on the command line or in logs.

Quick Start

Run the credential-setup skill for the target namespace so it can prompt for the required values and store them securely at the highest available tier.

Frequently Asked Questions about credential-setup

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

FAQPage Schema
How do I securely store API keys and secrets for integrations on Linux?

Secure credential setup collects API keys and secrets through interactive tty-only prompting, writing them to the OS keyring, an encrypted vault, or a 0600 dotfile fallback.

How does interactive credential onboarding validate a skill's schema?

Interactive credential onboarding discovers a skill's credential schema and validates it against the requested namespace, rejecting reserved namespaces during the secure setup process.

Do I need an interactive terminal to set up credentials?

Yes, credential setup enforces tty-only prompting to collect secrets interactively, ensuring sensitive values are never exposed on the command line or in logs.

What is the best way to manage secrets without exposing them in CLI logs?

Using secure interactive credential setup with tty-only prompting ensures secrets are collected safely and stored in the highest available tier without appearing in CLI logs.

Does credential setup work with encrypted vaults and OS keyring fallback?

Yes, credential setup uses tiered secure storage that writes to the OS keyring when available, falling back to an encrypted vault or protected dotfile on lower-capability desktop and Linux systems.

Why does schema validation reject reserved namespaces during credential configuration?

Schema validation rejects reserved namespaces during credential configuration to enforce guardrails, preventing users from overwriting critical system namespaces with custom secrets.