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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is obsidian-bases in kepano/obsidian-skills

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a thorough, highly actionable reference with executable YAML, a sequenced workflow including validation and test steps, and a properly signaled bundle reference. Its main weakness is volume: substantial reference content and multiple full examples are inlined in SKILL.md that could be delegated to bundle files to better honor progressive disclosure.

Suggestions

Move the three complete worked examples (Task Tracker, Reading List, Daily Notes) into a separate references/examples.md file and keep only one compact representative example inline, with a pointer to the rest.

Consider splitting the file properties table and the per-view-type examples into the bundle, leaving SKILL.md as a tighter overview that points to references/FUNCTIONS_REFERENCE.md and a new references/ for properties/views.

Tighten the workflow's validation step into an explicit inline fix-retry loop (e.g. 'If validation finds issues, fix them and re-validate before proceeding') rather than a forward reference to the Troubleshooting section.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material that assumes Claude's competence (no padding about what YAML or Obsidian is) and delegates the full function reference to the bundle file, but the large inlined set of three complete worked examples plus per-view-type examples could be trimmed slightly.	4 / 5
Actionability	YAML throughout is copy-paste ready — a full schema block, every filter operator, formula patterns, and three complete working .base files (task tracker, reading list, daily notes) covering the common cases, matching the top anchor for fully executable examples.	5 / 5
Workflow Clarity	A clear 6-step sequence includes an explicit Validate step ('Verify the file is valid YAML... Check that all referenced properties and formulas exist') and a Test step with an error-recovery pointer, but the feedback loop is a forward reference to a later section rather than a tight inline fix-retry loop, fitting the anchor for clear sequence with minor validation gaps.	4 / 5
Progressive Disclosure	Structure is good with a clearly signaled one-level-deep bundle reference ('see [FUNCTIONS_REFERENCE.md](references/FUNCTIONS_REFERENCE.md)') that exists on disk, but much reference material (file properties table, all view types, summary formulas, full examples) remains inlined in SKILL.md rather than split out, fitting the anchor for good structure with minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it concisely states the skill's concrete capabilities and provides a rich, explicit 'Use when...' trigger clause with the file extension, product name, and synonyms. It is distinctive and unlikely to fire for the wrong skill.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete capabilities comprehensively ('Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries'), matching the anchor for multiple specific concrete actions with full coverage.	5 / 5
Completeness	Explicitly states both what it does ('Create and edit Obsidian Bases... with views, filters, formulas, and summaries') and when to use it ('Use when working with .base files, creating database-like views of notes, or when the user mentions Bases...'), with concrete trigger phrases matching the top anchor.	5 / 5
Trigger Term Quality	Covers the file extension (.base files), the feature name (Bases), product (Obsidian), and synonyms (table views, card views, database-like views of notes), matching the anchor for comprehensive coverage including synonyms and file extensions.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Obsidian Bases, .base extension) with distinct, product-specific triggers, making conflict with other skills minimal and matching the anchor for a clear niche with distinct triggers.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: breferrari/obsidian-mind
Path: .claude/skills/obsidian-bases/SKILL.md
Commit: b84464b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.