Command reference

The commands below are what the CLI exposes for your editor's skills and your CI jobs to call. Most of the time the agent in your editor or your CI workflow handles these for you. It's useful to know what's available when you're building a custom skill or workflow.

Query your data

You query by picking metrics, dimensions, and filters from a dataset: there's no query language to write. Start by listing what's available, describe a dataset to see its fields, then run a query. Add --json to any read command for pipeable output.

buron datasets list
buron datasets describe gsc-queries

# Top search queries by clicks, last 30 days
buron datasets query gsc-queries \
  -m clicks,impressions -d query \
  --from 2026-06-10 --to 2026-07-10 --sort clicks:desc --limit 10

Filters are field:op:value (repeatable); the legal operators for each field come from datasets describe. For a complex query, pass the whole thing as JSON with --spec:

echo '{"measures":["cost"],"dimensions":["campaign_name"]}' \
  | buron datasets query cross-channel-ads --spec - --json

Save a query for reuse, run it later, or add it to a dashboard:

buron queries create "Top queries, 30d" --spec ./query.json
buron queries list --dataset gsc-queries
buron queries run <id>
buron dashboards add <dashboardId> <queryId>

When no dataset covers the question, buron gaql "<query>" runs a read-only GAQL statement against your live Google Ads account. It's built for config reads the datasets don't cover: bidding strategies, conversion actions, ad approval status.

buron gaql "SELECT campaign.name, campaign.bidding_strategy_type FROM campaign WHERE campaign.status = 'ENABLED'"

# Target one account in an MCC; omit --customer to fan out across every enabled account
buron gaql --customer 1234567890 "SELECT campaign.name, metrics.cost FROM campaign WHERE segments.date DURING LAST_30_DAYS"

Read a file

Print the contents of a file:

buron file read /wiki/company.md

Write a file

Write content from another source:

echo "# Q2 recap" | buron file write /wiki/analyses/q2-recap.md

Or from a local file:

buron file write /ads/google/reports/today.md --from-file /tmp/report.md

If the file already exists, this overwrites it. To add to a file instead, use buron file append with the same syntax.

Find a file

Search by name pattern:

buron file glob "/wiki/**/*.md"

Or search by content inside a folder:

buron file grep "Loopio" --directory /wiki/entities/

Edit a file

For one-off text changes, buron file replace is faster than rewriting the whole file:

buron file replace /wiki/team.md -o "old text" -n "new text"

Move or delete a file

Rename or move:

buron file move /wiki/old.md /wiki/new.md

Delete:

buron file delete /wiki/old.md

Deletes can't be undone. To be safe, move things you're unsure about into an archive folder instead.

Manage CI tokens

Mint, inspect, and revoke the tokens CI jobs use as BURON_TOKEN:

buron token create
buron token list
buron token revoke <id>

The created token is shown exactly once. See Run Buron from CI for the full workflow.

Update editor skills

Buron's skills install through the open agent-skills ecosystem, so updates come from the same tool:

npx skills update