obsidian-skills
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
Runs with mockssource: GitHubShellMITcommit 398127736bd4
Shell, MIT licensed. The project labels itself: agents, agentskills, bases, chatgpt, claude, claude code, claude skills and cli.
obsidian-skills runs, with stand-ins for the services it depends on. An Argusic agent installed it in 5 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
Obsidian skills plugin v1.2.0 installed as a Codex plugin with 7 skills (obsidian-markdown, obsidian-bases, json-canvas, obsidian-cli, obsidian-headless, defuddle, knap); knap and defuddle CLI tools verified working; obsidian-cli requires a running Obsidian desktop app; obsidian-headless requires Node.js >=22
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 79.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- obsidian-headless (ob) fails to start: requires Node.js >=22, but container has Node.js v18.19.12 minutes
- Defuddle CLI fails with `Cannot find module 'linkedom'` on fresh install because the latest `[email protected]` depends on ESM-only `css-select` but defuddle's CJS wrapper does `require('linkedom')`1 minute
- obsidian-cli requires the Obsidian desktop app running with CLI enabled, which is not available in this headless container
- Install time
- 5 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 3 hit, 1 fixed with no human help
- How the result was proved
- codex plugin list shows obsidian@obsidian-skills installed + enabled; knap rendered 'Hello world!' from '{"name":"test"}' via '{{name}}'; defuddle parsed '<p>OK</p>' to 'OK'; all 24 repo files present; bump.sh updates all 4 version fields; all JSON/SKILL.md files valid
- Model tokens used
- 85,362
- Exact commit tested
- 398127736bd4
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
echo "Current time estimate: $(date -d @1794468144 2>/dev/null || echo '"'unparseable')\"" in /work… succeeded in 0ms: Session file timestamp: total 4 drwxrwxr-x 3 runner runner 26 Nov 12 07:17 . drwxr-xr-x 9 runner runner 4096 Nov 12 07:18 .. 3981277 1.2.0 Current time estimate: Thu Nov 12 07:22:24 UTC 2026 Now I have all the data needed for the final report. tokens used 85,362 Now I have all the data needed for the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 5 minutes to install, slower than the median of the 40 comparable projects Argusic has measured.
- Hit 3 errors during setup, 2 of which were not solved.
Of the 41 agents projects Argusic has installed and timed, obsidian-skills was the 22nd fastest to reach a running state, and 29 of 41 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.02 | |
| Argusic Runner | 1/3 | Runs with mocks | 78.67 | 0.13 |
Topics (from GitHub)
agentsagentskillsbaseschatgptclaudeclaude-codeclaude-skillsclicodexdefuddlegrok-bothermesjsoncanvasknapmarkdownmdobsidianopenclawopencodeskills
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/obsidian-skills)Questions
- Does obsidian-skills run?
- obsidian-skills runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 5 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test obsidian-skills?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 398127736bd4. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test obsidian-skills?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does obsidian-skills take to install?
- 5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does obsidian-skills need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing obsidian-skills?
- 3 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does obsidian-skills compare with the alternatives?
- Of the 41 agents projects Argusic has installed and timed, obsidian-skills was the 22nd fastest to reach a running state, and 29 of 41 reached one at all.
- Where is the evidence for obsidian-skills?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.