governance-vault-ops

Operates an Obsidian vault as an auditable ledger with automated sync, checks, and SSH signing.

1|Updated Nov 12, 2024
One-click install
npx skills add https://github.com/ak125/nestjs-remix-monorepo --skill governance-vault-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governance-vault-ops
Source: https://github.com/ak125/nestjs-remix-monorepo/tree/main/.claude/skills/governance-vault-ops
Command: npx skills add https://github.com/ak125/nestjs-remix-monorepo --skill governance-vault-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the secure and auditable operation of an Obsidian vault, ensuring all changes are tracked, signed, and managed according to strict governance rules.

Core Features & Use Cases

  • Automated Sync: Keeps the vault synchronized with a canonical source.
  • Signature Auditing: Enforces and verifies SSH signatures on all commits.
  • Orphan Checking: Identifies and helps manage broken links within the vault.
  • Use Case: Maintain an auditable ledger of decisions and incidents by ensuring every entry in the Obsidian vault is signed, tracked, and free of broken references.

Quick Start

Run the gov command to perform a dry-run sync of the canon to the vault, review changes, and confirm before a signed commit.

Frequently Asked Questions about governance-vault-ops

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

FAQPage Schema
How do I enforce SSH commit signatures in an Obsidian vault?

You can enforce SSH commit signatures by running the `gov` command, which audits all vault commits to verify SSH signatures and tracks changes according to strict governance rules.

What is the best way to maintain an auditable ledger of decisions in Obsidian?

Maintain an auditable ledger by operating the vault with automated diff, sync, and orphaned link checks, enforcing non-autonomous human-decided operations with a single write point and read-only CI.

How do I check for orphaned links in an Obsidian vault?

The Skill checks for orphaned links by identifying and helping manage broken references within the vault during its automated synchronization and audit processes.

Can I synchronize my Obsidian vault from a canonical source automatically?

Yes, you can synchronize your Obsidian vault from a canonical source automatically using a dry-run sync feature, which allows you to review changes and confirm before performing a signed commit.

Does this Obsidian vault governance approach allow autonomous automated commits?

No, this approach enforces non-autonomous, human-decided operations with a single write point and read-only CI to ensure strict auditability. It does not allow autonomous automated commits.

Why does my Obsidian vault sync require human confirmation before committing?

Your Obsidian vault sync requires human confirmation to enforce non-autonomous, human-decided operations, ensuring every change is reviewed, signed, and managed according to strict governance rules.