Skip to content

chore(skills): cover standards CLI + deploy --with-keyring / --wait-for-indexer#4

Merged
trevormil merged 2 commits into
masterfrom
chore/skills-standards-and-deploy-paths
May 14, 2026
Merged

chore(skills): cover standards CLI + deploy --with-keyring / --wait-for-indexer#4
trevormil merged 2 commits into
masterfrom
chore/skills-standards-and-deploy-paths

Conversation

@trevormil

Copy link
Copy Markdown
Contributor

Summary

Two skill updates so Claude reaches for the right tool when a user asks about a BitBadges standard by name or wants a headless CLI broadcast.

`query/SKILL.md`

  • Description lists the standards surface (auctions / crowdfunds / payment-requests / intents / smart-tokens / ...) — the skill now surfaces for standard-named questions, not just raw API ones.
  • New "Standards shortcuts (preferred over raw API)" section: example commands per standard.
  • API route count 104+ → 106+ (SDK #223 routes.yaml drift fix + #228 gamm chain-query client).

`broadcast/SKILL.md`

  • Fifth signing path: `deploy --with-keyring --from ` (SDK #226). Best for headless CLI flows that have a chain-binary key already imported.
  • Top-level note on `--wait-for-indexer [timeout-ms]` (SDK #227). Lets agent scripts immediately query the new entity.

`CHANGELOG.md`

Both entries added under [Unreleased] > Changed.

Test plan

  • Markdown renders
  • Cross-refs to docs page (`bitbadges-cli list / show / status`) match the surface that just shipped on bitbadgesjs main

trevormil and others added 2 commits May 13, 2026 21:25
…-indexer

The CLI surface that landed in bitbadgesjs #225–#228 + #220–#222 isn't
documented in the agent skills yet. Two skill updates so Claude reaches
for the right tool when a user asks about a standard by name or wants a
headless CLI broadcast:

`query/SKILL.md`
  - Description: list the standards surface (auctions / crowdfunds /
    payment-requests / intents / smart-tokens / ...) so the skill is
    surfaced for standard-named questions, not just raw API ones.
  - New section "Standards shortcuts (preferred over raw API)": example
    commands per standard. The standards CLI is friendlier than
    grepping the indexer route registry — agents should default to it.
  - Bump API route count 104+ → 106+ (SDK #223 routes.yaml drift fix +
    #228 gamm chain-query client added 27+ routes).

`broadcast/SKILL.md`
  - Add a fifth signing path: `deploy --with-keyring --from <key>`
    (SDK #226). Best for headless CLI flows where the user already has
    a chain-binary key but doesn't want to context-switch out of
    bitbadges-cli to run bitbadgeschaind tx ... themselves.
  - Top-level note on `--wait-for-indexer [timeout-ms]` (SDK #227).
    Lets agent scripts immediately query the new entity instead of
    racing the indexer.

CHANGELOG.md updated with both changes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Skills mix `bitbadges-cli`, `bb cli`, and `bitbadgeschaind` in examples
without telling Claude when to use each. Adds a short rule-of-thumb
table to the README:

  - `bb cli <subcmd>` — preferred for everything in the JS SDK CLI
    surface (`build`, `deploy`, `api`, standards verbs, `auth`, etc).
    `bb cli` is `bitbadgeschaind cli` is `bitbadges-cli` — same code,
    friendlier alias.
  - `bitbadgeschaind tx | query | keys` — Cosmos chain-binary surface
    only. NOT forwarded through `bitbadges-cli`. Use when the broadcast
    skill needs the chain-binary signing path or the address skill needs
    keyring lookups.
  - `bitbadges-cli <subcmd>` — fallback for when the chain binary isn't
    on PATH; examples in skills standardize on `bb cli` for terseness.

Also flips the post-install setup example from `bitbadges-cli config set`
to `bb cli config set` so the README matches its own guidance.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@trevormil
trevormil merged commit 2785e38 into master May 14, 2026
1 check passed
@trevormil
trevormil deleted the chore/skills-standards-and-deploy-paths branch May 14, 2026 01:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant