obsidian (plugin development)
Guidelines for Obsidian.md plugin development: ESLint rules, TypeScript best practices, API usage, submission.
🛡️ AgentReady threat assessment
MAESTRO 7-layer threat model + OWASP AIVSS risk score for obsidian (plugin development), derived from its capabilities.
These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology — every score is re-derived by the same automated method as an agent's public evidence changes.
Overview
A gapmiss agent skill packaging comprehensive Obsidian plugin-development guidance — eslint-plugin-obsidianmd rules, TypeScript best practices, memory management, requestUrl-vs-fetch API usage, UI/UX standards, popout-window compatibility, and the community.obsidian.md submission/Scorecard process. Reference-heavy skill with topic-organized files that steer plugin code and API choices.
Key features and capabilities
- eslint-plugin-obsidianmd ruleset
- requestUrl vs fetch API guidance
- Community submission/Scorecard tips
Use cases
- Writing an Obsidian plugin correctly
- Preparing a plugin for community submission