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

81%

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

Quality

Content

75%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 content is an efficiently organized, actionable reference for authoring .base files, with a real workflow and a properly offloaded functions reference. It could tighten its inline tables and make the validation feedback loop more explicit to reach the top of the scale.

Suggestions

Make the validation step an explicit feedback loop (e.g., "If validation fails: fix the issue, then re-validate before testing in Obsidian") rather than a descriptive checklist.

Move the file-property and summary-formula tables into FUNCTIONS_REFERENCE.md or a dedicated reference file to keep SKILL.md a leaner overview.

Expand the map-view example with concrete lat/lng property settings so all four view types have equally executable examples.

Dimension	Reasoning	Score
Conciseness	The body is a lean reference (schema, tables, signatures) that assumes Claude's competence and avoids explaining YAML or Obsidian; minor over-explanation appears in the inline comments and the somewhat repetitive WRONG/CORRECT pairs.	4 / 5
Actionability	Concrete, copy-paste-ready YAML examples cover the common cases (filters, formulas, full example bases), with only minor gaps such as the sparse map-view example and the lack of an executable validation command.	4 / 5
Workflow Clarity	A six-step workflow includes a "Validate" step and a "Test in Obsidian" step with concrete checks (valid YAML, referenced properties/formulas exist, common issues); checkpoints are present but the validate-fix-retry loop is descriptive rather than a strict explicit feedback loop.	4 / 5
Progressive Disclosure	Good structure with a clearly signaled one-level-deep reference to the verified FUNCTIONS_REFERENCE.md bundle file, offloading the bulk function catalog; the body still retains sizable inline reference material (file-property table, summary-formulas table, operator table), keeping it just short of the lean overview ideal.	4 / 5
	Total	16 / 20 Passed

Description

87%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.

A well-crafted description that concretely states capabilities and provides explicit, natural trigger terms with the file extension. Its only mild gap is that the action vocabulary is mostly create/edit rather than a broader enumerated set.

Dimension	Reasoning	Score
Specificity	"Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries" names the domain plus several concrete capability areas, but the actions themselves are limited to create/edit rather than an exhaustive action list.	4 / 5
Completeness	It explicitly answers both "what" (create/edit Bases with views, filters, formulas, summaries) and "when" ("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") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keyword coverage including ".base files", "Bases", "table views", "card views", "filters", "formulas", and "database-like views of notes", but a few natural variants like "list view" and "map view" are absent.	4 / 5
Distinctiveness Conflict Risk	"Obsidian Bases (.base files)" is a clear, narrow niche with distinct triggers, making it unlikely to fire for the wrong skill.	5 / 5
	Total	18 / 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: Atmosphere/atmosphere
Path: .claude/skills/obsidian-bases/SKILL.md
Commit: b600b8a

Reviewed: 2 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.