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.

2.56x

Quality

—

Does it follow best practices?

Impact

82%

2.56x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

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 an accurate, highly actionable Obsidian Bases reference with excellent copy-paste examples, but it is a monolithic inline dump that underperforms on token efficiency and progressive disclosure, and lacks an explicit creation/validation workflow.

Suggestions

Move the full function reference tables (global, date, string, number, list, file functions) and default summary formulas into a separate REFERENCES.md, keeping SKILL.md as a concise overview with one-level-deep links.

Add a short 'Creating a Base' workflow with explicit steps and a validation checkpoint (e.g., confirm the .base renders in Obsidian or lint the YAML) before considering the file complete.

Trim redundant inline examples — keep one canonical full example in SKILL.md and relocate the others to an EXAMPLES.md file.

Dimension	Reasoning	Score
Conciseness	Every line is useful reference material Claude would not know (no generic concept explanations), but the ~600-line body is a large monolithic dump of full function tables and four complete examples that could be tightened or split out, fitting the 'could be tightened' anchor rather than 'lean'.	2 / 3
Actionability	It provides a complete schema, filter/formula syntax, per-view-type examples, and four copy-paste-ready full .base files (Task Tracker, Reading List, Project Notes, Daily Notes), fully executable YAML guidance.	3 / 3
Workflow Clarity	The body is a syntax reference rather than a sequenced process; there is no explicit step sequence with validation checkpoints for creating/editing .base files, so it sits at the 'sequence present but checkpoints missing/implicit' level at best.	2 / 3
Progressive Disclosure	Content is well-organized by headers, but the entire API reference and all examples live inline in one 600-line SKILL.md with no bundle files to offload detail, matching the 'content that should be separate is inline' anchor.	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: third-person voice, concrete capabilities, a rich explicit 'Use when' trigger clause, and a distinct niche. It matches the strongest anchor on every dimension.

Dimension	Reasoning	Score
Specificity	It names concrete actions ('Create and edit') and enumerates specific components ('views, filters, formulas, and summaries'), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly states what the skill does and provides an explicit 'Use when' clause answering when to invoke it, satisfying both halves of the dimension.	3 / 3
Trigger Term Quality	The 'Use when' clause covers natural terms users would say — '.base files', 'database-like views', 'Bases', 'table views', 'card views', 'filters', 'formulas' — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	The Obsidian Bases niche with file-extension and feature-specific triggers makes it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Repository: davepoon/buildwithclaude
Commit: 2b23b55

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.