Honeycomb agent skills for Claude Code, Cursor and RevampKey

3 ready-made playbooks that teach an AI agent how to do real Honeycomb work: which tools to call, what to check first, and when to stop and ask you.

Download RevampKey, free I have it: connect Honeycomb

Connect Honeycomb once and all 3 skills install themselves and stay up to date. Mac, Windows and Linux.

All 3 Honeycomb skills

Each skill is one job. You ask in plain words and the agent loads the skill that matches, then follows its steps.

Start hereRead-only13 Honeycomb tools

Use Honeycomb with AI agents, safely

Teaches an agent to confirm the team, environment and dataset before querying, choose the right read tool, keep results small, and ask before any change. It does not modify Honeycomb without your approval.

Use it when

You are connecting Honeycomb to an AI agent for the first time.
You want to know which environment and dataset an agent is querying.
You need to stop an agent from making changes to boards, triggers or SLOs without asking.

Tools it uses

get_team_info
list_environments
list_datasets
get_environment
search_columns
get_dataset_columns
get_trace
run_unsaved_query
get_query_history
get_slos
get_triggers
get_dataset
feedback

Example

Before you investigate anything, check which Honeycomb environment and dataset you are looking at, and tell me what you can see.

You are connected to team Acme, with 2 environments: production and staging. Your api-gateway data is in the production environment, dataset api-gateway, which has 14 columns including duration_ms and status_code. I have not changed anything. Tell me the time window and I will run a read-only query.

Use in RevampKeyRead the full skill →

Read-only12 Honeycomb tools

Investigate a latency or error spike with AI

Traces a Honeycomb latency or error spike to a specific segment, comparing it against a baseline and checking a trace from inside the window. It reads your data and does not change triggers, SLOs or Boards without asking.

Use it when

Latency jumped at 14:20 and you need to know which route is responsible
Error count doubled after a release and you want to know which status or error type rose
A trigger fired and you need the segment behind it before paging anyone

Tools it uses

get_environment
list_environments
list_datasets
get_dataset
get_team_info
get_triggers
get_slos
search_columns
get_dataset_columns
run_unsaved_query
get_trace
get_query_history

Example

Investigate the latency spike in the checkout dataset between 14:10 and 14:40 today, and tell me which route is responsible.

Scope: production environment, checkout dataset, spike 14:10 to 14:40 against a baseline of 13:40 to 14:10. p99 latency on /api/checkout rose from 310 ms to 1,840 ms, while the other four routes stayed flat. Within that route, 92% of the slow requests call the payments-gateway span. One trace from 14:22 shows that span taking 1.6 s. Hypothesis: the payments gateway slowed for one region, confidence medium, since the regional split is not yet checked.

Use in RevampKeyRead the full skill →

Read-only11 Honeycomb tools

Review Honeycomb SLO and trigger coverage

Audits your Honeycomb SLOs and triggers against the services that matter, finding unguarded services, dead or noisy alerts, and stale conditions. It proposes a prioritised fix list and asks before changing anything.

Use it when

You want to know which critical services have no alert or SLO
Your team gets too many alerts and you want the noisy ones found
An alert never fires and you suspect its threshold or attribute is stale

Tools it uses

get_environment
get_team_info
list_datasets
get_slos
get_triggers
get_dataset
get_dataset_columns
run_unsaved_query
get_query_history
search_columns
get_trace

Example

Review our Honeycomb SLOs and triggers for the checkout services and tell me what isn't covered.

Checkout has an availability SLO and an error trigger, but payment-retry has neither. The latency trigger on api-gateway is true for about 40% of normal hours, so it is noisy. Proposed: add an error-rate trigger on payment-retry, and change the gateway trigger to a baseline. I have changed nothing; say yes to apply either one.

Use in RevampKeyRead the full skill →

Get all 3 without copying a file

RevampKey adds the skills when you connect Honeycomb, updates them for you and removes them when you disconnect.

Download RevampKey

How Honeycomb skills work

Connect Honeycomb
The Honeycomb MCP server gives the agent its tools.
Ask in plain words
“Investigate the latency spike in the checkout dataset between 14:10 and 14:40 today, and tell me which route is responsible.” Each SKILL.md says when it applies, so only the one that fits is loaded.
Approve any change
The agent calls the tools in order, checks its work, and shows you any change before it makes it.

How to install Honeycomb skills

In RevampKey the skills install themselves when you connect Honeycomb. In other tools each skill is one folder with a SKILL.md file, and you also need the Honeycomb MCP server connected there.

About 1 minute · nothing to copy

Download RevampKey for Mac, Windows or Linux and sign in.
Open Connectors and connect Honeycomb. All 3 skills come with it and stay up to date; they go away when you remove the connector.
Ask in plain language, for example “Investigate the latency spike in the checkout dataset between 14:10 and 14:40 today, and tell me which route is responsible.”
Download RevampKeyConnect Honeycomb · 1 click
Get RevampKey to connect Honeycomb
RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and Honeycomb is one click away with its skills already attached.
Download RevampKey
Not now? Use the skills in your current tool
for s in essentials investigate-latency-or-error-spike review-slo-and-trigger-coverage; do curl -fsSL --create-dirs -o .claude/skills/honeycomb-$s/SKILL.md https://revampkey.com/marketplace/honeycomb/skills/$s/SKILL.md done
Other tools

Into this project’s .claude/skills folder

Connect the Honeycomb MCP server in Claude Code.

Run this in your project folder to add all 3 skills:

for s in essentials investigate-latency-or-error-spike review-slo-and-trigger-coverage; do
  curl -fsSL --create-dirs -o .claude/skills/honeycomb-$s/SKILL.md https://revampkey.com/marketplace/honeycomb/skills/$s/SKILL.md
done

Ask in plain language, for example “Investigate the latency spike in the checkout dataset between 14:10 and 14:40 today, and tell me which route is responsible.”

Into the shared .agents/skills folder

Connect the Honeycomb MCP server in Cursor.

Run this in your project folder to add all 3 skills:

for s in essentials investigate-latency-or-error-spike review-slo-and-trigger-coverage; do
  curl -fsSL --create-dirs -o .agents/skills/honeycomb-$s/SKILL.md https://revampkey.com/marketplace/honeycomb/skills/$s/SKILL.md
done

Ask in plain language, for example “Investigate the latency spike in the checkout dataset between 14:10 and 14:40 today, and tell me which route is responsible.”

Into the shared .agents/skills folder

Connect the Honeycomb MCP server in Codex.

Run this in your project folder to add all 3 skills:

for s in essentials investigate-latency-or-error-spike review-slo-and-trigger-coverage; do
  curl -fsSL --create-dirs -o .agents/skills/honeycomb-$s/SKILL.md https://revampkey.com/marketplace/honeycomb/skills/$s/SKILL.md
done

Ask in plain language, for example “Investigate the latency spike in the checkout dataset between 14:10 and 14:40 today, and tell me which route is responsible.”

Into the shared .agents/skills folder

Connect the Honeycomb MCP server in VS Code.

Run this in your project folder to add all 3 skills:

for s in essentials investigate-latency-or-error-spike review-slo-and-trigger-coverage; do
  curl -fsSL --create-dirs -o .agents/skills/honeycomb-$s/SKILL.md https://revampkey.com/marketplace/honeycomb/skills/$s/SKILL.md
done

Ask in plain language, for example “Investigate the latency spike in the checkout dataset between 14:10 and 14:40 today, and tell me which route is responsible.”

RevampKey or copy the files?

In RevampKey

One click when you connect Honeycomb
Updated for you when a skill improves
Removed when you disconnect
The MCP server is set up for you
800+ other connectors, same way

Download free

Copy into your project

One command per project
Run it again to get updates
You connect the Honeycomb MCP server yourself
Works in Claude Code, Cursor, Codex and VS Code

See the command

Honeycomb skills FAQ

What is a Honeycomb agent skill?

A SKILL.md file: a short playbook an AI agent loads when your request matches it. Each Honeycomb skill describes one job, which Honeycomb tools to use in which order, what to check first and when to stop and ask you.

Do the Honeycomb skills change anything on their own?

3 of the 3 only read. The others tell the agent to show you the change and wait for a yes before it creates, edits or deletes anything in Honeycomb.

Which tools can use these skills?

Any agent that reads the open Agent Skills format: Claude Code, Cursor, Codex, VS Code with Copilot and RevampKey. In RevampKey they are attached when you connect Honeycomb; elsewhere you copy the folders into your project or skills directory.

Do I need the Honeycomb MCP server too?

Yes. The skills tell the agent how to do the work; the Honeycomb MCP server gives it the tools to do it. The Honeycomb MCP setup guide covers every client.

Honeycomb MCP server setup · This page as Markdown

Put Honeycomb’s best workflows in your agent

Download RevampKey, connect Honeycomb and ask your first question in about a minute.

Download RevampKey Connect Honeycomb · 1 click

All 3 Honeycomb skills

Use Honeycomb with AI agents, safely

Use it when

Tools it uses

Investigate a latency or error spike with AI

Use it when

Tools it uses

Review Honeycomb SLO and trigger coverage

Use it when

Tools it uses

Get all 3 without copying a file

How Honeycomb skills work

How to install Honeycomb skills

RevampKey or copy the files?

In RevampKey

Copy into your project

Honeycomb skills FAQ

Put Honeycomb’s best workflows in your agent

Skills for related tools