Provenote early-stage Claude Code plugin

Every quote in your notes, checked against its page.

Turn a reading list into source-grounded notes, check a draft against them, and build the paper. The quote check is a program, not a model's opinion: each quote is matched on its stated page against a page-marked Markdown copy of the source. What that does and does not show.

No server, no account, no API key for the quote check. The skills are Markdown that your assistant reads; the helpers are standard-library Python that runs on your machine. Converting PDFs needs Poppler's pdftotext, and building a paper needs pandoc.

Install

Upgrading from research-kit? Remove the old plugin before installing; see the upgrade steps.

In Claude Code, with Git installed:

/plugin marketplace add nik110403/provenote
/plugin install provenote@provenote

Then ask Claude to start a research project, search the literature, or verify notes. A Codex adapter exists too; see the install guide.

Seen in a real run

Animated terminal demo of a real Claude Code run on a small example project: verify-quotes passes the six real quotes of one note and fails a planted fabricated quote, check-claims flags a draft sentence with an invented quote and an uncited quotation, and Claude lists which draft sentences the notes do not back.

A real Claude Code run on a small demo project (about 18 seconds, plays once; how it was made). Six quotes pass, one planted fabrication fails, and the draft's invented quote and uncited quotation are flagged. The sources ship with the repository.

What you get

  1. Notes whose every quote is checked

    A reading list becomes structured notes with page-pinned quotes. Each quote is matched on its stated page against a Markdown copy of the source.

  2. A draft checked against those notes

    Review roles read the draft against the notes, challenge its strongest claims, and flag citations the notes do not support.

  3. A paper that builds

    The bibliography is checked for structure and coverage, then pandoc builds PDF, HTML or DOCX.

How it works

Enter at any stage for which you have the inputs. The tools do the mechanical checks; the assistant roles return text for your session to save.

  1. Scaffoldnumbered project tree
  2. Searchproviders, with a receipt
  3. ConvertPDF to page-marked Markdown
  4. Verify quoteseach quote, on its page
  5. Draftwritten by you
  6. Reviewagainst the notes
  7. Buildbibliography check, then paper

Side track: set up and run a repeatable analysis, then return to the draft.

What is and is not verified

The check is narrow: each quote appears, on its stated page, in a hashed Markdown copy of the source (hash enforced with --strict). It does not show that the copy matches the original PDF, that the quote supports the claim, or that the claim is true. Those stay with a model or with you. Read the full boundary.