Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This skill set enables personal knowledge management users to automate the ingestion and organization of information within Obsidian. It focuses on turning raw sources into a structured network of linked notes that the user owns and controls.
Researchers can execute bounded, source-grounded research loops to investigate topics via the public web and draft cited dossiers. These findings can then be merged into a canonical vault through a reviewed process, ensuring deep research is systematically filed.
WHO IT'S FOR
PKM power users
building a connected knowledge graph in Obsidian
Academic researchers
running source-grounded research loops and drafting dossiers
Visual thinkers
mapping knowledge using Obsidian JSON Canvas boards
Content curators
extracting clean Markdown from cluttered web pages
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
Install the claude-obsidian plugin from the Claude Code marketplace
Installs: Complete claude-obsidian product package: skills, portable core, Claude adapter, and templates. · Claude Code
Before you start
Python 3.11 or newer, reachable as `python3` on `PATH` for both plugin hooks; native Windows requires the setup described in the Windows and WSL guide.
A current Claude Code release supporting the exec-form `command` and `args` hook shape and the `compact` `SessionStart` matcher.
Bash for installer and optional legacy-extension scripts.
Obsidian is optional and needed only for its visual editor.
On Windows, use WSL for vault writes; native Windows supports only read-only inspection and dry-runs.
Platform: Vault writes on Windows require WSL; native Windows is limited to read-only inspection and dry-runs. The documented native-Windows setup must make `python3` available on `PATH` for the hooks.
Run from: A separate, user-owned Obsidian vault when using the installed plugin; do not use the plugin cache as the vault.
In a terminal, add the author's public marketplace, install the namespaced plugin, and verify that it appears in the plugin list.
claude plugin marketplace add AgriciDaniel/claude-obsidian
claude plugin install claude-obsidian@agricidaniel-claude-obsidian
claude plugin list
When using the plugin, run Claude from the separate user vault, set CLAUDE_OBSIDIAN_VAULT, or pass --vault to portable commands. Do not use the read-only plugin cache as the vault.
Absolute or otherwise resolvable path to the Obsidian vault.
Optional exclusion glob, such as wiki/scratchpad/*, if part of the vault should be omitted.
Use the wiki-lint skill to run a deterministic, read-only health check on the Obsidian vault at /path/to/vault. Return the Markdown report in chat, preserve the reported paths, line numbers, categories, and counts, and group findings by likely impact. Do not repair or write anything. Replace /path/to/vault with the actual vault directory.
Optional vault path or relevant note inventory for locally checking link targets.
Use the obsidian-markdown skill to validate the pasted Obsidian note draft. Check its YAML properties, internal wikilinks, heading and block references, callout quoting, and code-fence balance. Clearly separate confirmed problems from targets that cannot be verified with the supplied context, and do not edit the vault.
The desired success condition and any important stakes.
Use the think skill to review this decision: [decision or question]. Use only the evidence and constraints I provide. Separate observations, inferences, unknowns, and preferences, then give a concise recommendation, the strongest counterargument, key risks, verification still needed, and a condition for revisiting the decision. Do not edit files or publish anything.