agentsclimarketplace
Sign in

Llm wiki obsidian hardening

Skill po4yka/llm-wiki-skills/skills/llm-wiki-obsidian-hardening

Harden an Obsidian vault for coding-agent and LLM-Wiki workflows. Use when the user wants Claude Code, Codex, Cursor, or other agents to edit an Obsidian vault without breaking wikilinks, attachments, frontmatter, sync, or human-owned synthesis.From its SKILL.md

Install
npx -y skills add po4yka/llm-wiki-skills --skill llm-wiki-obsidian-hardening

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

  • 1 stars1 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 file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, 585 tokens by cl100k_base, as published. Nobody here has run it

LLM-Wiki Obsidian Hardening

Goal

Make an Obsidian vault safer for agent-assisted LLM-Wiki work.

When to use

  • Before letting a coding agent edit an Obsidian vault for the first time.
  • When wikilinks, embeds, or attachment folders keep breaking after agent edits.
  • When setting up AGENTS.md/CLAUDE.md boundaries for a vault used with LLM-Wiki workflows.
  • When a vault syncs via iCloud, Syncthing, or Obsidian Sync and index or WAL files risk corruption.
  • Before running bulk edits or migrations across vault notes.

Inputs

  • Obsidian vault path.
  • Desired mode: audit-only or apply.
  • Sync method if known.
  • Existing plugins and conventions if relevant.

Procedure

1. Preflight

Check:

  • git or backup exists;
  • .obsidian/ is present;
  • attachment folders and embedded files;
  • wikilink style;
  • frontmatter style;
  • existing AGENTS.md/CLAUDE.md;
  • sync tool and local cache/index files;
  • re-verify the vault's current file state immediately before applying changes, since sync tools may have modified files since the initial scan.

2. Protect Obsidian semantics

Ensure instructions say:

  • preserve [[wikilinks]] unless user asks otherwise;
  • do not rewrite embeds ![[...]];
  • do not move attachments without link repair;
  • do not cat the whole vault;
  • use rg or Obsidian CLI when available;
  • preserve comments, aliases and YAML quoting.

3. Add LLM-Wiki boundaries

Recommend or add:

raw/
wiki/
inbox/
_meta/
_agent/

Add protected section markers around human synthesis when useful.

4. Harden writes

Suggest:

  • dry-run for bulk edits;
  • git branch for migrations;
  • frontmatter validation;
  • no edits under raw/;
  • wiki-lint after large changes;
  • local-only handling for sensitive notes.

5. Sync and index policy

Flag dangerous patterns:

  • syncing SQLite WAL/SHM files;
  • syncing HNSW/vector index files;
  • using multiple sync systems on one vault;
  • treating generated indexes as source of truth.

Prefer per-device indexes and reconstructable caches.

Output

## Obsidian hardening summary

## Vault risks

## Recommended instruction updates

## Link and attachment policy

## Sync/index policy

## Proposed patches

## Next skill

Safety gates

  • Do not alter .obsidian/ settings without explicit approval.
  • Do not rewrite wikilinks to Markdown links.
  • Do not move attachments without link repair.
  • Do not apply hardening changes without git or backup.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.