メニュー
Find recent errors in a Lensflare dataset and summarise their root cause. Use when the user asks "what's broken", "what errors are happening", or pastes a vague stack trace and wants the actual failure context from the running system.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure. Use when the user pastes a trace id, asks "why is this slow", or wants a request-level post-mortem of a real production / dev request captured in Lensflare.
Translate a natural-language question about logs or telemetry into a Lensflare query and return the results. Use when the user asks "find logs that…", "show me…", or describes a filter in prose that should map to a structured query.
| name | find-error |
| description | Find recent errors in a Lensflare dataset and summarise their root cause. Use when the user asks "what's broken", "what errors are happening", or pastes a vague stack trace and wants the actual failure context from the running system. |
You have access to the Lensflare MCP server (lensflare).
lensflare:listDatasets if the user has not specified one. If exactly one dataset exists, use it. Otherwise, ask the user which to query.lensflare:queryTelemetry with query: 'level in ["error", "fatal"] or status = "error"'. Use limit: 50 unless the user asked for more.name (for spans) or message (for logs) to find the dominant failure mode.traceId, call lensflare:getTrace and read summary.erroredSpans to identify the failing span.traceId so the user can open the trace in the desktop app.Query language reminder. Use ~= for regex, contains for substring, and quote string values. Boolean operators are and / or / not. Top-level fields include level, status, serviceName, traceId, durationUs. Attributes use attributes.<key> (or attr.<key>). The full grammar is in the queryTelemetry tool description.