ClaudeSuperPower

create-honeycomb-board

Skill

Design and then create a board (dashboard) in Honeycomb with queries and SLOs. Trigger phrases: "create a board", "make a board", "build a dashboard", "create a Honeycomb board", "make a dashboard in Honeycomb", "set up a board", "dashboard for my service", "visualize service health", "golden signal

Install

git clone https://github.com/honeycombio/agent-skill.git ~/.claude/skills/create-honeycomb-board

What is create-honeycomb-board?

Design and then create a board (dashboard) in Honeycomb with queries and SLOs. Trigger phrases: "create a board", "make a board", "build a dashboard", "create a Honeycomb board", "make a dashboard in Honeycomb", "set up a board", "dashboard for my service", "visualize service health", "golden signals dashboard", "set up monitoring board", or any request to design and create or build a Honeycomb board or dashboard.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Read files only

Read-only tools

~104 tokens of context used while enabled, before you invoke anything

All declared tools (16)
AskUserQuestionGlobGrepReadmcp__honeycomb__create_boardmcp__honeycomb__find_columnsmcp__honeycomb__find_queriesmcp__honeycomb__get_datasetmcp__honeycomb__get_dataset_columnsmcp__honeycomb__get_environmentmcp__honeycomb__get_query_resultsmcp__honeycomb__get_slosmcp__honeycomb__get_triggersmcp__honeycomb__get_workspace_contextmcp__honeycomb__list_boardsmcp__honeycomb__run_query

Documentation

README · ~4 min read

Create a Honeycomb Board

Build a board (dashboard) in Honeycomb using the create_board MCP tool. There is no update tool — define it well before creating.

When building a board, think about the purpose and time frame involved. Some examples:

  • a board for a service. This should be timeless, looking at the service's health, performance, and business metrics. Do not do any problem diagnosis or investigation when building this board. Do not express opinions or summarize graphs in text panels. The board should be a representation of the service's health at whatever moment someone looks at it.
  • a board for a feature. This should look at the feature's usage trends, and its impact on the business. This board would have a time frame of 7 days, and would not include any infrastructure metrics or service dependencies.
  • a board for a problem. This might be created during an incident, or afterward. This one would have a time frame specific to the incident. It would include investigations, and your opinions about what is happening. Patterns of what to look for are appropriate here.

Workflow

Gather SLOs

Use get_slos to list SLOs in the environment. Relevant SLOs will go on the board as slo panels.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills