zotero-obsidian-bridge

Use this skill when Zotero is the literature source of truth and the project KB should receive source notes under Sources/Papers plus project-linked synthesis in Knowledge and Writing.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zotero-obsidian-bridge/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-structured, actionable skill body with a clear gated workflow, held back mainly by poor alignment with its own bundle — detail is inlined and the existing reference/script files are not surfaced.

Suggestions

Move the Evidence Record schema and default flow detail into references/PAPER-NOTE-SCHEMA.md and references/WORKFLOW.md and link them from the body instead of inlining, to align progressive disclosure with the existing bundle.

Add an explicit validation step to the workflow instructing Claude to run scripts/verify_paper_notes.py after ingestion, with a fix-and-re-run loop on failure.

Replace or supplement the external ../research-ideation/references/research-contract.md pointer with the bundle-local reference paths (or confirm the contract path exists) so every reference resolves within the skill.

Dimension	Reasoning	Score
Conciseness	Mostly lean short rules and a compact Evidence Record template with no padding or explaining of concepts Claude already knows; a couple of sentences (the final synthesis-linking note) slightly overlap the Claim Promotion Gate and could be trimmed.	4 / 5
Actionability	Concrete folder paths, an explicit default flow, a copy-paste Evidence Record template, and named registry files make it mostly executable, but it leans on an external research-contract.md path and never surfaces the bundle's verify script.	4 / 5
Workflow Clarity	A clear ingest→notes→gate→synthesis→writing→canvas sequence with an explicit Claim Promotion Gate checkpoint, but the body never instructs running verify_paper_notes.py or defines an error-recovery loop.	4 / 5
Progressive Disclosure	The body has reasonable section structure, but schemas and flow detail that belong in references/ are inlined while the actual bundle files (PAPER-NOTE-SCHEMA.md, WORKFLOW.md, verify_paper_notes.py) are never linked, and the only reference points outside this bundle.	3 / 5
	Total	15 / 20 Passed

Description

73%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 distinctive, well-scoped description that clearly conveys both purpose and trigger conditions. Its main weakness is action specificity — it describes destinations more than concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain (Zotero↔KB bridge) and several concrete destinations (Sources/Papers, Knowledge, Writing) but the actions themselves are minimal and generic ('should receive', 'source of truth') rather than enumerated concrete actions.	3 / 5
Completeness	Both what (receive source notes under Sources/Papers plus synthesis in Knowledge/Writing) and when ('Use this skill when Zotero is the literature source of truth') are present, but the 'when' is a state rather than concrete user-said trigger phrases.	4 / 5
Trigger Term Quality	'Zotero', 'literature source of truth', and 'source notes' give good natural keyword coverage a user would actually say, though common synonyms and file-extension-style triggers are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche pairing Zotero with a specific Obsidian KB folder structure yields distinct triggers and minimal conflict risk with other skills.	5 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/zotero-obsidian-bridge/SKILL.md
Commit: 6ed46da

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