feat: add obsidian-vault plugin#1
Merged
Merged
Conversation
… creation Review pass on the draft plugin before merge: - plugin.json: add author/repository/keywords to match trip-planner shape; reword description from "always-on" marketing language to accurately describe conditional activation on note creation/editing in a vault - marketplace.json: mirror the new plugin.json description - SKILL.md: add NOT-for clause to disambiguate non-vault .md work; reword detection hint so .obsidian/ can live in an ancestor (Cowork projects commonly sit as subdirectories inside a vault); rename "Safe Editing Rules" to "Safe Output Rules" and annotate edit-only items so the checklist applies to new-file creation too; add property-type consistency check; reword Canvas bullet to remove accidental refusal framing; strengthen recommended CLAUDE.md snippet to cover all .md output (notes, session logs, CLAUDE.md/TASKS.md) - README.md: reframe lead and "What it does" to drop "always-on"; rename "What's always on" heading to "What the skill covers"; update CLAUDE.md snippet to match the SKILL.md version
Match the reworded descriptions now used in plugin.json and marketplace.json — drop "always-on" framing in favor of language that accurately describes conditional activation on note creation/editing.
…rt descriptions Rewrites obsidian-vault/README.md to mirror trip-planner's proven shape: promise-led lead paragraph, "What you get" bullets naming specific failure modes (broken wikilinks, YAML type drift, callout fallbacks), a dedicated "How it works" activation explainer, and a "Why a plugin?" section that frames the alternative honestly (full conventions would crowd out project-specific context in CLAUDE.md). Short descriptions in plugin.json, marketplace.json, and the root README plugins table now share the same line — "Let Claude edit your Obsidian vault without breaking it. Wikilinks stay linked, frontmatter stays queryable, callouts render — and Claude speaks Dataview, Tasks, Templater, Bases, and Canvas fluently." — replacing the drier "conventions applied automatically" framing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
obsidian-vault plugin
Adds the
obsidian-vaultplugin — an always-on Obsidian conventions skill for Claude Cowork vaults.What it does
Keeps Claude's note editing consistent and safe across sessions. The skill activates automatically whenever Claude detects an Obsidian vault in the working directory. Core OFM conventions are always in context; detailed plugin syntax and property type rules load from reference files only when the task calls for them.
Files added
.claude-plugin/marketplace.jsonupdated to include theobsidian-vaultentry at the current version (0.4.3).TODOs before merge