obsidian-plugins
Files
Install
npx skills add alisonaquinas/llm-doc-skills --skill 'obsidian-plugins' -g -y
/plugin install doc-skills@llm-skills
npx skills when you only want this skill, or install the bundle once to make every included skill available through the plugin marketplace flow. Browse the full skill bundle repository at github.com/alisonaquinas/llm-doc-skills.Invoke
/doc-skills:obsidian-plugins
SKILL.md
name: obsidian-plugins description: Use when a task involves managing Obsidian plugins, enabling or configuring community or core plugins, installing beta plugins via BRAT, or working with plugin data files inside a vault.
Obsidian Plugins
Intent Router
Load sections based on the task:
- Core (built-in) plugin list and configuration →
references/core-plugins-reference.md - Community plugin installation, safe mode, and popular plugins →
references/community-plugins-guide.md - Plugin data files,
.obsidian/plugins/structure, and BRAT →references/plugin-data-and-brat.md
Overview
This skill covers Obsidian plugin management: enabling and configuring core (built-in) plugins, installing and updating community plugins, managing plugin data files inside the vault, and installing pre-release plugins via BRAT.
Use it when setting up a plugin-heavy vault, auditing which plugins are active, debugging plugin conflicts, or automating vault configuration that includes plugin state.
Quick Start
# List installed community plugins in a vault
ls /path/to/vault/.obsidian/plugins/
# Inspect a plugin's stored data
cat /path/to/vault/.obsidian/plugins/dataview/data.json
# Validate plugin manifest JSON
python -c "import json; json.load(open('/path/to/vault/.obsidian/plugins/templater-obsidian/manifest.json'))"
# Check which community plugins are enabled
cat /path/to/vault/.obsidian/community-plugins.json
Preferred Workflow
- Enable community plugins first: Settings → Community Plugins → toggle off Restricted Mode.
- Browse and install via Settings → Community Plugins → Browse — search by name or keyword.
- After installing, open each plugin's settings page to configure it before use.
- Audit
.obsidian/community-plugins.jsonwhen migrating a vault to another machine — installed plugins need reinstalling on the new machine. - Use BRAT only for plugins not yet published to the community directory; pin to a specific release tag for stability.
Authoring Guidance
This skill is the right fit for:
- enabling or disabling core and community plugins
- configuring plugin behavior through settings
- installing beta or pre-release plugins via BRAT
- scripting vault setup that includes plugin state
- debugging plugin conflicts or broken plugin data files
- auditing plugin permissions and data storage
Plugin Conflicts
Plugins occasionally conflict when two plugins bind the same hotkey or patch the same editor behavior. Disable plugins one at a time to isolate a conflict. The developer console (Ctrl+Shift+I / Cmd+Option+I) shows JavaScript errors from failing plugins.
Official References
Primary sources:
- Obsidian community plugins: https://obsidian.md/plugins
- Obsidian help — plugins: https://help.obsidian.md/Extending+Obsidian/Community+plugins
Deep-dive references for this skill:
references/core-plugins-reference.mdreferences/community-plugins-guide.mdreferences/plugin-data-and-brat.md