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

obsidian-dev

Skill51 starsChanged 10 months agoMITView on GitHub

Development patterns for Obsidian. Load when implementing features or following coding conventions.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow established patterns for your project type (plugin/theme)

    line 24
  2. Distinctive:

    Use appropriate tools and conventions

    line 25
  3. Distinctive:

    Test thoroughly across different environments

    line 26
  4. Distinctive:

    Document important decisions and patterns

    line 27

≈ “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 Development Skill

This skill provides patterns and rules for developing Obsidian plugins and themes.

Purpose

To ensure consistent development across plugins and themes, proper code organization, and adherence to Obsidian's development patterns.

Scope

This skill covers:

  • Implementing new plugin features
  • TypeScript/JavaScript coding conventions
  • Plugin debugging and troubleshooting
  • Project structure and organization

Core Rules

  • Follow established patterns for your project type (plugin/theme)
  • Use appropriate tools and conventions
  • Test thoroughly across different environments
  • Document important decisions and patterns

Bundled Resources

  • references/plugin-guidelines.md: Official Obsidian plugin review guidelines
  • references/agent-dos-donts.md: Critical development guidelines
  • references/code-patterns.md: Implementation patterns and examples
  • references/coding-conventions.md: Code style and organization
  • references/commands-settings.md: Command and settings patterns
  • references/common-tasks.md: Frequently needed 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