skills.rest
cookkie03
cookkie03COMMUNITY
Explore all skills by this author →
GitHub

workspace-setup

Configures an Obsidian vault as a git-synced collaborative workspace for AI agents.

Updated May 10, 2026
Search Tags:#git#claude code#hooks#obsidian#vault setup#workspace automation#frontmatter validation
One-click install
npx skills add https://github.com/cookkie03/skills --skill workspace-setup-cookkie03
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workspace-setup
Source: https://github.com/cookkie03/skills/tree/main/workspace-setup
Command: npx skills add https://github.com/cookkie03/skills --skill workspace-setup-cookkie03

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve? Setting up an Obsidian vault so a human and an AI coding agent can work on it together—synchronously or asynchronously—requires git configuration, commit conventions, agent hooks, and persistent memory files. Doing this by hand is error-prone and the setup drifts over time. ## Core Features & Use Cases - Guided vault setup: Interviews the user about purpose, folders, language, and remote (GitHub or Gitea), then initializes git, .gitignore, and the Obsidian Git plugin configuration. - Living state files in _meta/: Generates taxonomy.md, index.md, hot-cache.md, and log.md so the AI always knows where things are, what changed, and why—kept separate from an immutable CLAUDE.md. - Multi-agent hooks: Installs a shared auto-commit Stop hook and a pre-turn session-brief hook (user delta since last ai: commit) for Claude Code, Agents SDK, and Gemini CLI. - Deterministic auditors: Ships check-claude-md.py (anti-drift audit of CLAUDE.md) and check-frontmatter.py (data-driven frontmatter validation) plus sync.py to auto-rebuild the index. - Use Case: Ask the AI to prepare an existing Obsidian vault for collaborative work; it detects what is missing, wires the hooks, and produces an operational CLAUDE.md with AGENTS.md/GEMINI.md symlinks. ## Quick Start Set up this Obsidian vault as a collaborative AI workspace with git sync and generate the CLAUDE.md and _meta state files.

Frequently Asked Questions about workspace-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an Obsidian vault to work with an AI coding agent?▼

Run the workspace-setup flow: it interviews you about purpose, folders, and remote, then initializes git, configures the Obsidian Git plugin, installs agent hooks, and generates a CLAUDE.md plus living state files in _meta/ that keep the AI oriented across sessions.

How do I sync an Obsidian vault with git automatically?▼

The skill configures the Obsidian Git plugin with a 10-minute auto-backup interval, auto-pull on startup, and push on backup using the vault: commit prefix. An agent-side Stop hook commits AI changes with the ai: prefix and pushes to GitHub or Gitea.

Does this work with agents other than Claude Code?▼

Yes. The hook script is agent-agnostic and lives in hooks/auto-commit.sh; each agent only needs its own config file pointing to it. Templates are provided for Claude Code (.claude/settings.json), Agents SDK (.agents/settings.json), and Gemini CLI (.gemini/settings.json).

How does the AI know what the user changed between sessions?▼

A pre-turn hook (_meta/session-brief.sh) injects the delta since the last ai: commit into context: user commits, uncommitted files, new _raw/ inbox items, and %% comments. It is read-only, silent when there is no delta, and never blocks the prompt.

Why does CLAUDE.md drift over time and how is it prevented?▼

CLAUDE.md tends to accumulate dates, procedures, and stale folder references. The check-claude-md.py auditor mechanically flags dated facts, numbered procedures, long catalogs, and nonexistent paths, running at session start and in the Stop hook whenever CLAUDE.md changes.

What are the limitations of the auto-commit hook?▼

The hook skips execution during rebase, merge, cherry-pick, or detached HEAD states to avoid corrupting the repo, and a failed pull --rebase is aborted so sync is deferred to the next cycle. Push failures are left for Obsidian Git to reconcile rather than forced.

Related Skills

Explore More Software Engineering Skills→
MengboooMengbooo

obsidian-setup

Configures MOTechTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTimeTime.

Community
Intermediate
NirajkashyapNirajkashyap

wiki-ingest

Ingest documents into an Obsidian wiki as interconnected wiki pages.

Community
Advanced
CarbeneAICarbeneAI
9

Obsidian

Create and edit Obsidian Markdown, Bases, and JSON Canvas files.

Community
Intermediate
hummbl-devhummbl-dev

obsidian

Manage Obsidian Markdown vaults and notes with automatic wikilink updates.

Community
Intermediate