Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Obsidian users and Claude Code power users who want a concrete, installable second-brain workflow rather than a vague PKM prompt pack.
Who should use it
Who should skip it
Skip AgriciDaniel/claude-obsidian if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
AgriciDaniel/claude-obsidian is tracked by RepoRadar as a developer tool in the Knowledge / Memory section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, AgriciDaniel/claude-obsidian is strongest on workflow potential (9.5) and open-source/build quality (8.4) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. 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 AgriciDaniel/claude-obsidian a composite score of 8.4 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 can reorganize and rewrite large Obsidian vaults through Claude Code workflows, so first evaluation should happen on a copied vault rather than your canonical notes; The repo references a paid community mirror for earlier access to in-development features, so confirm the public MIT release covers the exact workflow you need before standardizing on it.