From obsidian-pack
Execute Obsidian secondary workflow: UI components and user interaction. Use when building modals, views, suggestions, or custom UI elements. Trigger with phrases like "obsidian modal", "obsidian UI", "obsidian view", "obsidian custom interface".
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-pack:obsidian-core-workflow-bThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Secondary workflow for Obsidian: building modals, views, suggestion popups, and custom UI elements.
Secondary workflow for Obsidian: building modals, views, suggestion popups, and custom UI elements.
obsidian-install-auth setupobsidian-core-workflow-aFor full implementation details and code examples, load:
references/implementation-guide.md
| Error | Cause | Solution |
|---|---|---|
| View not showing | Not registered | Call registerView in onload |
| Modal closes immediately | Event propagation | Stop event propagation |
| Decorations not updating | Missing update handler | Implement update method |
| Menu item missing | Wrong event | Verify event type |
For common errors, see obsidian-common-errors.
Basic usage: Apply obsidian core workflow b to a standard project setup with default configuration options.
Advanced scenario: Customize obsidian core workflow b for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub bulozb/claude-code-plugins-plus-skills --plugin obsidian-packGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
4plugins reuse this skill
First indexed Jul 11, 2026