obsidian
Comprehensive guidelines for Obsidian.md plugin development including all 27 ESLint rules from eslint-plugin-obsidianmd v0.1.9, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, locale file sentence-case enforcement, and submission requirements. Use when working with Obsidian plugins, main.ts files, manifest.json, Plugin class, MarkdownView, TFile, vault operations, or any Obsidian API development.
99
100%
Does it follow best practices?
Impact
99%
1.37xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides comprehensive specificity with concrete topics and version numbers, includes natural trigger terms that developers would actually use, has an explicit 'Use when...' clause with relevant file types and API elements, and is highly distinctive to the Obsidian.md ecosystem. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and topics: '27 ESLint rules from eslint-plugin-obsidianmd v0.1.9', 'TypeScript best practices', 'memory management', 'API usage (requestUrl vs fetch)', 'UI/UX standards', 'locale file sentence-case enforcement', and 'submission requirements'. These are highly specific and actionable. | 3 / 3 |
Completeness | Clearly answers both what (comprehensive guidelines covering ESLint rules, TypeScript practices, memory management, API usage, UI/UX, locale files, submission requirements) AND when with explicit 'Use when...' clause listing specific file types, classes, and development contexts. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Obsidian plugins', 'main.ts', 'manifest.json', 'Plugin class', 'MarkdownView', 'TFile', 'vault operations', 'Obsidian API development'. These are exactly the terms developers would use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche targeting Obsidian.md plugin development specifically. The combination of Obsidian-specific terms (TFile, MarkdownView, vault operations, manifest.json in Obsidian context) makes it unlikely to conflict with general TypeScript or other plugin development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that efficiently covers 27+ ESLint rules through well-organized tables, provides executable code examples, includes clear validation workflows with feedback loops, and appropriately delegates detailed content to reference files. The structure respects token budget while remaining highly actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly efficient, using tables for rule summaries and avoiding explanations of concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable TypeScript and CSS code examples, specific do/don't patterns in tables, and concrete commands like 'npx eslint .'. The code snippets are copy-paste ready. | 3 / 3 |
Workflow Clarity | The Plugin Submission Validation Workflow provides a clear 6-step sequence with explicit validation checkpoints and a feedback loop ('If ESLint reports new errors after fixing, re-run from step 1'). The code review checklist adds another layer of structured verification. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, rules reference tables, and clearly signaled one-level-deep references to detailed topic files (memory-management.md, accessibility.md, etc.). Navigation is intuitive and well-organized. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- gapmiss/obsidian-plugin-skill
- Commit
08dae85
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.