Skip to content

Personal wiki upkeep with recommend and lint passes

Three scheduled tasks keep a personal markdown wiki honest. A daily pass archives chat sessions as raw notes, a weekly pass recommends what is durable enough to promote, and a monthly lint flags contradictions, stale claims and broken links.

PersonalWorks with Claude Desktop with MCP · Claude Code+1Community example
Build your promptSee requirements

What it does

  • Archives recent chat sessions into a raw folder as portable markdown
  • Scans new raw material and recommends pages worth promoting
  • Lints the wiki for contradictions, stale claims, orphans and broken links
  • Auto fixes only mechanical issues like dead links
  • Writes a report for everything that needs a judgment call

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Promoting any recommendation into a wiki page
  • Any edit beyond mechanical fixes
  • Deleting or merging pages

You decide what happens next.

More about this workflow

This setup is for busy people who want their own day to run a little smoother. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it archives recent chat sessions into a raw folder as portable markdown. Next, it scans new raw material and recommends pages worth promoting. Then it lints the wiki for contradictions, stale claims, orphans and broken links. After that, it auto fixes only mechanical issues like dead links. Finally, it writes a report for everything that needs a judgment call. It works with your notes app and docs, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before promoting any recommendation into a wiki page, any edit beyond mechanical fixes and deleting or merging pages, and says plainly if a step cannot be undone.

“it never writes wiki pages itself”
greencat667 greencat667 on GitHub · Sep 22, 2026
Before you startNotes app · Docs accessScoped permissionsClaude Desktop with MCP or Claude Code
Explore required tools and model recommendations

Tools and access

  • Notion

    Handles the notes app part of this job. Grant only the pages it needs, read first.

    API required: Yes. Needs a Notion integration. You choose which pages it can see by sharing them with it.

    Sign up: Notion

  • Google Docs

    Handles the docs part of this job. Grant one folder, create and edit only.

    API required: Yes. Needs a Google Cloud OAuth app with the Docs API turned on.

    Sign up: Google Workspace

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Fast and careful with your inbox and calendar.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Cheapest Claude option for daily sorting.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

capture daily, recommend weekly, lint monthly

your test for what gets in

2Your prompt

4 of 4 still empty
Fill these in before you run it: [WIKI FOLDER PATH] [PAGE TYPES YOU USE] [CADENCE: capture daily, recommend weekly, lint monthly] [WHAT COUNTS AS DURABLE: your test for what gets in] You are the Personal wiki upkeep with recommend and lint passes agent. Three scheduled tasks keep a personal markdown wiki honest. A daily pass archives chat sessions as raw notes, a weekly pass recommends what is durable enough to promote, and a monthly lint flags contradictions, stale claims and broken links. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Archives recent chat sessions into a raw folder as portable markdown - Scans new raw material and recommends pages worth promoting - Lints the wiki for contradictions, stale claims, orphans and broken links - Auto fixes only mechanical issues like dead links - Writes a report for everything that needs a judgment call What you must never do without a yes from a person: - Promoting any recommendation into a wiki page - Any edit beyond mechanical fixes - Deleting or merging pages Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Desktop with MCP, Claude Code, Cursor

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Notion with its own login, not yours. Grant only the pages it needs, read first.
  2. 2Connect Google Docs with its own login, not yours. Grant one folder, create and edit only.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval30 / 30

Waits for a yes on: promoting any recommendation into a wiki page, any edit beyond mechanical fixes, deleting or merging pages.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 86.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Personal wiki upkeep with recommend and lint passes](https://trustcase.dev/badge/personal-wiki-upkeep-with-recommend-and-lint-passes.svg)](https://trustcase.dev/use-cases/personal-wiki-upkeep-with-recommend-and-lint-passes)
HTML
<a href="https://trustcase.dev/use-cases/personal-wiki-upkeep-with-recommend-and-lint-passes"><img src="https://trustcase.dev/badge/personal-wiki-upkeep-with-recommend-and-lint-passes.svg" alt="Trustcase trust score for Personal wiki upkeep with recommend and lint passes" height="20"></a>

More personal workflows

Other workflows that use the same tools

  • Daily product spec risk triage against compliance rules

    Operations. Each morning a second line risk reviewer reads product requirement docs completed in the last day from the team wiki and grades six risk areas against the company's ICT and regulatory framework. It outputs one report per document and changes nothing.

  • Lead research brief

    Sales. Turns a new inbound lead into a one page brief before your first call.

  • Proposal first draft

    Sales. Builds a proposal from your template and the discovery notes.