Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for local AI users who keep duplicating model downloads across tools, machines, and runtimes and want one consistent path layer for their own model library.
Who should use it
Who should skip it
Pass on alexziskind1/model-shelf if its scope or audience does not match what your team is building right now.
About this signal
alexziskind1/model-shelf is tracked by RepoRadar as a local ai tool in the Local AI section. It was first seen on 2026-06-27 and last updated on 2026-06-27. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. alexziskind1/model-shelf leads on workflow potential (9.0) and open-source/build quality (8.4); 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 alexziskind1/model-shelf 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 31.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
The Claude plugin path installs a local skill and SessionStart hook, so inspect that behavior before using it in a shared agent environment; If downloads are enabled it can still pull large weights from Hugging Face, so set storage expectations before pointing agents at it; Auto-discovery across mounted drives is convenient but can mask where a model actually came from, so verify the resolved path in workflows that require strict provenance.