Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams whose most important agent context keeps disappearing into individual local chats instead of becoming searchable shared knowledge.
Who should use it
Who should skip it
Skip Asklear/Klear-Team-Brain if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
Asklear/Klear-Team-Brain is tracked by RepoRadar as a team memory in the AI Infrastructure section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Asklear/Klear-Team-Brain leads on workflow potential (9.6) and practical usefulness (9.0); its lowest signal is momentum (6.0), so factor that in before investing setup time. 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 Asklear/Klear-Team-Brain a composite score of 8.5 out of 10, placing it in the Gold 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 1.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
It collects real coding-agent session artifacts and can upload them to a self-hosted service, so first rollout should keep the directory allowlist tight and verify the client-side redaction path before broader capture; Best fit is teams that already have internal trust boundaries for code, docs, and agent logs, not casual solo users who only need personal recall.