BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

usagetrim

Skill Development Usable
Works inClaude Code
Usable Scanned — metadata only

Reduces log noise from test and build tools, enabling teams to spot failures and bottlenecks faster without parsing gigabytes of output.

Fast local CLI and MCP tool for compacting verbose test runners and build output.

43 starsMIT (commercial OK)FreeQuick setup
Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

Reduces log noise from test and build tools, enabling teams to spot failures and bottlenecks faster without parsing gigabytes of output. Runs locally—no external dependencies or latency.

DevOps and platform engineers managing CI/CD pipelines with verbose test suites or builds generating overwhelming output.

Claude Code Claude Cowork Claude Chat

https://github.com/00200200/usagetrim

By 00200200

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → Plugins → Add plugin. Search and click Install. Skills work in Claude Code only.
Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.
Command
claude plugins install 00200200/usagetrim

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

After installing, paste this into Claude:

Help me compress lengthy test runner output to extract only failure summaries and errors
CostFree

Trust Signals Auto-scanned

Stars43Contributors8Last updated2026-10-25LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-10-27 · scanner v1

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 42 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

Things to check

  • Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
3/5
Versatility
2/5
Reliability
3/5
Security
3/5
Overall score2.75 / 5.00 UsableEvaluatedOct 2026
Scored from trust signals (evidence-eval-v1): 42 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →