Use when asked to work through, apply, resolve or review a template update pull request (the weekly copier/update branch opened by the copier-update workflow), or after running copier update --trust by hand: applies the upgrade notes, resolves conflict markers by the resolution policy, checks the seeded-once files the…
Use when filing a bug, opening or creating a GitHub issue, drafting an epic or ticket, writing up a finding or review observation worth tracking, or opening a pull request for this repository. Routes the change to the right repo first (library / template / domain), picks the right issue form, links epic children as…
Use before opening a pull request, marking one ready for review, or pushing further commits to a branch with an open pull request — or when asked to review a diff or a PR. Reviews the cumulative diff against the project's written commitments and reports evidence-grounded findings; works with any coding agent and needs…
Use when adding a domain configuration field, env var, Dockerfile extension, mcpb install-screen entry, or release-manifest stamp: the sentinel-based config and customization contract.
Use before adding or changing any logging call in src/: the structlog-based standard, log levels, exception handling, and message format every module follows.
Use before any release work: the trunk release model, the unstable edge channel, the prepare/release/promotion machinery, release-notes pages, the pre-release artifact smoke test, and, when the plugin channel is enabled, the Claude Code plugin channel.
Use when adding, renaming, or documenting an MCP tool: the registration checklist, the getserverinfo tool, tool icons, and the public import-surface guard.
Reads one assigned batch of markdown-vault notes and returns a faithful partial summary with per-note path attribution. Used by the vault-summarize skill's map phase; not for general vault questions.
Use when the markdown-vault MCP server is down or misconfigured — vault not set up yet, vault directory moved or renamed, git token expired — or when the user asks to set up, connect, or repair their markdown vault. Runs a guided discover → validate → write-config → restart flow.
Use when the user asks to summarize, digest, or get an overview of a folder, project, or set of notes in their markdown vault — runs the vault's batched map-reduce recipe so note bodies stay out of the retained conversation context.
Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.
Instructions for pvliesdonk/markdown-vault-mcp, a project described as: Generic markdown collection MCP server with FTS5 + semantic search, frontmatter-aware indexing, and incremental reindexing.
Use when the user asks you to search, retrieve, or reason about scholarly sources — papers, patents, books, or standards — guides tool selection, chaining, and cross-domain workflows.
Use when filing a bug, opening or creating a GitHub issue, drafting an epic or ticket, writing up a finding or review observation worth tracking, or opening a pull request for this repository. Routes the change to the right repo first (library / template / domain), picks the right issue form, links epic children as…
Use when drafting or revising a release-notes page under docs/releases/ — the Release Prepare workflow's notes job invokes it for every release PR (rc and stable alike), and a human may invoke the Release Notes dispatch for a re-draft or backfill. Walks the API-driven research fan-out (commits to PRs to linked issues…
FastMCP server for scholarly sources (papers, patents, books, and standards) with metadata enrichment and docling PDF conversion. Runs locally from the pvliesdonk-scholar-mcp Python package. Needs 19 environment variables to run.