obsidian-bases

内容创作者与技术写作员在管理海量笔记时，当需要构建 Obsidian 数据库视图、配置过滤器或编写 YAML 公式，使用此技能可自动生成标准 .base 文件，轻松实现笔记的表格/卡片多维展示与数据汇总，让知识库管理效率翻倍。

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/obsidian-skills-integrated/obsidian-bases/SKILL.md

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

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.

The content is a comprehensive, highly actionable reference for the Obsidian Bases format with excellent copy-paste examples, but it is a monolithic ~650-line document that inlines material (function reference, full examples) better suited to separate bundle files and omits validation checkpoints for the error-prone YAML/formula authoring it describes.

Suggestions

Move the exhaustive Functions Reference and the Complete Examples into separate bundle files (e.g., references/functions.md, references/examples.md), leaving SKILL.md a concise overview with clearly signaled one-level-deep links to improve progressive disclosure.

Add an explicit validation checkpoint (e.g., 'Verify the .base file renders in Obsidian and check the Bases view for formula errors before finalizing') to raise workflow clarity for the error-prone authoring process.

Remove the redundant 'Common Patterns' filter examples that duplicate 'Filter Syntax' to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is reference-dense and avoids explaining concepts Claude already knows, but at ~650 inlined lines it is noticeably long, and the 'Common Patterns' section re-demonstrates filters already shown in 'Filter Syntax', so it could be tightened substantially.	3 / 5
Actionability	It provides complete, copy-paste-ready .base file examples (Task Tracker, Reading List, Project Notes, Daily Notes) plus exhaustive function signatures with signatures and descriptions, fully covering the common cases.	5 / 5
Workflow Clarity	This is a single-purpose format skill with no explicit multi-step sequence, and it lacks any validation/verify checkpoint for error-prone YAML and formula syntax (only a partial Duration WRONG/RIGHT note), leaving validation gaps.	3 / 5
Progressive Disclosure	Section headers and external Obsidian reference links give it structure, but the exhaustive function-reference tables and four full examples are inlined in SKILL.md with no local bundle files, where splitting into reference files is clearly warranted.	3 / 5
	Total	14 / 20 Passed

Description

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

The description clearly conveys both the skill's purpose and explicit trigger conditions with concrete, domain-specific actions, scoring solidly above midpoint across all dimensions. It is held back from the top anchor by marketing puffery ('效率翻倍', '轻松') and a slightly verbose, run-on trigger clause.

Suggestions

Trim marketing fluff such as '轻松实现' and '让知识库管理效率翻倍' to tighten the specificity and avoid over-claims.

Lead with a crisp 'Use when…' trigger clause (e.g., 'Use when building Obsidian database views, configuring filters, or writing YAML formulas for .base files') instead of burying the trigger mid-sentence.

Add a few synonym/extension variants (e.g., 'Bases', '.base', 'note databases') to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (构建数据库视图, 配置过滤器, 编写 YAML 公式, 自动生成 .base 文件, 表格/卡片展示, 数据汇总), approaching comprehensive coverage, but marketing fluff like '效率翻倍' and '轻松实现' pads it slightly below a 5.	4 / 5
Completeness	It explicitly answers both 'what' (auto-generate .base files with views/filters/formulas/summaries) and 'when' (当需要构建…配置…或编写…时，使用此技能), but the trigger clause is somewhat verbose and buried rather than crisp, placing it between 3 and 5.	4 / 5
Trigger Term Quality	Natural domain keywords a user would say are present (Obsidian 数据库视图, 过滤器, YAML 公式, .base 文件, 笔记), with good coverage but a few synonyms and extension variants missing, fitting the 4 anchor.	4 / 5
Distinctiveness Conflict Risk	Obsidian Bases is a clear niche with .base-specific triggers, giving minimal conflict risk; minor overlap remains with generic note/knowledge-base management skills, so it does not reach a 5.	4 / 5
	Total	16 / 20 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 (652 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: anbeime/skill
Path: skills/obsidian-skills-integrated/obsidian-bases/SKILL.md
Commit: d9e888d

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