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.
76
71%
Does it follow best practices?
Impact
82%
2.56xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/obsidian-bases/SKILL.mdQuality
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 comprehensive 'Use when...' clause with multiple natural trigger terms, and targets a clearly distinct niche (Obsidian Bases). It closely mirrors the good examples provided in the rubric.
| 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, Bases, table views, card views, filters, formulas in Obsidian). | 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 needing this skill. | 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, product name, and specific feature names (card views, table views) make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with numerous complete, executable YAML examples covering diverse use cases. However, it is severely bloated — functioning as an exhaustive reference document rather than a focused skill guide, with inline function tables and property references that should be in separate files. It also lacks any explicit workflow for creating/validating .base files, which is a significant gap for a file-creation skill.
Suggestions
Extract the function reference tables (Global, Date, String, Number, List, File functions) and property references into a separate REFERENCE.md file, linking to it from the main skill.
Add a clear step-by-step workflow section: 1) Create .base file, 2) Define filters, 3) Add formulas, 4) Configure views, 5) Validate YAML syntax, 6) Test in Obsidian — with explicit validation guidance.
Remove the 'When to Use This Skill' and 'Overview' sections — this context belongs in frontmatter metadata, not the skill body.
Move the complete examples (Task Tracker, Reading List, etc.) to an EXAMPLES.md file, keeping only one concise example inline to demonstrate the pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, functioning as a comprehensive reference manual rather than a concise skill guide. It includes exhaustive function reference tables (string, number, list, date functions), operator tables, and property references that Claude could look up or already knows. The 'When to Use This Skill' and 'Overview' sections explain obvious concepts. Much of this content belongs in separate reference files. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready YAML examples throughout. The complete examples (Task Tracker, Reading List, Project Notes, Daily Notes Index) are concrete and immediately usable. Filter syntax, formula syntax, and view configurations all include working code. | 3 / 3 |
Workflow Clarity | There is no explicit workflow for creating or editing a .base file — no step-by-step process, no validation checkpoints, no guidance on how to verify the YAML is valid before saving. For a skill involving file creation/editing, the absence of a 'create a base file' workflow with validation steps is a notable gap. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with all content inline — exhaustive function reference tables, complete schema, all view types, all filter patterns, and multiple full examples. The references section at the bottom links to external docs but the skill itself should split the function references, property references, and detailed examples into separate files, keeping only a quick-start overview and navigation in the main SKILL.md. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (603 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Lingjie-chen/MT5
- Commit
3069d33
- 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.