CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A thorough, accurate reference manual with excellent executable examples, but it is a monolithic inlined API guide rather than an overview that progressively discloses detail, and it lacks explicit validation checkpoints for editing structured .base files.

Suggestions

Move the full Functions Reference (global, string, number, list, file, link, object, regexp tables) into a bundled REFERENCES.md and keep only a concise quick-start plus a few key examples in SKILL.md.

Add a short "Authoring workflow" section with explicit validation checkpoints, e.g. confirm the .base parses as YAML and the view renders before handing the file back to the user.

Add an explicit "Common pitfalls / deprecated patterns" callout so the Duration .round() caveat (currently inline) and any older syntax are grouped and signaled as such.

DimensionReasoningScore

Conciseness

Mostly efficient reference prose with no condescension, but ~650 lines of function/operator tables are inlined wholesale in SKILL.md when much of that API surface could live in a separate reference file.

3 / 5

Actionability

Copious copy-paste-ready YAML examples — filter structures, formula expressions, view configs, and four complete example Bases — cover the common cases with executable syntax rather than pseudocode.

5 / 5

Workflow Clarity

The body is a reference layout, not a sequenced workflow; there are no explicit validation or verification checkpoints (e.g. "confirm YAML parses", "check the base renders") for a task that edits structured files.

3 / 5

Progressive Disclosure

Section headers are well organized, but the bulk API/function reference is inlined in SKILL.md and the only outbound pointers are external doc URLs at the bottom — no one-level-deep bundled reference files to split detail into.

3 / 5

Total

14

/

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.

A model description: third-person voice, concrete actions, explicit trigger guidance with natural synonyms and the file extension, and a distinct niche. It reads like one of the rubric's good examples.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("Create and edit") plus the specific feature surface (views, filters, formulas, summaries), giving comprehensive coverage of what the skill manipulates.

5 / 5

Completeness

Explicitly answers both what ("Create and edit Obsidian Bases ... with views, filters, formulas, and summaries") and when ("Use when working with .base files ... or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian").

5 / 5

Trigger Term Quality

Covers natural user phrasings and synonyms — ".base files", "Bases", "table views", "card views", "filters", "formulas", "database-like views of notes" — including the file extension.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Obsidian Bases / .base files) with product-specific triggers, giving minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (652 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
anbeime/skill
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.