llm-wiki-kit

Unified entry point for ingesting any source (paste, URL, file, photo, transcript) into the vault. Routes on two axes — source-type (clean the input via the document/website/inline path) and content-type (apply schema and routing via a content-type primitive's ingester). Use whenever a user drops, pastes, or links any source for ingestion.

Run health checks on the vault. Combines structural checks (broken wikilinks, orphan pages, missing frontmatter fields, stale `modified` dates, tag synonyms, convergence debt in `raw/`, asset coverage) with semantic checks (contradiction detection across pages claiming the same fact). Use on request — "lint the wiki" / "check wiki health" — weekly or per-sprint, or after bulk ingestion of new raw sources.

Search the vault by content and frontmatter (--genre, --subtype, --tag, --status, --top). Returns ranked pages with title, genre, subtype, status, tags, and per-file match count — ready to read. Today's backend is ripgrep (literal substring, zero install); the SKILL was designed against a future SQLite FTS5 auto-upgrade tier (BM25, stemming, phrase/prefix) that has not yet shipped. Use for any *vault content* question; reserve the IDE's built-in Grep for regex, code search, or inspecting a known path.

Scan the vault for follow-up callouts (`> [!important] Follow-up due by YYYY-MM-DD`) and standalone `action-item` pages, then surface what's overdue and what's due in the next 60 days, grouped by owner and domain. Load when the user says "what follow-ups are due?", on a weekly sweep, or via `wiki run follow-up-tracker`. Writes one report page per run; pairs with `medical-summary` (which produces visit-specific summaries) and the content-type ingesters that emit the callouts in the first place.

Ingest a decision source (meeting decision callout, email thread that landed on a choice, written rationale or short ADR-style doc) into a structured decision page. Load from the `ingest` skill when content-type routing identifies the source as a durable choice with context, alternatives, and consequences — distinct from a meeting (which captures *what happened*) or a stakeholder-update (which captures *what to communicate*). Produces one page under `wiki/library/`, links the owner to `wiki/people/`, and is read by downstream operations (status-synthesis, onboarding-pack).

Ingest a meeting source (transcript, notes paste, recording link) into a structured meeting page. Load from the `ingest` skill when content-type routing identifies the source as a meeting (calendar invite text, transcript turns, agenda+notes shape). Produces one page under `wiki/library/`, links attendees to `wiki/people/`, and registers decisions and follow-ups for downstream operations (weekly-digest, follow-up-tracker).

Ingest a trip booking confirmation (hotel, flight, rental car, activity reservation) into a structured `trip-doc` page in the trip's container folder `efforts/trips/<slug>/`. Load from the `ingest` skill when content-type routing identifies the source as a booking (confirmation email, PDF, or web page). Aggregates: a single trip typically gets several runs — each new booking appends to the same trip page. Pairs with the `trip-prep` operation (which writes packing + pre-departure tasks back to the same page 2-3 weeks before departure).

Produce a weekly family meal plan with shopping list, reading the recipe pages in `library/` (`--subtype recipe`), the dietary-notes reference page, last week's plan, and family calendar context if available. Load when the user asks for a weekly plan or to plan-meals, when `wiki run meal-planning` invokes you, when `/plan-meals` fires from Claude Code's slash palette, or on a scheduled Sunday sweep. Writes one page to `outputs/meal-plans/<window>.md`; idempotent for a given window. For ad-hoc "what's for dinner tonight?" use a recipe recommendation skill instead — this operation is the weekly cadence.

Assemble a per-person packing list and a pre-trip task checklist for an upcoming trip, reading the trip page, family member pages, past trip pages for lessons learned, and any relevant medical pages for medications and special needs. Load when the user says "prep for the {trip} trip" / "what should we pack?", or when `wiki run trip-prep <trip>` runs you. Writes back to the trip page itself under `## Packing list` and `## Pre-trip tasks` sections — augments rather than creating a separate page. For booking capture use `ingest-trip-doc`.

Produce one weekly digest page summarizing meetings (and later, other content-types) inside an ISO-week window. Load when the user asks for "the digest", "last week's summary", or "what happened this week", when `wiki run weekly-digest` invokes you, when `/digest` fires from Claude Code's slash palette, or on a scheduled sweep. Writes one page to `outputs/digests/<window>.md`; idempotent for a given window — re-running overwrites the same page rather than producing a new one.

Ingest a medical document (visit summary, EOB, lab result, prescription note) into a `medical-record` capture page in `wiki/library/`, append a dated entry to the patient's case overview under `wiki/efforts/cases/`, and update the patient's medications page and providers. Load from the `ingest` skill when content-type routing identifies the source as medical (clinic or insurer letterhead, EOB layout, lab-result format). Pairs with the `medical-summary` operation (visit prep) and `follow-up-tracker` (recheck reminders).

Ingest a receipt (photo, PDF, statement entry, emailed receipt) into a structured `receipt` page and route the contents to the right domain — vehicle service history, appliance warranty tracking, vendor service log, tax-relevant expense list. Load from the `ingest` skill when content-type routing identifies the source as a receipt. Stubs vendor pages under `wiki/people/` on first reference.

Ingest a tax form (W-2, 1099-DIV/INT/B/MISC/NEC, 1098, K-1, 5498, 1095-*, brokerage year-end statement, tax-prep summary) into a structured `tax-document` page under `wiki/library/{year}/`. Load from the `ingest` skill when content-type routing identifies the source as a tax form (issuer letterhead, prominent form number). Critical: redacts SSNs before writing; the raw PDF stays in `raw/tax/`.

Produce a current-state medical summary for a person — active conditions, current medications, allergies, recent visits, outstanding follow-ups — suitable for a doctor visit, school form, or emergency reference. Load before a provider visit (especially a new specialist), for annual physical prep, when a form requires medical info, or via `wiki run medical-summary <person>`. Writes one versioned page per run; pairs with the `medical-record` ingester (which produces the input data) and the `follow-up-tracker` (which surfaces rechecks).

Roll up open action items across meeting follow-ups, stakeholder-update asks, customer-feedback follow-ups, and interview follow-ups into one owner-grouped digest. Load when the user asks 'what does <owner> have on their plate?', when `wiki run action-item-rollup` invokes you, or on a scheduled weekly sweep. Writes one page to `outputs/action-items/<window_end>.md`; re-running the same window overwrites the same page.

Ingest a customer-feedback source (support ticket, sales call note, survey response, NPS comment, churn-call summary, in-app feedback) into a structured customer-feedback page. Load from the `ingest` skill when content-type routing identifies the source as customer-originated commentary on the product, the relationship, or a recent experience. Produces one page under `wiki/library/`, links the customer to `wiki/people/`, the contact (if a named individual) to `wiki/people/`, and registers the page for downstream operations (status-synthesis, onboarding-pack).

Ingest an interview source (recording transcript, written notes, recorded-call summary) into a structured interview page. Load from the `ingest` skill when content-type routing identifies the source as a scheduled, structured conversation with a defined research goal — user research, customer-discovery, hiring, win-loss. Produces one page under `wiki/library/`, links the subject to `wiki/people/`, and registers the interview for downstream operations (status-synthesis, action-item-rollup).

Ingest a stakeholder-update source (status email, slide bullets, paste from a doc) into a structured stakeholder-update page. Load from the `ingest` skill when content-type routing identifies the source as a project status update — typically a short narrative addressed to a named audience with highlights/risks/asks structure. Produces one page under `wiki/library/`, links the project to `wiki/efforts/projects/`, audience members to `wiki/people/`, and registers the page for downstream operations (status-synthesis, action-item-rollup).

Ingest a vendor-contract source (signed contract PDF text, renewal notice, procurement summary, or order form) into a structured vendor-contract page. Load from the `ingest` skill when content-type routing identifies the source as a vendor contract — typically a counterparty name, a term window, an amount, and signed/effective dates. Produces one page under `wiki/library/` and registers the contract for downstream operations (renewal-reminders).

Produce a one-page onboarding briefing for a newcomer joining a customer or project. Load when the user asks 'brief me / brief X on the apollo project' or 'put together an onboarding pack for the acme account', when `wiki run onboarding-pack` invokes you with a `scope:` argument, or when a new team member joins. Writes one page to `outputs/onboarding/<scope>.md`; re-running on the same scope overwrites — the pack is meant to stay current.

Surface vendor contracts with a renewal date inside a configured look-ahead window, plus any open-ended contracts that have no end date. Load when the user asks 'what's coming up for renewal?', when `wiki run renewal-reminders` invokes you, or on a scheduled monthly sweep. Writes one page to `outputs/renewals/<run_date>.md`; re-running on the same date overwrites.

Produce one stakeholder-map page per project, listing the audience members who receive updates plus their cadence. Load when the user asks 'who's on the distro for project X' or to refresh-stakeholders, when `wiki run stakeholder-map-refresh` invokes you, when `/refresh-stakeholders` fires from Claude Code's slash palette, or on a scheduled monthly sweep. Writes one page per project to `outputs/stakeholder-maps/<project>.md`; idempotent per project — re-running overwrites the same page rather than producing a new one.

Produce a cross-project status snapshot for an ISO-week window by walking stakeholder-updates, decisions, and customer-feedback. Load when the user asks 'what's the state of the world this week?', when `wiki run status-synthesis` invokes you, or on a scheduled weekly sweep. Writes one page to `outputs/status/<window>.md`; re-running the same window overwrites. Distinct from `weekly-digest`, which is meeting-centric — `status-synthesis` is project / customer / decision-centric.

Promote a follow-up — pasted by the user, extracted from a meeting transcript, or surfaced from a medical record — into a standalone `action-item` page under `wiki/library/`. Load when the user says "track this as an action", "make this its own task", or wants to promote a one-line follow-up to a page that can accumulate updates. Most follow-ups stay inline on their source page; this skill is for the ones that don't.

Ingest a recipe from a URL, photo, scan, or pasted text into a structured page under `wiki/library/`. Load from the `ingest` skill when content-type routing identifies the source as a recipe (food-blog or recipe-site URL, photo of a card, ingredient+instructions shape in pasted text). Output is one page using the `_templates/recipe.md` schema, cross-linked to `wiki/library/dietary-notes.md` for per-person allergen flags. Pairs with the `meal-planning` operation, which reads the library.

Use this skill when the user asks to propose, draft, or open an RFC (request for comments). Triggers on "RFC", "propose a change to…", "let's get input on…", "draft a proposal". Do NOT use for already-decided things (use `new-adr`) or single-feature specs (use `new-spec`).

Use this skill whenever you're implementing a non-trivial change — a feature, a multi-file bug fix, a refactor, a migration, a framework or dependency upgrade, a schema or API change, performance work, an infrastructure or build-system edit, or anything spec-driven. It enforces the project's plan → execute → self-review → fix loop with mechanical gates (lint, typecheck, tests) and adversarial review. Default to this skill for any task larger than a one-line edit.

Use this skill when the user wants to fix a defect — a deviation between current behavior and intended behavior in existing code. Triggers on "fix bug", "fix this bug", "diagnose and fix", "investigate this regression", "this is broken", "crash", "wrong output", "perf regression". For defect-shaped tasks that touch more than one file. Do NOT use for new features (use `new-spec`) or refactors unrelated to fixing incorrect behavior.

Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build. Triggers on "new spec", "write a spec for X", "let's spec this out", "start a feature for…". Spec-driven development; the spec drives implementation. Do NOT use for cross-cutting proposals (use `new-rfc`) or recording decisions (use `new-adr`).

Progressive-disclosure security-depth modules for the security-reviewer. Holds ten boundary-keyed checklists (access-control, authn-session, injection, path-and-file, secrets-and-crypto, outbound-ssrf, supply-chain, config-misconfig, exceptional-conditions, llm-agent) as references/, each anchored on a current standard (OWASP Top 10:2025, ASVS 5.0, API Security Top 10:2023, Proactive Controls 2024, CWE Top 25, OWASP LLM Top 10:2025). The work-loop's orchestrator loads only the boundary-matching modules and inlines them into the security-reviewer's brief; the subagent never self-discovers this skill. Not a reviewer prompt itself — it is the depth library the reviewer reasons from.

Use this skill when the user asks to create, write, draft, or open a new ADR (architecture decision record). Triggers on phrases like "new ADR", "write an ADR for…", "record this decision", "let's ADR this". Do NOT use for RFCs (use `new-rfc`) or feature specs (use `new-spec`).

First-run wizard for fresh vaults. Load whenever the user signals they're new to this vault — 'I just made a new vault, help me get started', 'this is my first time using this vault', 'what should I do first', 'walk me through this vault', or any onboarding-shaped phrase along those lines. The wizard reads the journal to learn the recipe, walks the installed outcome verbs from `wiki outcomes`, glosses one verb by reading its underlying skill's SKILL.md (read-only — never invokes `wiki <verb>`), and writes a one-byte sentinel at `<vault>/.wiki.bootstrap` so later sessions short-circuit to a brief no-op. Recipe-agnostic — works against `personal`, `family`, `work-os`, or any future recipe.

Help the user install, rebind, or stop using an agent — the `kind: agent` primitive that the kit passes via `claude --agent <name>` at scheduled-run time. Load this skill whenever the user names an agent ("the household-manager", "who runs my weekly digest", "why is `--agent` missing"), or when `wiki agents` / `wiki schedule list` / `wiki doctor` surface an agent binding the user wants to change. The kit ships eight default agents under three recipes; this skill bridges between what the user wants ("a different voice for my Sunday digest") and the verbs that effect it (`wiki add agent:<name>`, `wiki schedule install <op> --agent <name>`, and the v1 manual `rm -r <vault>/.claude/agents/<name>/` for removal until the dedicated `wiki remove` verb ships).

Resolve `<path>.proposed` sidecar conflicts. The kit writes a sidecar when it tried to update a file the user had already edited — it never clobbers. This skill walks through reconciling the on-disk version with the proposed update, then commits the merged result through `wiki resolve` so the journal regains a clean baseline. Use whenever a `.proposed` sidecar appears, or whenever `wiki doctor` reports pending proposals.

Produce a fixture digest. Reach for this skill when the user says "prep-digest" or invokes /prep-digest. Used only by PR-3 tests.

Synthetic SKILL that intentionally does NOT name its outcome verb, so the install-time SKILL-fragment validator surfaces a WikiError.

Dispatch a research query to a configured HTTP research provider via `wiki research`. Picks among Perplexity (current-state web), Semantic Scholar (peer-reviewed literature), and Gemini Deep Research (long-form synthesis) based on the question shape and what's installed in research-providers.yaml at the vault root. Writes the markdown answer to stdout or via `--out` to a vault path under drift detection. Load whenever the user asks for external information the vault doesn't already have.

Validate vault state against the journal. Replays the journal, computes the expected on-disk set, and reports drift — orphan files (on disk but not in the journal), missing files (in the journal but not on disk), managed-region damage (markers deleted or misaligned), pending proposals, stale locks, and uninstalled-but-referenced primitives. Use to diagnose "something feels off" symptoms, after a manual edit, after a git merge, or whenever the user asks "is the vault healthy?".

Coordinate concurrent writes to the vault. Acquire the lock before starting a multi-file operation (a digest, a re-sync, a bulk ingest, an operation run) so two agents working on the same vault at the same time don't trample each other. Load this skill whenever a workflow will write more than a single page, or when running a `wiki run <operation>`.

Use this skill when the user wants to substantively change `docs/CONVENTIONS.md` — modify how the team works in this repo. Triggers on "change the convention for…", "update the rules", "amend our process", "let's revise how we do X". Substantive convention changes go through RFC review, not a direct PR. Typo and broken-link fixes don't count — those land as normal PRs.