vault-provenance

Classify factual claims in a vault note and back-fill epistemic status frontmatter.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/DoctorMozg/claude-pipelines --skill vault-provenance-doctormozg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-provenance
Source: https://github.com/DoctorMozg/claude-pipelines/tree/main/plugins/mz-knowledge/skills/vault-provenance
Command: npx skills add https://github.com/DoctorMozg/claude-pipelines --skill vault-provenance-doctormozg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Notes in a knowledge vault often mix first-hand observations, cited findings, and received wisdom without any record of where each claim came from, making it impossible to audit trustworthiness later. This Skill classifies every factual claim in a single note against a five-value epistemic vocabulary and writes the results into the note's frontmatter after explicit user approval. ## Core Features & Use Cases - Per-claim epistemic classification: Extracts declarative factual claims (up to 25 per note) and labels each as first-hand, cited, inferred, received, or unmarked, with confidence and reasoning. - Approval-gated frontmatter back-fill: Presents the full claims analysis for review, then patches epistemic_status: and sources: frontmatter only after explicit approval, preserving the note body verbatim. - Aggregate status with 60% majority rule: Derives a note-level epistemic status, falling back to mixed with a single HTML comment pointer when no status dominates. - Use Case: After drafting a research note, run the audit to discover which claims lack sources, approve the classification, and have the note's provenance frontmatter written automatically before promoting it to evergreen. ## Quick Start Ask the assistant to classify the claims and back-fill provenance sources for a specific note by giving its name or path.

Frequently Asked Questions about vault-provenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit the provenance of claims in a note?

Invoke the skill with the note's name or path. It extracts declarative factual claims, classifies each as first-hand, cited, inferred, received, or unmarked, and presents the full analysis for your approval before writing any frontmatter.

How does epistemic status classification work for knowledge notes?

Each claim is matched against a closed five-value vocabulary: first-hand, cited, inferred, received, or unmarked. The classifier cites the exact triggering phrase, proposes sources from in-body citations and wikilinks, and records a confidence level with reasoning.

Does the skill modify the note body when back-filling sources?

No, the default is frontmatter-only: only the epistemic_status and sources keys are patched, and the body stays byte-for-byte identical. Inline HTML comment annotations are added only if you explicitly opt into annotation mode during the approval step.

Can I run a provenance audit across my entire vault at once?

No, the scope is strictly per-note by design. Vault-wide audits, schema compliance checks, and link suggestions are explicitly out of scope and handled by other skills such as vault-schema or vault-connect.

What happens if a note has more than 25 claims?

Only the first 25 claims are classified, and the cap is flagged in the summary via the capped field. This hard limit keeps the classification artifact reviewable in a single approval pass.

What if the note has no YAML frontmatter?

The skill halts and asks whether to create a frontmatter block or abort. It never fabricates a frontmatter block without explicit user approval.