Update to Honeycomb

{
  "name": "verify-recent-trace",
  "description": "Find a recent trace in Honeycomb, to see what happened in a recent test. Use when asked to \"verify in Honeycomb\", \"find the most recent trace\", or \"show me the trace\".\n",
  "included_files": [],
  "skill_md_contents": "---\nname: verify-recent-trace\ndescription: >\n  Find a recent trace in Honeycomb, to see what happened in a recent test. Use when asked to \"verify in Honeycomb\", \"find the most recent trace\", or \"show me the trace\".\nmetadata:\n  version: \"1.0.0\"\nallowed-tools:\n  - mcp__honeycomb__run_query\n  - mcp__honeycomb__get_trace\n  - mcp__honeycomb__get_query_results\n  - mcp__honeycomb__find_queries\n  - Read\n---\n\n# Honeycomb Verification Skill\n\n## Purpose\n\nQuery Honeycomb to find the traces that were created by a recent test.\n\n## When to Use\n\nThis skill is automatically activated when:\n\n- User asks to \"show me a trace in Honeycomb\"\n- Completing an implementation step that requires observability verification\n\n## Verification Output\n\nReport query results as:\nQueried [VIZ] where [FILTERS] by [GROUP_BY] over [TIME_RANGE]\nResults: [link to Honeycomb query]\n\n## Query Patterns\n\n- **Time Range**: 1200 seconds (20 minutes) - adjustable based on when the test started\n\n### Pattern 1: Get a particular trace\n\nWhat service are you testing? This determines the dataset.\nDo you know the name of the span you expect to see?\n\n```\nQuery for:\n- dataset: [dataset]\n- filter: name = [expected span name]\n- time_range: [calculated time range]\n- calculation: COUNT\n- include_samples: true\n```\n\nNow take the most recent sample, and use get_trace to get the full trace.\nOutput:\n\nQueried [CALCULATION] where [FILTERS] over [TIME_RANGE]\nFound [count] results\nResults: [link to the query]\n\nMost recent trace: [link to the trace]\nRoot span: [root span name]\nTotal spans: [count of spans]\nServices: [list of services]\n\n### Pattern 2: Find all traces since the test started\n\n```\nQuery for:\n- all datasets\n- filter: trace.parent_id does-not-exist\n- time_range: [calculated time range]\n- calculation: COUNT\n- breakdowns: name\n- include_samples: true\n```\n\nOutput:\nQueried [CALCULATION] where [FILTERS] by [BREAKDOWNS] over [TIME_RANGE]\nFound [count] results\nResults: [link to the query]\n\nFor each sample, print:\n\n- Trace ID\n- Span name\n- anything else it gives you\n  Construct a link to the trace in Honeycomb, according to:\n  https://ui.honeycomb.io/modernity/environments/personal-agent/trace?trace_id=[<traceId>]\n  &trace_start_ts=[test_start_time]\n  &trace_end_ts=[((date +%s))]\n\n### Pattern 3: Find the most recent trace, precisely\n\n```\nQuery for:\n  calculated_fields: event_time=EVENT_TIMESTAMP()\n  calculation: COUNT\n  breakdowns: event_time, trace.trace_id\n  order: event_time DESC\n  limit: 1\n  include_samples: false\n```\n\nPrint the summary of the trace, as in Pattern 1.\n\nTake the output trace_id and use get_trace to get the full trace.\n\n### Pattern 4: When you don't see any traces, try: Get the time range right\n\nBefore running a test that will generate a trace, print the current time.\n\nstart_time=$(date +%s)\n\nThen run the test to create the trace.\n\nThen calculate the correct time range:\n\necho $(( $(date +%s) - $start_time + 20))\n\nInclude that in the query you're using to find traces.\n"
}