By doctormozg
Personal Obsidian knowledge base skills and agents — vault maintenance, note processing, review, link suggestions, and Obsidian syntax reference
npx claudepluginhub doctormozg/claude-pipelines --plugin mz-knowledgePipeline-only agent dispatched by process-notes. Reads raw note content, detects atomic boundaries, and drafts complete note content with claim-style titles and status:draft frontmatter. Never user-triggered.
Pipeline-only agent dispatched by vault-ingest. Invokes the right transcription or OCR tool for a captured modality (voice, image, PDF, YouTube), cleans the output, and writes a single transcript artifact. Never user-triggered.
Pipeline-only agent dispatched by process-notes and vault-connect. Searches vault for existing notes that should be linked to or from target notes. Produces typed relationship proposals. Never user-triggered.
Pipeline-only agent dispatched by vault-review. Scans vault for topic clusters lacking Maps of Content (MOCs). Uses tag+folder+title clustering to detect coverage gaps. Writes moc_gaps.md artifact. Never user-triggered.
Pipeline-only. Classifies every factual claim in a single vault note against a five-value provenance vocabulary and proposes source attributions.
Pipeline-only agent dispatched by vault-schema. Validates every note frontmatter in an Obsidian vault against a YAML DSL declaration at `.mz/vault-schema.yml` and emits severity-labeled findings. Never user-triggered.
Pipeline-only. Applies heuristic scoring rules to fleeting inbox notes and proposes promote/merge/discard/defer decisions with one-sentence rationales.
Pipeline-only collector agent dispatched by vault-health. Scans an Obsidian vault for orphan notes, broken wikilinks, stub notes, stale notes, and tag statistics. Writes structured audit_data.md. Never user-triggered.
Pipeline-only. Answers user questions using only vault content, cites every factual claim with inline [[wikilinks]], and explicitly surfaces claims the vault does not support.
Pipeline-only scanner agent dispatched by vault-refactor. Enumerates every reference to a given note across an Obsidian vault — covering every OFM wikilink form, quoted YAML frontmatter wikilinks, and Bases link() formulas. Writes a structured references_report.md. Never user-triggered.
Pipeline-only writer agent dispatched by vault-refactor. Applies a precomputed list of per-reference replacements to vault files via targeted Edit calls. Refuses to proceed if the rollback manifest is missing. Never user-triggered.
ALWAYS invoke when finding missing wikilinks for a note, suggesting connections between notes, discovering which vault notes should link to the current note, or improving a note's link density. Triggers: link notes, suggest wikilinks, find connections, improve link density.
ALWAYS invoke when auditing an Obsidian vault for orphan notes, broken links, stale content, stub notes, or tag inconsistencies. Triggers: vault audit, orphan notes, broken wikilinks, vault health check.
ALWAYS invoke when capturing voice memos, screenshots, PDFs, YouTube videos, or images into the vault as fleeting notes. Triggers ingest audio, transcribe voice, capture screenshot, ingest PDF, capture YouTube.
ALWAYS invoke when classifying epistemic status of claims in a note, back-filling sources frontmatter, or auditing a note's knowledge provenance. Triggers: epistemic status, provenance, claim sources, mark claims.
ALWAYS invoke when renaming a vault note, moving a note to a different folder, or refactoring wikilink references across the vault. Triggers: rename note, move note, vault refactor, update wikilinks.
ALWAYS invoke when injecting a research report or brainstorm report from .mz/research or .mz/reports into the vault as atomized notes. Triggers: ingest research, import report, atomize report, research to notes.
ALWAYS invoke when starting a knowledge review session, surfacing notes to review, checking which notes are due for review, or running the weekly/monthly review ritual.
ALWAYS invoke when validating vault frontmatter schema, migrating vault notes to a new schema, or checking note-type frontmatter compliance. Triggers: vault schema, frontmatter validation, schema migration.
ALWAYS invoke when triaging inbox fleeting notes in a fast batch with promote/merge/discard/defer decisions. Triggers: triage inbox, fleeting review, clear inbox, batch decide.
ALWAYS invoke when working with Obsidian Bases (.base files), database views, filters, formulas, or the Bases query language. Triggers: .base file, Bases view, filter formula, vault database.
ALWAYS invoke when using the obsidian CLI tool to interact with a vault from the terminal. Triggers: obsidian CLI, vault command line, obsidian read/create/search from shell.
ALWAYS invoke when bootstrapping a new Obsidian vault with CLAUDE.md, folder structure, schema, and rules. Triggers init vault, bootstrap obsidian, setup knowledge base, create vault structure.
ALWAYS invoke when working with Obsidian vault .md files. Triggers: wikilinks, callouts, embeds, frontmatter properties, Obsidian Flavored Markdown, OFM syntax.
ALWAYS invoke when processing fleeting notes into permanent atomic notes, atomizing long notes, running the fleeting-to-permanent pipeline, or converting raw captures into vault-ready notes.
ALWAYS invoke when asking a question that should be answered from vault notes with inline wikilink citations. Triggers: what does my vault say about, answer from notes, search my vault for, grounded answer.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Create and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Memory compression system for Claude Code - persist context across sessions
Intelligent prompt optimization using skill-based architecture. Enriches vague prompts with research-based clarifying questions before Claude Code executes them
No description provided.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Multi-agent plugins for Claude Code. Autonomous development pipelines, code review, deep research, and business intelligence — all as slash commands.
[!TIP] Skills compose. Most real tasks span 3–4 commands across multiple plugins — chain them end-to-end instead of reaching for any single skill in isolation. Click any workflow below to see the flow.
mz-dev-base + mz-dev-pipeflowchart LR
A["/deep-research"]:::base --> B["/build"]:::pipe
B --> C["/verify"]:::pipe
C --> D["/review-branch"]:::base
classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/deep-research — survey trade-offs, cite references, pick an approach/build — research → plan (approval gate) → parallel code → review → test/verify — lint + types + tests + coverage, diagnose failures/review-branch — independent final pass before opening the PRmz-dev-pipeflowchart LR
A["/debug"]:::pipe --> B["/blast-radius"]:::pipe
B --> C["/investigate"]:::pipe
C --> D["/polish"]:::pipe
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/debug — reproduce → regression test → diagnose → fix → verify/blast-radius — map every caller, test, and type at risk of the patch/investigate — prove or disprove "does the same race exist on the refund path" without touching code/polish — fix-test-review loop until the criteria are metmz-dev-base + mz-dev-pipeflowchart LR
A["/init-rules"]:::base --> B["/explain"]:::pipe
B --> C["/audit"]:::pipe
C --> D["/blast-radius"]:::pipe
classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/init-rules — install curated coding rules for the detected languages/explain — multi-angle walkthrough with Mermaid diagrams of the module/audit — ranked list of landmines and tech-debt hotspots/blast-radius — know what shatters before the first refactor commitmz-dev-pipe + mz-dev-baseflowchart LR
A["/audit"]:::pipe --> B["/investigate"]:::pipe
B --> C["/debug"]:::pipe
C --> D["/review-branch"]:::base
classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/audit — prioritized vulnerabilities with file:line evidence/investigate — verify top critical findings, drop false positives/debug — TDD-style fix anchored on a regression test/review-branch — catch any fallout the fix introduced elsewheremz-creative + mz-design + mz-dev-pipe 3 pluginsflowchart LR
A["/brainstorm"]:::creative --> B["/expert"]:::creative
B --> C["/design-document"]:::design
C --> D["/build"]:::pipe
classDef creative fill:#fbefff,stroke:#8250df,color:#8250df
classDef design fill:#ffebf0,stroke:#bf3989,color:#bf3989
classDef pipe fill:#dafbe1,stroke:#1a7f37,color:#1a7f37
/brainstorm — 5 lens personas → parallel ideation → vote-to-consensus/expert — Delphi critique (3 rounds) with dedicated report writer/design-document — draft → 4-critic loop → WCAG 2.2 AA hard gate/build — plan → code → review → test against the approved specmz-biz-outreach + mz-dev-base + mz-creative 3 pluginsflowchart LR
A["/lead-gen"]:::outreach --> B["/deep-research"]:::base
B --> C["/brainstorm"]:::creative
classDef outreach fill:#fff1e5,stroke:#bc4c00,color:#bc4c00
classDef base fill:#ddf4ff,stroke:#0969da,color:#0969da
classDef creative fill:#fbefff,stroke:#8250df,color:#8250df
/lead-gen — strategy → source research → scout → enrich → score → report/deep-research — domain context to ground outreach in current regulation/brainstorm — multi-lens positioning ideas tied back to the lead-gen reportmz-dev-pipeOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim