credentials

Store and retrieve encrypted API credentials for trading platforms.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/shreed27/DAIN --skill credentials-shreed27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: credentials
Source: https://github.com/shreed27/DAIN/tree/main/CloddsBot-main/src/skills/bundled/credentials
Command: npx skills add https://github.com/shreed27/DAIN --skill credentials-shreed27

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a secure and encrypted way to store, manage, and retrieve API credentials for various trading platforms, preventing sensitive keys from being exposed.

Core Features & Use Cases

  • Encrypted Storage: Uses AES-256-GCM encryption to protect API keys and secrets at rest.
  • Platform Support: Supports multiple trading platforms including Polymarket, Kalshi, Binance, and Hyperliquid.
  • Use Case: A user needs to connect their trading bot to Binance Futures. They can use the /creds set binance --key <api_key> --secret <api_secret> command to securely store their Binance API credentials, which the bot can then access without the keys ever being visible in plain text.

Quick Start

Use the credentials skill to add your Binance API key and secret.

Frequently Asked Questions about credentials

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

FAQPage Schema
How do I securely store trading API keys for platforms like Binance or Polymarket?

You can securely store trading API keys by using AES-256-GCM encryption to protect credentials at rest in a SQLite database. This prevents sensitive API keys and secrets from being exposed in plain text while allowing automated retrieval.

What is the best way to manage encrypted credentials for Hyperliquid or Kalshi without exposing them?

Managing encrypted credentials involves adding, listing, and deleting API keys through a secure storage system that utilizes environment variables for encryption keys. This ensures secrets remain encrypted at rest within a persistent SQLite database.

Does this credential management approach support testing API keys before saving them?

Yes, the credential management system supports testing credentials for supported trading platforms. You can verify that API keys and secrets are valid before relying on them for automated trading operations.

How do I add my Binance Futures API key and secret so my trading bot can access them securely?

To add Binance Futures API credentials, use the set command with your api key and secret. The system encrypts the credentials using AES-256-GCM and stores them in a SQLite database for secure bot access.

What encryption standard is used to protect API keys stored in a SQLite database?

AES-256-GCM encryption is used to protect API keys stored in a SQLite database. This authenticated encryption algorithm ensures that trading credentials remain secure at rest and are only accessible via environment variable keys.

Can I use environment variables to manage encryption keys for trading API credentials?

Yes, environment variables are utilized to manage encryption keys for trading API credentials. This separates the encryption key from the stored data in the SQLite database, ensuring credentials cannot be decrypted without the environment variable.