obsidian-vault-report

Generate synthesis reports from the Obsidian vault corpus. Use when user says "write a report", "research paper", "strategy doc", "synthesize", "what does our vault say about X", or any request to analyze and combine knowledge from existing vault notes into a new document.

Quality

78%

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 ./.github/skills/obsidian-vault-report/SKILL.md

Quality

Content

71%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 well-organized, actionable skill body with a concrete pipeline and an excellent copy-ready report template. Its main flaws are a large bundled script that is never surfaced or navigable from SKILL.md, and absent validation checkpoints around the MOC registration step.

Suggestions

Add a section (e.g., 'Script Usage') in SKILL.md documenting scripts/report.py — its purpose, example invocations from its docstring, and when to run it versus doing the pipeline manually — so the bundle's main asset is discoverable.

Add a validation checkpoint to the pipeline (e.g., verify the saved report exists, its wikilinks resolve to real notes, and the Master MOC Reports section was updated correctly) to close the workflow-clarity gap.

Trim or compress the 'Related Skills' and boilerplate 'Step N: Reflection' sections to their essential links to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The ~110-line body is efficient — trigger table, terse pipeline steps, template, quality bar — with no explanation of concepts Claude already knows; only minor sections (Related Skills, the composable Reflection boilerplate) could be trimmed, which is anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	The pipeline, exact paths (Research/Reports/, MOC section), wikilink conventions, and complete copy-ready report template give mostly executable guidance; the notable gap is that the bundled 991-line scripts/report.py is never mentioned as an execution path, holding it at anchor 4.	4 / 5
Workflow Clarity	The 7-step SEARCH→REGISTER pipeline is clearly sequenced with concrete targets per step, and the operations are additive (new report file, MOC section) so the destructive-cap does not apply; it stops short of anchor 5 because there are no validation checkpoints (e.g., verifying the MOC update or that wikilinks resolve).	4 / 5
Progressive Disclosure	The body itself is well-sectioned and self-contained, but the bundle's only asset — scripts/report.py, a complete alternative implementation — is entirely unreferenced by SKILL.md, leaving the skill's largest resource undiscoverable; that buried reference fits anchor 3 (references present but not clearly signaled) rather than anchor 4.	3 / 5
	Total	15 / 20 Passed

Description

86%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 description with explicit what/when structure and outstanding natural trigger phrases. Its only weaknesses are a somewhat thin action list and trigger phrases broad enough to slightly overlap sibling vault skills.

Dimension	Reasoning	Score
Specificity	"Generate synthesis reports from the Obsidian vault corpus" names the domain and one to two concrete actions (generate, analyze and combine), matching anchor 3; it is not anchor 4 because it does not list several distinct specific actions the way "extracts text, fills forms, converts pages" does.	3 / 5
Completeness	It explicitly answers both "what" ("Generate synthesis reports from the Obsidian vault corpus") and "when" ("Use when user says…") with a list of concrete trigger phrases, mirroring the anchor-5 example structure exactly; without the explicit trigger list it would drop to 4.	5 / 5
Trigger Term Quality	The quoted phrases — "write a report", "research paper", "strategy doc", "synthesize", "what does our vault say about X" — are exactly the natural phrasings a user would say, with synonym-level coverage and no meaningful terms missing for this domain.	5 / 5
Distinctiveness Conflict Risk	The vault-synthesis niche is distinct and "what does our vault say about X" is a unique trigger, but broad phrases like "write a report" and "research paper" carry minor overlap risk with closely related sibling skills (e.g., obsidian-linked-research), placing it at anchor 4 rather than 5.	4 / 5
	Total	17 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: 0xRabbidfly/Eric-Cartman
Path: .github/skills/obsidian-vault-report/SKILL.md
Commit: aa16c9e

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