Use when setting up the shared atmosphere-vault Obsidian vault on a new machine or for a new team member. Guides through cloning, symlinking claude_docs, and verifying obsidian-cli.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
DevOps assistant for setting up the shared atmosphere-vault Obsidian knowledge base on a developer machine.
Invoke when a team member needs to:
PROJECT_DIR = ~/workspace/atmosphere/atmosphere
VAULT_DIR = ~/workspace/atmosphere/atmosphere-vault
VAULT_REPO = git@github.com:Atmosphere/atmosphere-vault.gitAsk the user for PROJECT_DIR and VAULT_DIR if they differ from defaults. The vault is a
sibling of the project directory so the ../atmosphere-vault relative path in the routing
block resolves correctly.
Check that the following are installed:
# Obsidian desktop app (required)
ls /Applications/Obsidian.app 2>/dev/null && echo "Obsidian: OK" || echo "Obsidian: MISSING — install from https://obsidian.md"
# obsidian-cli (optional, for scripted vault access)
which obsidian-cli 2>/dev/null && echo "obsidian-cli: OK" || echo "obsidian-cli: not installed (npm install -g obsidian-cli)"# Only if not already present
if [ ! -d "$VAULT_DIR" ]; then
git clone git@github.com:Atmosphere/atmosphere-vault.git "$VAULT_DIR"
fi
# Verify on main branch
cd "$VAULT_DIR" && git statusInstall obsidian-git and Templater via Obsidian → Settings → Community Plugins, then configure them:
Templates/; trigger on new file creation: enabledPlugin binaries are excluded from git (.obsidian/plugins/ is in .gitignore).
This links atmosphere/claude_docs/ to atmosphere-vault/Claude Outputs/ so Claude Code
session outputs land directly in the vault.
cd "$PROJECT_DIR"
# Safety check: do NOT overwrite a real directory
if [ -d claude_docs ] && [ ! -L claude_docs ]; then
echo "ERROR: claude_docs/ exists as a real directory. Back it up before proceeding."
exit 1
fi
ln -sf "$VAULT_DIR/Claude Outputs" claude_docs
ls -la claude_docs # verify symlink resolvesInstruct the user to:
$VAULT_DIR and click OpenAfter obsidian-git is configured:
# Create a test file in Claude Outputs
echo "# Test" > "$PROJECT_DIR/claude_docs/test.md"
# Verify it appears in the vault
ls "$VAULT_DIR/Claude Outputs/test.md"
# Clean up
rm "$PROJECT_DIR/claude_docs/test.md"claude_docs/ directory that contains real filesmain branch before linkingnpm install -g obsidian-cli (global tool, not a project dependency)ls -la $PROJECT_DIR/claude_docs shows a symlink pointing to $VAULT_DIR/Claude Outputs86693b6
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.