Fully autonomous end-to-end ingestion of a SINGLE source (book, paper, article, transcript) into the knowledge base - prepare to markdown, extract insights against the live index, refresh the index, auto-link to existing knowledge, and changelog. One source per invocation.
Standard format for capturing and documenting insights in the knowledge base. Use when harvesting insights, creating permanent notes from user perspectives, or documenting unique thinking patterns.
KB-grounded Socratic interview. Searches existing notes on a topic, then runs a one-question-at-a-time dialogue to surface, sharpen, and extract your own thinking. Ends by running extract-insights on the full conversation transcript.
Upsert and maintain entity notes in a REFERENCE-kind scope (external facts/records), then reindex so they become connection/insight targets. Generic across reference scopes; Company is the default. The scope's entity taxonomy (type/relationship) lives in that scope's own schema doc (Company's is…
Manage domain-watch surveillance configs — seed new domains, review scan status and proposals, activate Watch Log proposals into thinking topics, pause domains, and update PIRs or watch queries.
Extract chapters from PDF, MOBI, and AZW3 book files into individual markdown files. Use when extracting non-EPUB books. PDF uses pymupdf with TOC-based chapter splitting and auto-OCR fallback (Gemini) for scanned/image-only PDFs; MOBI/AZW3 routes through calibre then epub-chapter-extractor.
Generate images using Google's Nano Banana (Gemini 2.5 Flash Image). Use when creating infographics, diagrams, thumbnails, social media graphics, or any AI-generated images. Costs $0.039/image.
Integrity report for a reference scope — the reference-scope analog of /coherence-sweep. Scans every entity note for provenance violations (any note not provenance:reference), type/relationship enum violations, missing/invalid asof, status/supersededby integrity, dangling wiki-links, orphan entities, and…
Bridge reference entities to the cognitive knowledge base — "this client maps to that insight you had." A thin mode over connection-finder that mounts core,Company/ and surfaces entity↔insight bridges, making the reference scope more than a CRM. READ-ONLY sense — it surfaces candidate bridges for human consideration…
The single entry point for incoming information of ANY kind about a reference entity (a person, org, product, engagement, or watched competitor). Extracts entity facts, RESOLVES them to the one existing canonical note (never duplicating), reconciles new-vs-old, and upserts (overwrite body, re-stamp asof, append Change…
Structured, temporal lookup against a reference scope — "what do we know about Acme Corp as of today?", "which engagements are active and expiring in 90 days?", "list our competitors". Respects status (active over superseded), validity windows, and asof freshness, and ALWAYS prints the asof date so staleness is…
Keep a reference scope canonical and internally consistent. SENSE phase (auto) detects issues by invoking ref-audit; FIX phase (human-gated) resolves conflicts, repairs bidirectional link integrity (A cites [[B]] as client → does B back-link?), fixes/removes dangling links, and MERGES duplicate entities into one…
Mechanical staleness sweep over a reference scope. Scans every note's asof age against the per-type Freshness SLA, builds an overdue-sorted refresh queue, then splits by scope — market/ stale items are handed to ref-ingest (the gate-free overwrite branch) for autonomous re-verification; CRM stale items are report-only…
Handle a validity transition on a reference entity — a contract renewal, role change, or re-termed price where a full prior snapshot matters. Creates the new status:active note (with validfrom/validuntil), marks the old note status:superseded + supersededby:[[New]], keeps both for history, and reindexes. Human-gated.…
Quick search across Obsidian vault using keywords or semantic similarity.
★not rated 106▲
+2 14d agoA16 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: