Credential Vault Specialist

Manage encrypted multi-tenant API credentials with AES-256 (Fernet) encryption.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/adriangmrraa/MultiAgents-Platform-ROI --skill credential-vault-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Credential Vault Specialist
Source: https://github.com/adriangmrraa/MultiAgents-Platform-ROI/tree/main/.agent/skills/Credential_Vault_Specialist
Command: npx skills add https://github.com/adriangmrraa/MultiAgents-Platform-ROI --skill credential-vault-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and secures tenant API keys and secrets to prevent accidental exposure, enforce ownership boundaries, and enable safe runtime usage without relying on insecure environment variables.

Core Features & Use Cases

  • Encrypted Storage: AES-256 (Fernet) encryption of all credential values at rest.
  • Multi-tenant Isolation: Tenant-specific credentials with optional global fallbacks and strict ownership validation.
  • Operational Tooling: Masked listing, key rotation, metadata for expiration tracking, SMTP JSON configs, and runtime decryption for API calls.
  • Use Case: Store and rotate OpenAI, Google, WhatsApp Cloud, and SMTP credentials per tenant so services can retrieve keys at runtime without exposing secrets in logs or frontends.

Quick Start

Save an OpenAI API key for tenant 42 under category openai with name API_KEY and scope tenant so the orchestrator can decrypt it at runtime.

Frequently Asked Questions about Credential Vault Specialist

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

FAQPage Schema
How do I securely store and manage multi-tenant API keys without using environment variables?

Secure multi-tenant API keys by encrypting them at rest with AES-256 (Fernet) and storing them in a centralized credential vault. This enforces ownership boundaries and prevents accidental exposure without relying on insecure environment variables.

What is the best way to rotate tenant-specific credentials and track their expiration?

Track credential expiration and rotate tenant-specific credentials using a centralized vault that supports metadata-based expiration tracking. This allows platform administrators to update keys safely while maintaining strict ownership validation.

Does this credential vault support global fallback when tenant-specific secrets are missing?

Yes, the credential vault supports global fallback resolution. If tenant-specific credentials are missing, the system automatically resolves and retrieves global fallback credentials while maintaining strict tenant isolation and ownership validation.

How do I list API credentials for tenants without exposing sensitive secret values?

List API credentials without exposing secrets by using masked listing functionality. The vault returns metadata and masked values for tenant and global scopes, ensuring sensitive encrypted data remains hidden during administrative audits.

Can I store and manage SMTP JSON configurations alongside OpenAI and WhatsApp Cloud API keys?

Yes, you can store SMTP JSON configurations alongside OpenAI and WhatsApp Cloud API keys. The vault securely encrypts and manages various credential categories per tenant for runtime decryption and on-demand API usage.