DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find the real failures in a long log without reading every line with Quicksilver

Have Jev mark which log lines report a failure, then pass Claude the collapsed result.

Who it is forAn engineer or on-call agent facing a log file with thousands of lines who needs the real errors fast.

The problemReading a 3,000-line log line by line costs many Claude tokens and most lines are noise.

The outcomeClaude receives the failing lines with repeated patterns collapsed into line-number ranges; the benchmark's noisy service log task reached 100% F1 with 95% fewer Claude tokens.

What you need first

  • Claude Code installed
  • Node 18 or later
  • A Jev key from console.typesafe.ai
  • Content you are allowed to send to TypeSafe's API

Steps

  1. Get a Jev key at console.typesafe.ai and run npx github:UditAkhourii/quicksilver.
  2. Restart Claude Code so it can use the skill.
  3. Run qs filter "Does this line report a failure?" app.log --lines and replace app.log with your log file. (inferred, check the README)
  4. Check the receipt line at the end of the output for lines scanned, matches, and borderline items.
  5. Ask Claude to explain the matched line ranges, and review any ? lines by hand.

Prompt for your agent

Using the repo UditAkhourii/quicksilver, run qs filter with the question "Does this line report a failure?" and the --lines flag on <log-file>. Summarize the matched line ranges and their likely causes. Verify that the receipt line reports the number of lines scanned.

Caveat. Logs whose labels encode unwritten policy, like the BGL supercomputer log in the benchmark, scored poorly, so test on a sample before trusting the results.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page