Agent skills

Install with your AI agent

Copy this request and paste it into an AI chat that can download files and install Agent Skills:

Install all three BroSettlement Agent Skills from https://github.com/BroLabel/brosettlement-agent-skills.

Clone or download the repository and inspect all three `SKILL.md` files and the bundled scripts. Ask me which skills directory this AI agent supports, then install `brosettlement-onboarding`, `brosettlement-api`, and `brosettlement-disaster-recovery` as sibling folders without overwriting existing skills. Do not run BroSettlement setup or expose credentials during installation. Reload or rediscover skills if required, then verify that all three skills are available.

After installation, activate `$brosettlement-onboarding` and guide me through configuring a new BroSettlement organization. If automatic installation is not supported, tell me the exact destination directory and the next action instead of claiming that installation succeeded.

The prompt installs all three skills from the public GitHub repository. During onboarding, the Onboarding skill uses the API skill to inspect the current Swagger contract, send signed API requests, initialize MPC, and verify remote statuses. The Disaster Recovery skill remains separate and is activated only for a controlled Share B + Share C recovery ceremony.

Three skills, one repository

BroSettlement Onboarding

Installed by the prompt above from the public BroSettlement Agent Skills repository.

This skill turns the Quickstart into an interactive setup assistant. It keeps track of progress, asks only questions that require user input, explains why each stage matters, and continues automatically through safe tutorial steps.

What it can do

• Check whether you already have a BroSettlement account and organization access. If not, it explains what must be completed before technical setup can continue.
• Ask which folder should contain the Co-Signer and inspect the selected location before creating or changing files.
• Check required software, host access, and permissions without asking for the user's public IP. For temporary testnet onboarding, explain that 0.0.0.0/0 accepts any IPv4 source and bypasses the IP restriction; require the correct narrow public egress IP or CIDR for production.
• Generate the required Ed25519 key pair without overwriting an existing key and keep the private key out of chat.
• Give exact manual instructions for creating an API key in BroSettlement Console with Initialize MPC, Read MPC, and Raw MPC co-signer; the user always creates the key, and the skill never operates the API Keys UI.
• Install the Co-Signer, prepare its configuration, run validation or build checks, and start the service.
• Verify both sides of the connection: the local health endpoint and the Online status in BroSettlement Console.
• Use the companion BroSettlement API skill for signed REST calls, live Swagger inspection, and remote status checks.
• Start MPC/DKG through the API skill only after the Co-Signer is healthy, then monitor GET /api/v1/mpc/status until completion or an actionable error.
• Continue through the first-use flow without redundant confirmation prompts: the onboarding request authorizes one testnet ledger account and one linked wallet.
• Verify each created resource by ID, explicitly report successful creation, show the sanitized API response and useful identifiers, and explain how to list all accounts or wallets with the CLI or find them under Accounts and Wallets in Console.
• Finish by listing the exact current paths and purposes of the API private keys, share-encryption key, encrypted MPC shares, and related configuration without copying or displaying secrets. It explains that the same shares and matching encryption key are required to move the Co-Signer to production infrastructure without losing signing access to previously created wallets, then stops without offering recurring monitoring or automation.

Example requests

Use $brosettlement-onboarding to configure a new BroSettlement organization.

Continue my BroSettlement setup. The Co-Signer is installed, but Console shows it as Offline.

Help me initialize MPC and create the first testnet wallet.

Guardrails

The skill does not ask you to paste private keys, API secrets, or recovery material into chat. It does not overwrite keys or configuration silently, does not initialize MPC before health checks pass, and keeps the first wallet flow on testnet unless you explicitly request and confirm a production operation.

BroSettlement API

Installed by the prompt above from the public BroSettlement Agent Skills repository.

This skill helps an agent work from the live integration contract instead of relying on a static command list. It uses the production Swagger UI by default.

What it can do

• Download and inspect the current OpenAPI document before implementing a request.
• List all available commands or search them by operation name, path, HTTP method, tag, or free-text query.
• Explain request and response schemas, required headers, authentication requirements, permissions, parameters, and common API errors.
• Reuse an existing key through its API Key ID and protected local PEM path, or provide manual Console instructions when the user must create a new key; the skill never asks for JWT, TOTP, passwords, or private-key contents.
• Build and send Ed25519-signed REST requests using the exact request bytes used to calculate the signature.
• Run API discovery, signed REST calls, MPC status and initialization, and WebSocket listening through one guarded brosettlement Go CLI.
• Check for a newer verified CLI release at the beginning of each API-skill request and update only the compiled executable, without changing either installed skill.
• Preserve raw query strings and the current six-line canonical format, handle body hashing, request timestamps, and idempotency requirements without exposing the private key.
• Validate authentication with a read-only probe, show a redacted mutation plan, request confirmation, then verify the resulting resource or lifecycle.
• Connect to BroSettlement WebSocket, authenticate the session, print or save events as JSON Lines, and reconnect with backoff when the connection drops.
• Diagnose signature failures, revoked or invalid API keys, missing permissions, schema validation errors, and WebSocket authentication problems.
• Help reconcile WebSocket events with REST resources and the BroSettlement operational ledger.

Bundled tools

The bundled source build requires Go 1.24 or later. At the start of each request, the API skill checks GitHub Releases for a newer compatible CLI and verifies checksums.txt before replacing the executable. SKILL.md, references, scripts, and the sibling skill are never changed by this update. If the check cannot complete, the installed CLI remains available. The previous separate Go entry points remain available for compatibility.

CLI examples

Copy these commands into the AI chat after installing the skills. The agent resolves @brosettlement to the verified bundled CLI:

# Full command list
@brosettlement commands

# Search by topic
@brosettlement commands wallets
@brosettlement commands "ledger balance" --json

# Signed REST request
@brosettlement api GET '/api/v1/wallets'

# MPC status
@brosettlement mpc status

# WebSocket
@brosettlement websocket listen --stop-after 30s

Example requests

Use $brosettlement-api to list all wallet-related API commands.

Find the Swagger operation for creating a transaction and show its request body.

Create a signed Go request for this endpoint and explain which environment variables I must provide.

Start a WebSocket listener, reconnect on disconnect, and save events to a JSONL file.

Guardrails

The skill treats Swagger as the source of truth and uses the documented API endpoint. Credentials are read at runtime from approved environment variables or secret storage. API-key creation and management remain user-only. It avoids logging private keys, passwords, JWTs, TOTP codes, signed WebSocket URLs, or full secrets and asks for confirmation before any request that could create, move, or change real assets.

What is inside

The public repository contains three portable sibling skill folders:

brosettlement-onboarding/
├── SKILL.md
├── references/
└── agents/
brosettlement-api/
├── SKILL.md
├── references/
├── scripts/
└── agents/
brosettlement-disaster-recovery/
├── SKILL.md
├── references/
├── scripts/
└── agents/

Each SKILL.md is a cross-agent entry point. The Onboarding skill expects the API skill as its sibling and delegates signed API operations and status verification to it. The Disaster Recovery skill is a separate break-glass workflow with a source-only Go CLI. The references directories contain detailed context loaded only when needed.

Install in a skills-compatible agent

1. Review the public repository and all three SKILL.md files.
2. Clone https://github.com/BroLabel/brosettlement-agent-skills.git.
3. Run ./install.sh --target /absolute/path/to/agent-skills with the skills directory supported by your agent. The installer refuses to overwrite existing skills.
4. Restart or reload the agent so it discovers all three skills.
5. Invoke each skill explicitly once to verify installation:

Use $brosettlement-onboarding to help me configure a new BroSettlement organization.

Use $brosettlement-api to implement a signed request for the BroSettlement API.

Use $brosettlement-disaster-recovery to explain the prerequisites for a Share B + Share C TRON recovery transfer.

Your agent may also activate a skill automatically when a request matches its description.

Update or uninstall

Installations created by the repository helper can be updated only while their tracked files remain unchanged:

./install.sh --target /absolute/path/to/agent-skills --update

Preview the exact directories selected for removal, then repeat with explicit confirmation:

./uninstall.sh --target /absolute/path/to/agent-skills --all
./uninstall.sh --target /absolute/path/to/agent-skills --all --confirm

Use --skill brosettlement-onboarding, --skill brosettlement-api, or --skill brosettlement-disaster-recovery instead of --all to remove one skill. The helper refuses unrecognized installations and modified files. Never ask an AI agent to force-remove a modified skill until you have reviewed those changes.

Agents without native skill support

Open SKILL.md and provide it to the agent as project instructions or knowledge. Keep the relative references/ and scripts/ paths together so the agent can access the bundled resources.

Open format

The packages follow the Agent Skills specification: a folder with a required SKILL.md file and optional scripts, references, and assets.