agentleFS
Sign inStart free
davidvkimballdavidvkimball/obsidian-dev-skills/obsidian-ops/SKILL.md

obsidian-ops

Skill51 starsChanged 10 months agoMITView on GitHub

Operations, syncing, versioning, and release management for Obsidian projects. Load when running builds, syncing references, bumping versions, or preparing for release.

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. realjaymes/marketingagentskills★ 68same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify Build: Always run a build/lint after significant changes to ensure compatibility.

    line 25
  2. Very specific:

    Sync Status: Keep sync-status.json updated when updating reference materials.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Obsidian Operations Skill

This skill covers the operational aspects of maintaining an Obsidian project, including build workflows, sync procedures, and release management.

Purpose

To ensure reliable builds, consistent reference materials, and safe release processes while strictly following project policies.

Scope

This skill covers:

  • Build and lint workflows
  • Syncing reference documentation from external sources
  • Version management and release preparation
  • Build and environment troubleshooting

Core Rules

  • NEVER perform automatic git operations: AI agents must never execute git commit, git push, or any command that automatically stages or commits changes without explicit user approval for each step.
  • Verify Build: Always run a build/lint after significant changes to ensure compatibility.
  • Sync Status: Keep sync-status.json updated when updating reference materials.

Bundled Resources

  • references/build-workflow.md: Standard build and development commands.
  • references/release-readiness.md: Checklist for ensuring a project is ready for release.
  • references/scorecard-compliance.md: Map of Obsidian community plugin scorecard signals to concrete fixes (vulnerability overrides, attestation workflow, CSS dedup, obsidianmd rules).
  • references/contributing-template.md: Portable CONTRIBUTING.md template for the scorecard hygiene check.
  • references/security-privacy.md: Developer policies, mandatory disclosures, and dependency vulnerability hygiene via pnpm.overrides.
  • references/sync-procedure.md: How to pull updates from reference repositories.
  • references/versioning-releases.md: Workflow for versioning and GitHub releases, including the build-provenance attestation pattern.
  • references/troubleshooting.md: Common issues and their resolutions.
  • references/quick-reference.md: One-page cheat sheet for common operations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free