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.

77

2.56x
Quality

72%

Does it follow best practices?

Impact

82%

2.56x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/obsidian-bases/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 accurate and rich with executable YAML examples, but it inlines a large amount of reference material that would be better split into bundled files, and lacks explicit validation steps for the .base files it helps generate. It reads more as an embedded manual than a lean SKILL.md overview.

Suggestions

Move the function/property/summary reference tables and the complete schema into bundled reference files (e.g. references/functions.md, references/schema.md) and replace them with a concise summary plus one-level-deep links, to improve progressive_disclosure and conciseness.

Add a short, explicit workflow with a validation checkpoint (e.g. 'Confirm the .base file parses as valid YAML and the referenced properties/formulas exist before saving') to lift workflow_clarity above the destructive/batch cap of 3.

Trim redundant prose such as restating what each section contains and the generic 'This skill enables Claude Code to...' intro, keeping only what Claude cannot already infer.

DimensionReasoningScore

Conciseness

The body is noticeably verbose for a reference skill: large inline function/property tables (File Properties Reference, Global/Date/String/Number/List/File Functions, Default Summary Formulas) reproduce reference material Claude could consult via the linked docs, and the full schema plus four complete worked examples pad the file well beyond a lean overview.

2 / 5

Actionability

Provides concrete, copy-paste-ready YAML blocks for filters, formulas, views, and four complete example bases, with only minor gaps (e.g. map view is only briefly described rather than shown with required lat/long fields).

4 / 5

Workflow Clarity

Structure (schema -> syntax -> examples) gives an implicit sequence, but there are no explicit validation or verification steps for the YAML being produced, and the rubric caps batch/file-generation skills without validation feedback loops at 3.

3 / 5

Progressive Disclosure

Sections are well-labeled and external doc links are present at the end, but the bulk reference material (full function tables, complete schema) is inlined rather than split into bundled reference files, and the no-bundle-files listing means there is no one-level-deep reference structure to navigate.

3 / 5

Total

12

/

20

Passed

Description

95%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 strong, concise description that clearly states capabilities and gives explicit, comprehensive trigger guidance with the file extension and natural synonyms. No significant weaknesses; it reads like the 5-anchor reference examples.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries'), naming the domain plus four specific feature areas, with only minor gaps relative to the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' (create and edit Bases with views, filters, formulas, summaries) and 'when' with a concrete 'Use when...' clause listing trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage including the file extension ('.base files'), the feature name ('Bases'), and synonyms/related phrasings users say ('table views, card views, filters, or formulas in Obsidian'), matching the 5 anchor.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Obsidian Bases / .base files) with distinct triggers and the qualifying 'in Obsidian', giving minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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