obsidian-plugin-dev
Skill0 starsChanged 10 months agoMITView on GitHub
Best practices for Obsidian plugin development
2 other projects use a version of this.
Adopted by
Most recently taken up by
- aresbit/claude-skillstheir own version, first seen Jul 12, 2026
- strombraaten/claude-skillstheir own version, first seen Jun 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- aresbit/claude-skills★ 0same name
- strombraaten/claude-skills★ 0same 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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llm-integrationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 162
Check console: Ctrl+Shift+I / Cmd+Option+I
- Very specific: line 168
Use app.metadataCache for file metadata instead of reading full file
- Distinctive: line 175
Never execute user-provided code
≈ “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.
Files
Obsidian Plugin Development Skill
This skill provides context and patterns for developing Obsidian plugins effectively.
Core Patterns
Plugin Lifecycle
import { Plugin } from 'obsidian';
export default class MyPlugin extends Plugin {
async onload() {
// Register commands, UI, events
// Load settings
// Initialize managers
}
onunload() {
// Cleanup: remove UI, unregister events
}
}Safe File Operations
// ✅ Correct: Use Vault API
const file = this.app.vault.getAbstractFileByPath(path);
if (file instanceof TFile) {
const content = await this.app.vault.read(file);
await this.app.vault.modify(file, newContent);
}
// ❌ Wrong: Never use Node.js fs
import * as fs from 'fs'; // NEVER DO THISFrontmatter Management
import { App, TFile } from 'obsidian';
async function updateFrontmatter(app: App, file: TFile, updates: Record<string, any>) {
await app.fileManager.processFrontMatter(file, (frontmatter) => {
Object.assign(frontmatter, updates);
});
}Modal Creation
import { Modal, App, Setting } from 'obsidian';
class MyModal extends Modal {
constructor(app: App, private onSubmit: (result: string) => void) {
super(app);
}
onOpen() {
const { contentEl } = this;
contentEl.createEl('h2', { text: 'Title' });
new Setting(contentEl)
.setName('Input')
.addText(text => text.onChange(value => {
// Handle input
}));
new Setting(contentEl)
.addButton(btn => btn
.setButtonText('Submit')
.setCta()
.onClick(() => {
this.close();
this.onSubmit(result);
}));
}
onClose() {
const { contentEl } = this;
contentEl.empty();
}
}Settings Management
interface MyPluginSettings {
apiKey: string;
folderPath: string;
}
const DEFAULT_SETTINGS: MyPluginSettings = {
apiKey: '',
folderPath: 'MyFolder'
};
// In Plugin class:
settings: MyPluginSettings;
async onload() {
await this.loadSettings();
this.addSettingTab(new MySettingTab(this.app, this));
}
async loadSettings() {
this.settings = Object.assign({}, DEFAULT_SETTINGS, await this.loadData());
}
async saveSettings() {
await this.saveData(this.settings);
}Common Pitfalls
Path Handling
// ✅ Always normalize paths
import { normalizePath } from 'obsidian';
const safePath = normalizePath(userInputPath);
// ✅ Check existence before operations
const exists = await this.app.vault.adapter.exists(path);
if (!exists) {
await this.app.vault.createFolder(path);
}File Moving
// ✅ Correct: Use Vault API with TFile
const file = this.app.vault.getAbstractFileByPath(oldPath);
if (file instanceof TFile) {
await this.app.fileManager.renameFile(file, newPath);
}Event Handling
// Register events properly
this.registerEvent(
this.app.vault.on('modify', (file) => {
// Handle file modification
})
);
// Events are automatically cleaned up on plugin unloadTesting in Obsidian
- Build plugin:
npm run build - Copy outputs to vault:
.obsidian/plugins/your-plugin/main.jsmanifest.jsonstyles.css(if exists)
- Reload Obsidian: Ctrl+R / Cmd+R
- Check console: Ctrl+Shift+I / Cmd+Option+I
Performance Tips
- Cache
TFilereferences when processing multiple operations - Debounce frequent operations (file watches, input handlers)
- Use
app.metadataCachefor file metadata instead of reading full file - Batch file operations when possible
Security
- Validate all user inputs before file operations
- Sanitize file names: no
.., absolute paths, or special chars - Never execute user-provided code
- API keys: stored in
data.json(handled by Obsidian)
Useful APIs
this.app.vault: File operationsthis.app.workspace: UI and view managementthis.app.metadataCache: File metadata and linksthis.app.fileManager: Advanced file operationsthis.addCommand(): Register commandsthis.registerEvent(): Subscribe to eventsnew Notice(message): Show notifications
Resources
- Official API: https://docs.obsidian.md/
- Plugin examples: https://github.com/obsidianmd/obsidian-sample-plugin
- Community plugins: https://github.com/obsidianmd/obsidian-releases
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
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.

