Obsidian

Skill yuelenghan/orbit/skills/obsidian

An open-source arsenal of reusable skills for AI agents — repo understanding, code review, delivery workflows, security pentests, and plug-and-play integrations with Jira, GitHub, GitLab, Jenkins & more. Drop into Claude Code, Codex, or any skill-aware host.

Install

npx -y skills add yuelenghan/orbit --skill obsidian

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user needs local vault note search, read, create, update, or label operations through the packaged launcher and local CLI runtime.

SKILL.md

1.8 KB, 341 tokens by cl100k_base, as published. Nobody here has run it

Obsidian Skill

Use this skill to operate a local Obsidian vault through the packaged launcher and local CLI runtime.

Within Orbit's shared provider framework, this skill is one implementation of the docs capability.

Runtime and execution

Always run the packaged launcher through ${OBSIDIAN_SKILL_DIR} so it works from the user's current working directory:

macOS/Linux: ${OBSIDIAN_SKILL_DIR}/bin/obsidian
Windows: ${OBSIDIAN_SKILL_DIR}\bin\obsidian.cmd

${OBSIDIAN_SKILL_DIR} is a documentation placeholder, not a guaranteed shell environment variable. Resolve BIN to a real launcher path once before the first CLI call. Do not call node app/dist/cli.js directly.

Scope and boundaries

Local vault operations only.
CLI-mediated operations only.
No remote REST dependencies.
Labels map to YAML frontmatter tags so scenarios can keep using the shared docs.content.label.add contract.

Capability Domain

Domain:

docs

Provides:

docs.config.get
docs.config.set
docs.content.search
docs.content.get
docs.content.create
docs.content.update
docs.content.label.add
provider-specific workflow helpers

Config check:

obsidian config get

Config check

Run obsidian config get when configuration state is unknown or before the first provider-scoped task in a new session.

Supporting files

Read references/commands.md for the packaged command surface.
Read references/usage.md for execution policy and local-vault behavior.

Gives 0 of the 12 instructions most note taking skills give in 341 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-07

include a visual element on every slidein 44 of 686, across 13 files
use wikilinks for internal vault linksin 36 of 686, across 12 files
commit to a single visual motif across every slidein 34 of 686, across 9 files
use subagents to visually inspect rendered slidesin 31 of 686, across 7 files
read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
keep 0.5 inch minimum marginsin 30 of 686, across 7 files
re-verify affected slides after every fixin 27 of 686, across 5 files
run content QA checks before declaring successin 26 of 686, across 3 files
Use Markdown links for external URLs onlyin 26 of 686, across 11 files
pick a bold topic specific color palettein 24 of 686, across 2 files
read editing guide before editing existing presentationsin 23 of 686, across 1 file
use one dominant color across all slidesin 23 of 686, across 1 file

Said here and by no other author read

Use the packaged launcher for all operations
Resolve the launcher path before the first CLI call
Do not call node directly
Restrict operations to the local vault
Restrict operations to the CLI
Run config get when configuration state is unknown

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.