Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for heavy coding-agent users who want to see whether their own prompting, verification habits, and workflow structure are improving over time instead of guessing.
Who should use it
Who should skip it
Skip Feloguarin/claude-insight if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
Feloguarin/claude-insight is tracked by RepoRadar as a developer tool in the Productivity section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for Feloguarin/claude-insight are workflow potential (9.0) and open-source/build quality (8.4), while momentum (6.0) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Feloguarin/claude-insight a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 53.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Transcript analysis reads whatever is already stored in local Claude Code logs, so review what lives in your transcript directory before running it on a shared or regulated workstation; The install shortcut pipes a shell script that writes a slash command into the local Claude Code environment, so inspect that script before using the one-liner on a main machine; Fluency scores and builder archetypes are useful diagnostics rather than ground truth, so compare the report against a few real transcripts before turning it into policy or performance review.