Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From lensflare-desktop
Queries Lensflare datasets for recent errors and fatals, groups by frequency, fetches traces, and summarizes root causes with failing spans and services. Use for 'what's broken' or vague stack traces.
npx claudepluginhub voidhashcom/lensflare --plugin lensflare-desktopHow this skill is triggered — by the user, by Claude, or both
Slash command
/lensflare-desktop:find-errorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have access to the Lensflare MCP server (`lensflare`).
Searches logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes for debugging distributed issues.
Analyzes Lensflare traces span-by-span, explaining timing, errors, and parent/child structure. Use for debugging slow requests, error post-mortems, or production traces via trace ID.
Lists recent unresolved errors from a Faultline instance and prompts the user to investigate a specific error group.
Share bugs, ideas, or general feedback.
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.