Honeycomb CLI and MCP server usage — auth, queries, datasets, SLOs, boards, triggers, markers, columns, and raw API requests for observability workflows
Manages Honeycomb observability workflows through CLI commands and MCP tools for queries, datasets, SLOs, and API requests.
npx claudepluginhub bendrucker/honeycomb-cliThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Three key types, stored in the OS keyring per profile:
| Type | Used For |
|---|---|
config | Management API (boards, SLOs, triggers, columns, queries) |
ingest | Sending events (X-Honeycomb-Team header) |
management | Same as config, kept separate for granular access |
honeycomb auth login # interactive key setup
honeycomb auth status # verify stored key
honeycomb auth status --offline # check keyring without API call
Requires a config key with query permissions.
# from a file
honeycomb query run --dataset my-dataset --file query.json
# from stdin
echo '{"calculations":[{"op":"COUNT"}],"time_range":3600}' | honeycomb query run --dataset my-dataset --file -
# list/view saved queries
honeycomb query annotation list --dataset my-dataset
honeycomb query annotation view <id> --dataset my-dataset
honeycomb api makes authenticated requests to any Honeycomb API endpoint. Useful for endpoints without dedicated subcommands (events, query results, service maps).
honeycomb api /1/events/my-dataset -X POST --input events.json --key-type ingest
honeycomb api /1/query_results/my-dataset/abc123 # poll query results
honeycomb api /1/maps/dependencies/requests -q '.results'
honeycomb api /2/teams -q '.[].name' --paginate # v2 with jq + pagination
Flags: -X method, -f string fields, -F typed fields, -H headers, -q jq filter, --paginate, --input body file, --key-type override, --raw skip JSON:API unwrapping (v2 paths).
| Flag | Purpose |
|---|---|
--format json|table | Output format (default: table in TTY, json in CI/agent) |
--profile | Configuration profile |
--no-interactive | Disable prompts |
--api-url | Override Honeycomb API URL |
list, get, create, update, delete subcommands--dataset for dataset-scoped resources (columns, markers, queries), --environment where applicableCLAUDE_CODE is set, the CLI forces --no-interactive and defaults to --format jsonauth, query, dataset, board, column, marker, slo, trigger, environment, key, recipient, mcp, apimcp SubcommandThis plugin configures the Honeycomb MCP server (.mcp.json) for direct tool access via OAuth. Use its tools (run_query, get_dataset_columns, find_columns) when you need query results in context.
The CLI's mcp subcommand is a separate MCP client that authenticates with a config key (Bearer token). Use it when you need to write MCP results to disk:
honeycomb mcp call run_query -f dataset=prod -q '.content[].text' > results.json
honeycomb mcp tools # list available MCP tools
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.