Agent skill

Find Error

by voidhashcom in voidhashcom/lensflare

Find recent errors in a Lensflare dataset and summarise their root cause.

MITAuto-check passedDevelopment

Install Find Error

skills CLI
$ npx skills add voidhashcom/lensflare --skill find-error -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install voidhashcom/lensflare find-error --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/voidhashcom/lensflare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/lensflare-desktop/skills/find-error .claude/skills/find-error && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
find-error
GitHub stars
100
Token cost
~355 tokens
SKILL.md length
168 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Find recent errors in a Lensflare dataset and summarise their root cause.

  • Works in 5 steps: Call lensflare:listDatasets if the user… → Call lensflare:queryTelemetry with… → Group the returned records by name (for… → …
  • The user asks whats broken
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • What errors are happening

What it does

Find Error is an agent skill from voidhashcom/lensflare. 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.

Its SKILL.md is about 360 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging and Root cause analysis. The licence is MIT.

When your agent uses it

  • The user asks whats broken
  • What errors are happening
  • Pastes a vague stack trace and wants the actual failure context from the running system

Example prompts

  • “s broken”
  • “what errors are happening”
  • “/find-error”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Call lensflare:listDatasets if the user has not specified one. If exactly one dataset exists, use it. Otherwise, ask the user which to…
  2. Call lensflare:queryTelemetry with query: 'level in ["error", "fatal"] or status = "error"'. Use limit: 50 unless the user asked for more.
  3. Group the returned records by name (for spans) or message (for logs) to find the dominant failure mode.
  4. For the most frequent error, if it has a traceId, call lensflare:getTrace and read summary.erroredSpans to identify the failing span.
  5. Report: the error class, frequency, the failing service, and the first failing span. Include the traceId so the user can open the trace in…

What it can do on your machine

Read from SKILL.md and the folder at commit 77af210. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Find Error loads about 355 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 168 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~355

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from voidhashcom/lensflare at commit 77af210, republished under its MIT licence (© voidhashcom). 168 words, ~355 tokens.

Download SKILL.mdSave it as .claude/skills/find-error/SKILL.md (or your agent's skills folder).
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.

Find an error in Lensflare

You have access to the Lensflare MCP server (lensflare).

  1. Call lensflare:listDatasets if the user has not specified one. If exactly one dataset exists, use it. Otherwise, ask the user which to query.
  2. Call lensflare:queryTelemetry with query: 'level in ["error", "fatal"] or status = "error"'. Use limit: 50 unless the user asked for more.
  3. Group the returned records by name (for spans) or message (for logs) to find the dominant failure mode.
  4. For the most frequent error, if it has a traceId, call lensflare:getTrace and read summary.erroredSpans to identify the failing span.
  5. Report: the error class, frequency, the failing service, and the first failing span. Include the 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.

© voidhashcom, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/lensflare-desktop/skills/find-error of voidhashcom/lensflare.

Open the folder on GitHubat commit 77af210

Compare with similar skills

Find Error next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Find Error compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Find Error this skillvoidhashcom/lensflare100—~355Automated safety check: PassMIT
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Graph-Based Bug Tracingtirth8205/code-review-graph32k1 repos~287Automated safety check: PassMIT
Systematic DebuggingChrisWiles/claude-code-showcase6.1k3 repos~1.2kAutomated safety check: PassNone

Similar skills

  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 3 days ago
    DevelopmentAuto-check: notes
  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed
  • Systematic Debugging

    ChrisWiles/claude-code-showcase

    Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.

    6.1k GitHub starsUsed in 3 repos~1.2k tokens
    DevelopmentAuto-check passed
  • Debugging and Error Recovery

    addyosmani/agent-skills

    Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.

    102k GitHub starsUsed in 1 repo~2.6k tokens
    DevelopmentAuto-check passed

More from voidhashcom/lensflare

  • Analyze Trace

    voidhashcom/lensflare

    Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure.

    100 GitHub stars~340 tokensUpdated 3 mo ago
    Auto-check passed
  • Query Logs

    voidhashcom/lensflare

    Translate a natural-language question about logs or telemetry into a Lensflare query and return the results.

    100 GitHub stars~366 tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about Find Error

What does Find Error do?

Find recent errors in a Lensflare dataset and summarise their root cause. Find Error is an agent skill from voidhashcom/lensflare. Find recent errors in a Lensflare dataset and summarise their root cause.

When should I use Find Error?

Find Error fits situations like: the user asks whats broken; what errors are happening; pastes a vague stack trace and wants the actual failure context from the running system.

How do I install Find Error in Claude Code?

Run `npx skills add voidhashcom/lensflare --skill find-error -a claude-code`. Or copy the skill folder (plugins/lensflare-desktop/skills/find-error in voidhashcom/lensflare) into .claude/skills/find-error in your project. Claude Code loads it when a task matches its description.

How do I install Find Error in Codex?

Run `npx skills add voidhashcom/lensflare --skill find-error -a codex`. Or copy the skill folder (plugins/lensflare-desktop/skills/find-error in voidhashcom/lensflare) into .agents/skills/find-error in your project. Codex loads it when a task matches its description.

Can I use Find Error in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add voidhashcom/lensflare --skill find-error -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/find-error, .gemini/skills/find-error, .github/skills/find-error and .opencode/skills/find-error in your project.

What does Find Error need to run?

SKILL.md names no scripts, command-line tools or credentials: Find Error is instructions for the agent only.

Does Find Error access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Find Error safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Find Error use?

Find Error is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Find Error use?

About 355 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Find Error?

Skills that share tags, products or a category with Find Error: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Graph-Based Bug Tracing (tirth8205/code-review-graph, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Find Error?

voidhashcom (a GitHub organization) maintains it in voidhashcom/lensflare, which has 100 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on June 25, 2026.

Source: voidhashcom/lensflare on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.