wiki-ingest

Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this URL, process this source, read and file this source, batch ingest, ingest these sources.

Quality

88%

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

Quality

Content

81%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-engineered, action-oriented body with strong workflow validation and feedback loops for a destructive/batch operation. The main gaps are a missing concrete transaction-bundle JSON example and external references that are not part of the skill bundle.

Suggestions

Add a minimal complete `claude-obsidian.transaction.v1` JSON example for an ingest bundle so the central artifact is copy-pasteable, not just described as a field list.

Tighten the untrusted-data and capture-maturity prose into scannable bullets to reduce token cost without losing the security directives.

Either bundle the referenced provenance/transaction contracts under ./references/ or note explicitly that they are external vault-owned files, so the reference targets are verifiable.

Dimension	Reasoning	Score
Conciseness	The body is dense and skill-specific (provenance contracts, transaction model, ledger rules) without explaining concepts Claude already knows, but several prose passages (e.g. the untrusted-data paragraph) could be tightened, so it sits at 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Copy-paste-ready bash commands (CORE resolution, transaction inspect/apply with approval SHA, checkpoint) and a numbered analysis sequence give concrete executable guidance; the central transaction bundle is specified as a bulleted field list rather than a full JSON example, a minor gap below the top anchor.	4 / 5
Workflow Clarity	A clear sequence (scope → analyze → provenance → build transaction → preview/apply/recover) with explicit validation (inspect before apply, SHA-256 approval) and feedback loops (exit 75 re-read/rebuild, transaction recover) matches the top anchor for destructive/batch workflows.	5 / 5
Progressive Disclosure	Sections are well-organized with clearly signaled one-level-deep references ('Read [the provenance contract](../wiki/references/provenance.md)'), but no bundle files exist and the referenced paths live outside the skill bundle, so navigation cannot be verified within the bundle — a minor organization gap.	4 / 5
	Total	17 / 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, well-structured description that explicitly covers what, when, and trigger phrases with a clear niche and boundary. Minor specificity gap versus the most comprehensive anchor only because the core action is essentially 'ingest' with supporting aspects.

Dimension	Reasoning	Score
Specificity	Names the domain ('Ingest supplied source material into an Obsidian vault with provenance and claim tracking') plus concrete sub-actions and an enumerated source-type list, matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive 5-anchor example.	4 / 5
Completeness	It clearly states what the skill does and explicitly answers when to use it ('Use for a single source or bounded batch, not for saving an assistant answer') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	An explicit 'Triggers:' clause lists seven natural user phrasings ('ingest this file', 'ingest this URL', 'process this source', 'read and file this source', 'batch ingest', 'ingest these sources'), giving comprehensive coverage of natural variations.	5 / 5
Distinctiveness Conflict Risk	The Obsidian-vault-with-provenance niche is distinct, and the explicit exclusion ('not for saving an assistant answer') plus dedicated triggers minimize overlap with other skills.	5 / 5
	Total	19 / 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
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-obsidian
Path: skills/wiki-ingest/SKILL.md
Commit: ad67087

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