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

82%

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

65%

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

The content is highly actionable with complete executable examples but is organized as a monolithic inline reference rather than an overview pointing to bundled detail files, and lacks validation checkpoints for the create/edit workflow. Splitting the function/type reference into bundled files and adding a verify-after-edit step would lift the weaker dimensions.

Suggestions

Move the exhaustive functions reference (global/date/string/number/list/file/link/object/regexp tables) into a bundled REFERENCES.md and keep SKILL.md as a concise overview with one-level-deep, clearly signaled links.

Add a short create/edit workflow with an explicit validation checkpoint, e.g. 'after editing, confirm the .base YAML parses and the target view renders before finalizing.'

Trim the inline 'Common Patterns' and default-summary tables or relocate them to the bundled reference so the main file stays focused on the schema and a couple of canonical examples.

Dimension	Reasoning	Score
Conciseness	The body is largely lean reference material with no concept preamble, but the entire function/type reference and all examples are inlined (~610 lines) when much could live in a bundled file, leaving it mostly efficient but heavier than necessary.	2 / 3
Actionability	Provides copy-paste-ready YAML for every construct plus four complete worked Base files and full function signatures, matching the executable-and-complete anchor.	3 / 3
Workflow Clarity	Structure is clear for a reference skill, but the promised create/edit task has no validate→fix→confirm loop (e.g. verify YAML parses, confirm a view renders), so the missing validation checkpoints cap it below 3.	2 / 3
Progressive Disclosure	No bundle files exist and the SKILL.md is a monolithic inline reference (full function tables, all view types, all examples) with only external help-doc links, matching the 'large API reference that could be in a separate file' anchor rather than a split, navigable structure.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is exemplary: it names concrete capabilities, includes an explicit 'Use when...' trigger clause with natural terms, answers both what and when, and occupies a clearly distinct niche. No improvements needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Create and edit", "views, filters, formulas, and summaries"), matching the anchor for several specific capabilities rather than a single domain+action.	3 / 3
Completeness	Explicitly states both what it does and when to use it via an explicit "Use when working with .base files... or when the user mentions..." clause, matching the anchor-3 example.	3 / 3
Trigger Term Quality	Covers natural user terms (.base files, Bases, table views, card views, filters, formulas, database-like views) that a user would actually say, matching the full-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Obsidian Bases / .base files is a distinct niche with specific triggers unlikely to conflict with other skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (619 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: heyitsnoah/claudesidian
Path: .agents/skills/obsidian-bases/SKILL.md
Commit: 6c56f35

Reviewed: about 16 hours 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.