obsidian-skills-integrated

内容创作者与技术写作员在让AI撰写Obsidian笔记时，使用此官方技能可精准处理双链、Callout及Bases数据库语法，一键生成格式零破坏的Canvas画布与专业笔记，彻底解决AI破坏专属格式的痛点。

Quality

45%

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/SKILL.md

Quality

Content

25%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 body reads as a promotional integration report rather than an actionable skill: it is verbose with marketing fluff, offers prompt templates instead of executable guidance, and inlines all peripheral content with no reference files. It needs to be rewritten as concise, procedural, executable instructions for Claude.

Suggestions

Replace promotional sections (核心价值/核心优势/适用人群/预期收益) with concise, executable guidance: concrete syntax rules and example output for obsidian-markdown, json-canvas, and obsidian-bases.

Add real workflow sequences with validation checkpoints (e.g. validate .canvas JSON before writing, verify wikilinks resolve) instead of conceptual inter-skill pipelines.

Move peripheral material (comparison table, FAQ, maintenance/update commands) into separate reference files linked one level deep from a lean SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The ~255-line body is heavily padded with promotional sections — '核心价值', '核心优势', '适用人群', '预期收益' (claiming '效率提升10倍', '时间缩短90%') — plus GitHub-star and CEO-endorsement framing that Claude does not need; useful content is buried under marketing.	2 / 5
Actionability	The '快速使用' examples are user-prompt templates rather than executable guidance for Claude, and the per-skill sections list capabilities (e.g. `[[笔记名称]]`, `> [!INFO]`) without showing how Claude should apply or emit them; the only real commands are PowerShell update snippets in '后续维护'.	2 / 5
Workflow Clarity	The '工作流' sections are conceptual inter-skill pipelines (obsidian-markdown → article-illustrator → baoyu-post-to-wechat) with no sequenced steps or validation checkpoints, and the maintenance update flow lacks any verify step before replacing files.	2 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets are absent) and the entire document — comparison table, FAQ, maintenance, workflows — is inlined monolithically in SKILL.md with only header-level structure and external URLs, so content that belongs in separate files is not split out.	2 / 5
	Total	8 / 20 Passed

Description

66%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 specifies a clear Obsidian niche with several concrete capabilities and natural trigger terms, but it omits an explicit 'Use when...' clause and leans on marketing superlatives ('一键', '彻底'). Adding an explicit trigger clause and trimming hyperbole would raise completeness and specificity.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when generating or editing Obsidian notes, Canvas boards, or Bases databases where wikilink/Callout/frontmatter syntax must be preserved.'

Soften marketing absolutes like '一键生成' and '彻底解决' to concrete, verifiable actions.

Include file extensions (.md, .canvas, .base) and synonyms alongside the domain terms to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Obsidian domain and several concrete actions — '精准处理双链、Callout及Bases数据库语法', '一键生成...Canvas画布与专业笔记' — listing multiple specific capabilities, though '一键生成' and '彻底解决' add mild marketing padding rather than new actions.	4 / 5
Completeness	It clearly states what the skill does (handle wikilinks/Callouts/Bases, generate Canvas and notes) but has no explicit 'Use when...' trigger clause; the 'when AI撰写Obsidian笔记时' is only weakly implied, so per the missing-trigger-clause cap completeness stays at 3.	3 / 5
Trigger Term Quality	Includes natural domain terms an Obsidian user would actually say — 'Obsidian笔记', '双链', 'Callout', 'Canvas画布', 'Bases数据库' — giving good keyword coverage, though it omits file extensions (.md/.canvas/.base) and common synonyms.	4 / 5
Distinctiveness Conflict Risk	The Obsidian-specific triggers (双链, Callout, Canvas, Bases) carve a clear niche with minimal conflict risk; only minor overlap exists with generic markdown-formatting skills, and the broad '内容创作者与技术写作员' audience framing prevents a 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: anbeime/skill
Path: skills/obsidian-skills-integrated/SKILL.md
Commit: 0ca4f26

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