settings

Manage AIBTC settings in ~/.aibtc/config.json with subcommands.

9|43|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/aibtcdev/skills --skill settings-aibtcdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: settings
Source: https://github.com/aibtcdev/skills/tree/main/settings
Command: npx skills add https://github.com/aibtcdev/skills --skill settings-aibtcdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commander.

What problem does it solve?

Manage AIBTC configuration stored at ~/.aibtc/config.json, including Hiro API keys for authenticated requests, a custom Stacks API URL, and visibility into package version and relay health status.

Core Features & Use Cases

  • Configure Hiro API key for authenticated requests, enabling higher rate limits.
  • Point to a custom Stacks API node for development, testing, or privacy.
  • Check the current package version and diagnose sponsor relay health to ensure smooth operation.

Quick Start

Run bun run settings/settings.ts get-server-version to verify the installed version.

Frequently Asked Questions about settings

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

FAQPage Schema
How do I configure a Hiro API key for Stacks API requests?

Configure a Hiro API key by storing it in the ~/.aibtc/config.json file using the set-hiro-api-key command. This enables authenticated requests with higher rate limits, falling back to the HIRO_API_KEY environment variable if unset.

Can I point my Stacks CLI to a custom API node for development?

Point to a custom Stacks API node by running the set-stacks-api-url command to update your configuration file. This allows you to route requests to a custom endpoint for development, testing, or privacy.

How do I check the health of a Stacks sponsor relay?

Check sponsor relay health by running the check-relay-health subcommand. This diagnoses the operational status of your configured relay to ensure stable, uninterrupted API operations.

What is the best way to manage sensitive API keys for Stacks development?

Manage sensitive API keys centrally by storing them in the ~/.aibtc/config.json configuration file. You can securely set, retrieve, and delete keys using dedicated subcommands without exposing them in plain text.

Why does my Stacks API configuration need a local config.json file?

A local config.json file stores your Hiro API keys and custom Stacks API URL securely. The settings initialize this file automatically, ensuring persistent configuration across sessions for stable operations.