obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 follows best practices closely. It uses third person voice, lists specific capabilities, includes a clear 'Use when...' clause with multiple natural trigger terms, and targets a distinct niche (Obsidian Bases) that is unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create and edit Obsidian Bases', '.base files', 'views, filters, formulas, and summaries'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create and edit Obsidian Bases with views, filters, formulas, and summaries) and 'when' (explicit 'Use when...' clause covering .base files, database-like views, and multiple trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: '.base files', 'Bases', 'table views', 'card views', 'filters', 'formulas', 'Obsidian', 'database-like views of notes'. These are terms users would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Obsidian Bases and .base files are a very specific feature. The mention of the file extension, 'Obsidian', and specific view types (table views, card views) make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflows and excellent concrete examples. Its main weakness is length—several reference tables (file properties, operators, summaries) could be moved to supporting files to improve conciseness and progressive disclosure. The troubleshooting section with WRONG/CORRECT pairs is particularly valuable.
Suggestions
Move the file properties reference table, filter operators table, and default summary formulas table to a separate reference file (e.g., references/PROPERTIES_REFERENCE.md) to reduce SKILL.md length and improve progressive disclosure.
Ensure the referenced references/FUNCTIONS_REFERENCE.md file actually exists in the bundle to support the progressive disclosure pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy—the filter operators table, file properties reference, and summary formulas table are extensive reference material that could be offloaded to a separate reference file. Some sections like the view type examples are minimal enough to be efficient, but the overall length (~350 lines) could be tightened by moving reference tables to supporting files. | 2 / 3 |
Actionability | The skill provides fully executable YAML examples throughout, including complete base files for task tracking, reading lists, and daily notes. Filter syntax, formula syntax, and view configurations are all copy-paste ready with correct YAML formatting. The troubleshooting section provides concrete WRONG/CORRECT pairs. | 3 / 3 |
Workflow Clarity | The workflow section at the top provides a clear 6-step sequence with explicit validation checkpoints (step 5 validates YAML syntax and property references, step 6 tests in Obsidian with error recovery guidance). The troubleshooting section serves as a feedback loop for common errors with specific fix patterns. | 3 / 3 |
Progressive Disclosure | The skill references FUNCTIONS_REFERENCE.md for the complete functions reference, which is good progressive disclosure. However, the file properties table, filter operators table, and summary formulas table are all inline when they could be in reference files. The skill is quite long for a SKILL.md overview. No bundle files were provided to verify the referenced FUNCTIONS_REFERENCE.md exists. | 2 / 3 |
Total | 10 / 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
- kepano/obsidian-skills
- Commit
ac93987
- 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.