hive-credentials
Set up and install credentials for an agent. Detects missing credentials from agent config, collects them from the user, and stores them securely in the local encrypted store at ~/.hive/credentials.
npx skills add majiayu000/claude-skill-registry --skill hive-credentials-aden-hive-hive --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Set up and install credentials for an agent. Detects missing credentials from agent config, collects them from the user, and stores them securely in the local encrypted store at ~/.hive/credentials.
How it works
- Identify the Agent: determine which agent needs credentials by name, an open agent directory, or current session, locating the agent's directory under exports/{agent_name}/.
- Detect Missing Credentials: run check_missing_credentials with agent_path="exports/{agent_name}" to obtain a JSON payload listing missing and available credentials. If ready is true, all credentials are configured; otherwise proceed to Step 3.
- Present Auth Options for Each Missing Credential: for each missing credential, inspect CREDENTIAL_SPECS to determine available auth methods (aden, direct, custom). Present options via AskUserQuestion listing Aden Platform (OAuth), Direct API Key, and Local Credential Setup (Advanced).
- Execute Auth Flow Based on User Choice: ensure HIVE_CREDENTIAL_KEY is available (session or shell config); if not set, EncryptedFileStorage will auto-generate one and instruct persisting it. Depending on choice:
- Option 1 Aden Platform (OAuth): check for ADEN_API_KEY, guide OAuth via Aden, persist ADEN_API_KEY to shell config, update ~/.hive/configuration.json, and call CredentialStore.with_aden_sync(...) to sync credentials from Aden.
- Option 2 Direct API Key: show setup instructions from CREDENTIAL_SPECS, securely collect the API key, health-check with check_credential_health, and store in the local encrypted store using CredentialStore and CredentialObject/CredentialKey. Optionally export to current session.
- Option 3 Local Credential Setup: show API, provide direct CredentialStore usage example for programmatic CI/CD setup.
- Record Configuration Method: write the chosen method for the credential into ~/.hive/configuration.json under credential_methods for the specific credential.
- Verify All Credentials: use verify_credentials agent_path="exports/{agent_name}" to confirm readiness; if missing credentials remain, loop back to Step 3.
When to use it
- Before running or testing an agent for the first time
- When
AgentRunner.run()fails with "missing required credentials" - When a user asks to configure credentials for an agent
- After building a new agent that uses tools requiring API keys
What it can touch
- Uses the encrypted local storage at ~/.hive/credentials
- Reads and writes to ~/.hive/configuration.json
- May modify shell config to persist HIVE_CREDENTIAL_KEY and ADEN_API_KEY per the flow
- Interacts with environment variables for API keys and Aden API key
Caveats
- Shell config can contain only two keys: HIVE_CREDENTIAL_KEY and ADEN_API_KEY; other credentials must remain in the encrypted store
- Credentials must be stored in the local encrypted store; do not store plaintext keys in files or agent configs
- Requires health checks before storing credentials where possible
- After generating or updating HIVE_CREDENTIAL_KEY, user should add it to shell profile and reopen a terminal
# Setup Credentials Interactive credential setup for agents with multiple authentication options. Detects what's missing, offers auth method choices, validates with health checks, and stores credentials securely. ## When to Use - Before running or testing an agent for the first time - When `AgentRunner.run()` fails with "missing required credentials" - When a user asks to configure credentials for an agent - After building a new agent that uses tools requiring API keys ## Workflow ### Step 1: Identify the Agent Determine which agent needs credentials. The user will either: - Name the agent directly (e.g., "set up credentials for hubspot-agent") - Have an agent directory open (check `exports/` for agent dirs) - Be working on an agent in the current session Locate the agent's directory under `exports/{agent_name}/`. ### Step 2: Detect Missing Credentials Use the `check_missing_credentials` MCP tool to detect what the agent needs and what's already configured. This tool loads the agent, inspects its required tools and node types, maps them to credentials via `CREDENTIAL_SPECS`, and checks both the encrypted store and environment variables. ``` check_missing_credentials(agent_path="exp
- When to Use
- Workflow
- Step 1: Identify the Agent
- Step 2: Detect Missing Credentials
- Step 3: Present Auth Options for Each Missing Credential
- Step 4: Execute Auth Flow Based on User Choice
- Step 5: Record Configuration Method
- Step 6: Verify All Credentials
- Health Check Reference
- Encryption Key (HIVECREDENTIALKEY)
- Security Rules
- Credential Sources Reference
- Migration: CredentialManager → CredentialStore
- Example Session
Check current session printenv HIVE_CREDENTIAL_KEY > /dev/null 2>&1 && echo "session: set" || echo "session: not set" Check shell config files for f in ~/.zshrc ~/.bashrc ~/.profile; do [ -f "$f" ] && grep -q 'HIVE_CREDENTIAL_KEY' "$f" && echo "$f"; done export HUBSPOT_ACCESS_TOKEN="the-value"
What does the hive-credentials skill do?
Set up and install credentials for an agent. Detects missing credentials from agent config, collects them from the user, and stores them securely in the local encrypted store at ~/.hive/credentials.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill hive-credentials-aden-hive-hive --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.