Claude Prompts for OneNote
35 copy-paste prompts for the notes you already have. Paste a page of half-finished meeting scribbles, a clipped article, or a section that became a dumping ground, and Claude sends back a structured page, an owner-and-date action list, or a study set that you paste straight back into OneNote.
In short: This page contains 35 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Note Structure & Templates
7 promptsNotebook and Section Architecture
1/35<context>Here is my current OneNote structure: [PASTE YOUR NOTEBOOK, SECTION, AND PAGE NAMES]. What I use OneNote for: [DESCRIBE: meetings, projects, research, personal, all of it]. What goes wrong today: [DESCRIBE: cannot find things, pages land in the wrong place, sections nobody opens].</context> <task>Redesign the hierarchy. Tell me what becomes a notebook, what becomes a section group, what becomes a section, and what should just be a page.</task> <format>1. Proposed structure as an indented tree 2. One line per top-level container explaining what belongs in it and what does not 3. Move table: current page, new location 4. Sections to archive or delete outright, with the reason 5. The single rule that decides where a new page goes, stated in one sentence 6. What will break this structure in six months and how to prevent it</format>
Redesigns your notebook, section group, and section hierarchy with a move table for the pages you already have.
Pro tip: Ask for the one-sentence filing rule and nothing more elaborate. A structure that needs a decision tree gets abandoned in a week, and every stray page ends up in Quick Notes.
Reusable Page Template Body
2/35<context>I repeat this type of page constantly: [DESCRIBE: client call, project kickoff, incident, interview, weekly review]. What I always need on it: [LIST THE FIELDS AND SECTIONS]. What I always forget to capture: [LIST].</context> <task>Write the full body text of a reusable page, with headings, prompts, and empty placeholders, so I can paste it once into a blank page and save it as a OneNote template.</task> <format>1. Page title pattern 2. Complete page body, plain formatting, headings as short lines rather than markdown syntax 3. Placeholder lines in square brackets for everything I fill in live 4. A closing block for next steps and owner 5. What you deliberately left off to keep it fast to fill during a live call</format>
Produces the full body text of a repeatable page you save once as a OneNote template.
Pro tip: OneNote does not render markdown, so hash symbols show up as literal characters. Ask for headings as short bold-style lines, paste the body into a blank page, then use Insert, Page Templates, Save current page as a template.
Tag System You Will Actually Maintain
3/35<context>How I work: [DESCRIBE YOUR ROLE AND WHAT YOU TRACK]. Things I need to find again later: [LIST]. Tags I use today: [LIST, OR SAY NONE]. Team or solo: [ANSWER].</context> <task>Design a tag set for OneNote. Keep it small enough to memorize, and tell me exactly when each tag gets applied so two people tag the same thing the same way.</task> <format>1. Tag list, maximum eight, with the trigger for applying each one 2. Which built-in OneNote tags to reuse and which need a custom tag 3. Suggested keyboard shortcut order, since the first nine tags get Ctrl plus a number 4. Tags to explicitly not create, with the reason 5. Weekly routine that turns tags into a review list 6. How to keep tag usage consistent across a team</format>
Designs a memorizable OneNote tag set with clear application rules and a weekly review routine.
Pro tip: Order matters more than people expect. Only the first nine tags in the gallery get a Ctrl plus number shortcut, so put your two highest-frequency tags at positions one and two and reorder the gallery to match.
Page Naming Convention for Search
4/35<context>Sample of my current page titles: [PASTE TWENTY OF THEM]. What I usually search for when I am hunting a page: [DESCRIBE THE ACTUAL SEARCH TERMS YOU TYPE]. Time range these cover: [PERIOD].</context> <task>Write a page title convention tuned for OneNote search, then rename my sample titles to match so I can see it working.</task> <format>1. Title pattern with each element explained in one line 2. Date format choice and why it sorts correctly 3. Rename table: current title, new title, for all twenty 4. Words to always include because I search for them, and words to drop as noise 5. How the convention behaves when a page spans two projects</format>
Creates a search-friendly page title convention and rewrites your existing titles to match.
Pro tip: OneNote search weights page titles heavily, so the words you actually type when hunting belong in the title, not buried in the body. Untitled pages are effectively invisible to search.
Extract the Common Structure From Your Best Pages
5/35<context>These are three pages I was happy with: [PASTE PAGE ONE] [PASTE PAGE TWO] [PASTE PAGE THREE]. And here is one that was useless a month later: [PASTE IT].</context> <task>Reverse engineer what the good pages have in common and the bad one lacks, then turn that into a structure I can reuse.</task> <format>1. Shared elements across the good pages, ranked by how much they contribute 2. What the useless page was missing, specifically 3. The extracted structure as a skeleton I can paste 4. Two elements you would add that none of my pages have 5. The habit change that matters more than the template</format>
Reverse engineers the structure of your genuinely useful pages into a reusable skeleton.
Pro tip: Include the bad page in the paste. The contrast is what makes the analysis specific, and Claude cannot tell what failed you if it only sees the pages that worked.
Migration Map From Another Notes App
6/35<context>Moving from [EVERNOTE / NOTION / APPLE NOTES / OBSIDIAN / GOOGLE DOCS] to OneNote. Here is my current structure and item counts: [PASTE THE LIST OF NOTEBOOKS, FOLDERS, OR TAGS WITH ROUGH COUNTS]. What I care about keeping: [LIST]. What I would happily lose: [LIST].</context> <task>Map the old structure onto OneNote's notebook, section group, section, page, subpage model, and tell me what does not survive the move.</task> <format>1. Mapping table: source container, OneNote destination, note on the fit 2. Concepts with no OneNote equivalent, and the closest workaround for each 3. What to migrate first so the move is usable before it is complete 4. What to archive as a read-only dump instead of migrating properly 5. Formatting and attachment losses to expect 6. Cleanup pass to run one week after the move</format>
Maps another app's structure onto OneNote's hierarchy and flags what will not survive the migration.
Pro tip: Nested tags and backlinks have no real OneNote equivalent, so decide up front which one you are giving up. Ask for the workaround per concept before you migrate, not after 400 notes have landed flat.
Daily and Weekly Planning Page
7/35<context>My week looks like: [DESCRIBE THE RECURRING MEETINGS, DEEP WORK BLOCKS, AND REPORTING DEADLINES]. Where my tasks currently live: [ONENOTE / OUTLOOK TASKS / PLANNER / HEAD]. What falls through the cracks: [DESCRIBE].</context> <task>Write the body of a daily page and a weekly page that work together, so the weekly page feeds the daily one and nothing needs re-typing.</task> <format>1. Weekly page body, ready to paste 2. Daily page body, ready to paste 3. The handoff: what moves from weekly to daily and when 4. Where the To Do tag goes so the Find Tags summary is usable 5. Friday close-out checklist, five items maximum 6. What to do with items that roll over three weeks in a row</format>
Delivers paired daily and weekly planning page bodies with a defined handoff between them.
Pro tip: Tag every task line with the built-in To Do tag as you write it. Find Tags then builds a single summary page across the whole notebook, which is the closest OneNote gets to a real task list.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Meeting Notes & Action Items
7 promptsClean Up Notes Typed During the Call
8/35<context>Raw notes I typed while the meeting was happening, unedited: [PASTE THEM]. Meeting was about: [ONE LINE]. Attendees: [LIST]. I need this page to make sense to me in three months and to someone else next week.</context> <task>Restructure into a clean page. Keep every fact I captured, fix the shorthand, and separate what was decided from what was merely discussed.</task> <format>1. Page title with date and topic 2. Context, two sentences 3. Decisions made, each with who made it 4. Open questions with who owns the answer 5. Action items, owner and date each 6. Discussion notes, tidied, for anything that fits nowhere else 7. A short list of things I appear to have half-captured and should verify</format>
Turns live-typed meeting scribbles into a structured page that separates decisions from discussion.
Pro tip: Ask for the half-captured list. It surfaces the trailing fragments you typed while someone was still talking, which is exactly the material you would otherwise lose.
Action Items With Owners and Dates
9/35<context>Meeting notes: [PASTE THEM]. Attendees and roles: [LIST]. Meeting date: [DATE]. Our default turnaround when nothing is stated: [DAYS].</context> <task>Pull out every action item, including the ones phrased as someone saying they would look into it. Assign an owner and a date to each, and flag the ones where the owner was never actually named.</task> <format>1. Action table: action, owner, due date, source line from my notes 2. Implied actions nobody claimed, listed separately 3. Items that read like actions but are really decisions or FYI 4. Follow-up message text I can send to confirm the unclaimed ones 5. Which items to tag with To Do on the page</format>
Extracts explicit and implied action items with owners, dates, and the source line from your notes.
Pro tip: The unclaimed items are the whole value of this prompt. Someone saying they will take a look is not an owner, and those lines are the ones that go missing between meetings.
Decision Log Entry
10/35<context>Discussion notes where a decision got made: [PASTE THEM]. Project: [NAME]. Who was in the room: [LIST]. What we decided, in my words: [ONE LINE, OR SAY IT IS IN THE NOTES].</context> <task>Write a decision log entry that will still be defensible in a year, capturing the alternatives we rejected and why, not just what we picked.</task> <format>1. Decision statement, one sentence, unambiguous 2. Date, decision maker, and who was consulted 3. Options considered, with the reason each was rejected 4. Assumptions the decision rests on 5. What would make us revisit this 6. Anything the notes do not tell us that the log should record, flagged as a gap</format>
Writes a durable decision log entry including rejected alternatives and the assumptions behind the choice.
Pro tip: Recording the rejected options is what stops the same debate reopening in six months. When someone asks why we did not just do X, the entry answers it without anyone reconstructing the meeting from memory.
Recap Email From the Meeting Page
11/35<context>My OneNote meeting page: [PASTE IT]. Recipients: [WHO, AND WHETHER THEY ATTENDED]. Relationship: [INTERNAL TEAM / CLIENT / EXEC]. What I need from them after reading: [DESCRIBE].</context> <task>Write the recap email. It should be readable in thirty seconds on a phone, with the asks impossible to miss.</task> <format>1. Subject line 2. Email body, under 200 words 3. Actions section with owner and date, formatted for scanning 4. What I deliberately left out of the email versus the page 5. A one-line version for a Teams post, if that is a better channel 6. Follow-up timing if nobody replies</format>
Converts a meeting page into a short, scannable recap email with unmissable asks.
Pro tip: Send the recap from the page, never the page itself. Nobody reads a pasted notes page, and the parts you would strip for an email are the parts that make the page useful to you later.
Next Meeting Agenda From the Last One
12/35<context>Notes from the last meeting: [PASTE THEM]. Notes from the one before, if useful: [PASTE OR SKIP]. Next meeting length: [MINUTES]. Who is attending: [LIST]. What has happened since: [DESCRIBE OR SAY NOTHING].</context> <task>Build the agenda for the next session from what was left open, timeboxed to the actual meeting length.</task> <format>1. Agenda items with a timebox and an owner each, totalling the meeting length 2. Carried-over items with a status question for each 3. Items to drop, with the reason, so the agenda does not grow forever 4. Pre-reads to send and to whom 5. The one outcome that makes the meeting worth holding 6. What to cut first if the meeting runs long</format>
Generates a timeboxed agenda from the previous meeting's open items, including what to drop.
Pro tip: Ask for the cut-first list. Every recurring meeting accumulates zombie agenda items, and having the cut order decided before the meeting stops the last topic from being the one that always gets skipped.
Merge Notes From Several Attendees
13/35<context>Notes from the same meeting taken by different people. Person one: [PASTE]. Person two: [PASTE]. Person three: [PASTE OR SKIP]. Meeting topic: [ONE LINE].</context> <task>Merge them into one canonical page. Where the accounts disagree, show both rather than picking one, and mark it for resolution.</task> <format>1. Merged page, structured as context, decisions, actions, discussion 2. Conflict table: what each version says, and who needs to resolve it 3. Details only one person captured, kept and attributed 4. Duplicate content collapsed, with nothing dropped 5. Confidence note on any section built from a single source</format>
Reconciles multiple attendees' notes into one canonical page with disagreements surfaced, not silently resolved.
Pro tip: Never let a merge silently pick a winner. Two people remembering a different number is a signal worth chasing, and a merged page that hides the conflict is worse than two separate pages.
Roll Up a Running One-on-One Page
14/35<context>My running one-on-one page with [PERSON], covering [TIME PERIOD]: [PASTE THE WHOLE PAGE]. Their role: [TITLE]. Upcoming: [REVIEW CYCLE / PROMOTION CASE / NOTHING SPECIFIC].</context> <task>Roll it up. Show me the themes that keep recurring, what got resolved, what has been quietly unaddressed for months, and what to raise next time.</task> <format>1. Recurring themes with the dates they appeared 2. Commitments made by each side, and whether the notes show them closing 3. Topics raised once and never revisited 4. Trajectory read: what has changed over the period, with evidence from the notes 5. Three things to raise at the next one-on-one, phrased as questions 6. Anything worth writing down that the notes never capture</format>
Analyzes months of one-on-one notes for recurring themes, dropped commitments, and next-session talking points.
Pro tip: This is the one Claude use that pays for itself at review time. Six months of one-on-one notes contain the specific dated evidence that makes a promotion case or a performance conversation concrete instead of impressionistic.
Research & Study Notes
7 promptsClipped Article Into Structured Notes
15/35<context>Article text I clipped into OneNote, ads and navigation included: [PASTE IT]. Why I saved it: [ONE LINE]. What I am working on that this feeds: [DESCRIBE].</context> <task>Strip it to notes I will actually reread. Keep the claims and the numbers, drop the filler, and tell me what is relevant to my specific project versus generally interesting.</task> <format>1. Source line: title, author, publication, date, URL 2. Core argument in three sentences 3. Claims and data points worth keeping, one line each 4. Relevance to my project, separated from the rest 5. Quotes worth keeping verbatim, with a reason for each 6. What the article does not answer that I still need</format>
Compresses a clipped web article into reusable notes separated by relevance to your actual project.
Pro tip: OneNote's web clipper drags in navigation, cookie banners, and related-article blocks. Paste the whole mess and let Claude filter, rather than hand-deleting the noise before you know what is worth keeping.
Cornell Layout From Raw Reading Notes
16/35<context>My raw notes from [BOOK / PAPER / COURSE], unedited: [PASTE THEM]. Purpose: [EXAM / PROJECT / GENERAL UNDERSTANDING]. What I need to be able to do afterwards: [DESCRIBE].</context> <task>Restructure into a Cornell layout: cue questions on the left, notes on the right, summary at the bottom, so I can cover the notes column and self-test.</task> <format>1. Cue questions, one per note block, phrased so the answer is the note 2. Notes column content, tightened but complete 3. Summary paragraph, five sentences maximum, in my own register 4. Concepts my notes clearly do not understand yet, named honestly 5. How to lay this out on a OneNote page using a two-column table</format>
Converts raw reading notes into a Cornell cue, note, and summary layout you can self-test against.
Pro tip: Build the Cornell layout as a two-column OneNote table, not with tabs and indents. Table cells stay aligned when you add content later, which is exactly when a tab-based layout falls apart.
Flashcard Set From a Page
17/35<context>Study page: [PASTE IT]. Subject: [NAME]. Assessment format: [MULTIPLE CHOICE / SHORT ANSWER / ESSAY / PRACTICAL]. How long until I need this: [TIME].</context> <task>Generate a question and answer set covering the material, weighted toward what my assessment format actually tests, and formatted so I can paste it into a OneNote table.</task> <format>1. Tab-separated question and answer pairs, one per line, minimum twenty 2. Difficulty marker on each: recall, application, or analysis 3. Five questions targeting the concepts my page explains weakest 4. Concepts in the page that are not testable and can be skipped 5. A review order for the first pass</format>
Builds a graded flashcard set from a study page, formatted for pasting into a OneNote table.
Pro tip: Tab-separated text does not become a table when pasted directly into OneNote. Paste it into Excel first, then copy the cells across, and OneNote builds the table for you with the columns intact.
Compare Notes From Several Sources
18/35<context>Notes from source one: [PASTE]. Source two: [PASTE]. Source three: [PASTE]. The question I am trying to answer across all of them: [STATE IT].</context> <task>Build a comparison that shows where the sources agree, where they conflict, and where each one is simply silent.</task> <format>1. Comparison table: dimension, what each source says 2. Points of genuine conflict, with what would settle each one 3. Consensus points, and how strong the consensus actually is 4. Gaps where every source is silent 5. Answer to my question given only this evidence, with the confidence stated 6. What to read next to close the biggest gap</format>
Cross-compares notes from multiple sources into an agreement, conflict, and silence map.
Pro tip: Ask for the silence column explicitly. Sources agreeing looks like confirmation until you notice all three inherited it from the same original, and the gap nobody addresses is usually the interesting part.
Lecture or Podcast Transcript Into a Study Page
19/35<context>Transcript or dictated notes, unedited and full of filler: [PASTE IT]. Speaker and topic: [DESCRIBE]. Length of the original: [MINUTES]. What I need to retain: [DESCRIBE].</context> <task>Turn spoken sprawl into a study page. Remove the verbal filler and repetition, keep the examples, and preserve anything the speaker flagged as important.</task> <format>1. Topic outline as it was actually delivered 2. Key points with the speaker's own examples kept intact 3. Anything explicitly signposted as important or examinable 4. Terminology list with definitions as the speaker used them 5. Sections where the transcript is garbled and I should recheck the recording 6. Five questions the material should let me answer</format>
Turns a raw transcript into a structured study page with examples preserved and filler removed.
Pro tip: OneNote's Dictate button gives you a transcript with no punctuation and no paragraphs, which is unreadable but perfectly usable as Claude input. The garbled-sections list tells you which timestamps to replay.
Spaced Review Schedule From a Notebook
20/35<context>Pages in my study section with the date I wrote each: [PASTE THE LIST]. Deadline: [DATE]. Time available per day: [MINUTES]. Topics I already feel weak on: [LIST].</context> <task>Build a spaced repetition schedule across the pages I have, weighted toward the weak topics and fitting the time I actually have.</task> <format>1. Day by day schedule to the deadline, with which pages to review each day 2. Repetition intervals used and the reasoning 3. Weighting applied to weak topics, made explicit 4. Pages that need rewriting before they are reviewable, flagged 5. Checkpoint days where I test rather than review 6. What to cut if I lose a week</format>
Generates a deadline-driven spaced review schedule weighted toward your weakest topics.
Pro tip: Ask for the what-to-cut plan in the same output. Every study schedule survives contact with reality for about four days, and having the cut order pre-decided prevents the panic-abandon spiral.
Clean Up OCR and Handwriting Output
21/35<context>Text pulled from a scanned or photographed page using Copy Text from Picture, with all the OCR errors intact: [PASTE IT]. Subject matter: [DESCRIBE, so misread technical terms can be inferred]. Original was: [HANDWRITTEN / PRINTED / A WHITEBOARD PHOTO].</context> <task>Repair the OCR output first, then structure it. Flag anything you had to guess rather than silently correcting it.</task> <format>1. Repaired text with line breaks and punctuation restored 2. Corrections table: what the OCR produced, what it should be, confidence 3. Passages too corrupted to recover, marked for manual recheck 4. Structured version of the repaired notes 5. Numbers and names to verify against the original, since OCR errors there are the costly ones</format>
Repairs OCR output from scanned or handwritten pages, flagging guesses instead of silently correcting them.
Pro tip: Always check the numbers by hand. OCR turning a 3 into an 8 reads perfectly fluently and there is no way for Claude to detect it from context, which is why the verify list matters more than the cleanup.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Cleanup & Summarization
7 promptsRescue a Dumping-Ground Page
22/35<context>One page that has collected everything for [TIME PERIOD] with no structure at all: [PASTE THE WHOLE THING]. What it was originally for: [DESCRIBE]. What I need out of it now: [DESCRIBE].</context> <task>Impose a structure without throwing anything away. Group what belongs together, surface what is still live, and tell me what has quietly expired.</task> <format>1. Proposed page structure with headings 2. Full rewritten page under that structure, nothing dropped 3. Still live: items that need action, with what the action is 4. Expired: items overtaken by events, listed so I can confirm before deleting 5. Content that deserves its own page, with the suggested title 6. What to do differently so this page does not re-accumulate</format>
Restructures a chaotic catch-all page into headed sections while separating live items from expired ones.
Pro tip: Insist on nothing dropped in the first pass. Reviewing a restructured page and deleting the dead lines yourself takes two minutes, whereas discovering that a summarizer silently ate a client commitment takes months.
Merge Near-Duplicate Pages
23/35<context>Pages covering the same topic that drifted apart. Page one, written [DATE]: [PASTE]. Page two, written [DATE]: [PASTE]. Page three: [PASTE OR SKIP]. Topic: [ONE LINE].</context> <task>Produce one canonical page. Where the versions contradict each other, prefer the newer one but show me what the older one said before I lose it.</task> <format>1. Canonical merged page 2. Contradiction table: older version, newer version, what I kept 3. Unique content found only in one page, preserved and marked 4. Which page to keep as the canonical one and which to delete 5. What to write at the top of the survivor so future me knows it is the merged version 6. Content that is genuinely obsolete and safe to lose</format>
Merges drifted duplicate pages into one canonical version with contradictions surfaced before deletion.
Pro tip: Delete the losers only after the merged page has survived a week. OneNote's page recycle bin holds deleted pages for sixty days, but people rarely remember that at the moment they need it.
Executive Summary of a Long Page
24/35<context>Long page: [PASTE IT]. Who needs the summary: [ROLE]. How much time they will give it: [SECONDS OR MINUTES]. The decision or action it should lead to: [DESCRIBE].</context> <task>Write a summary sized to that attention span, leading with what the reader needs to do rather than with background.</task> <format>1. One-sentence version 2. Five-bullet version 3. One-paragraph version with the ask in the first line 4. The three details this audience will ask about, with the answers ready 5. What I left out and why it is safe to leave out 6. Where to place the summary on the page so it survives future edits</format>
Produces three lengths of executive summary sized to the reader's attention, leading with the ask.
Pro tip: Put the summary at the top of the original page rather than on a new page. A summary that lives somewhere else goes stale within two edits and then actively misleads whoever finds it first.
Strip Formatting Noise From Pasted Content
25/35<context>Content pasted from a web page or a document that arrived with broken structure: [PASTE IT]. Original source: [WEB PAGE / PDF / WORD DOC / EMAIL]. What I want to keep: [THE ARGUMENT / THE DATA / THE PROCEDURE / ALL TEXT].</context> <task>Rebuild it as clean text. Fix the broken line breaks and column splits, restore the reading order, and drop the navigation and boilerplate.</task> <format>1. Clean text with paragraphs and reading order restored 2. Tables rebuilt as tab-separated rows, if any were mangled 3. Boilerplate removed, listed briefly so I can confirm nothing important went 4. Places where the original order was ambiguous and I should check 5. Suggested headings to add, since the paste lost the original ones</format>
Rebuilds mangled pasted content into clean text with reading order, tables, and headings restored.
Pro tip: PDF pastes are the worst offenders because two-column layouts interleave line by line. Claude can usually rebuild the reading order from the sentence flow, but verify the first paragraph of each column before you trust the rest.
Turn Prose Notes Into a Table
26/35<context>Notes written as prose that are really a comparison or a list of records: [PASTE THEM]. What varies between the items: [DESCRIBE, OR SAY WORK IT OUT]. What I want to do with the table: [SORT / COMPARE / TRACK STATUS].</context> <task>Extract the implicit table. Work out the columns from the content, fill every row, and mark cells where my notes never said.</task> <format>1. Column list with a one-line justification for each 2. Tab-separated table including a header row 3. Cells marked as not stated rather than guessed 4. Rows where my notes are internally inconsistent 5. A column you would add that my notes do not cover but the use case needs 6. How to get this into OneNote as a real table</format>
Extracts an implicit table from prose notes with unstated cells flagged rather than invented.
Pro tip: The not stated marker is the point of this prompt. A table with plausible guesses in the gaps looks authoritative and is far more dangerous than one with visible holes you can go and fill.
Archive Triage: Keep, Merge, or Delete
27/35<context>Page index with titles and last-modified dates: [PASTE IT]. Section purpose: [DESCRIBE]. Retention rules we have, if any: [DESCRIBE OR SAY NONE]. My tolerance for deleting things: [LOW / MEDIUM / HIGH].</context> <task>Triage every page into keep, merge, archive, or delete, and give me the order to work through it so the first thirty minutes clear the most clutter.</task> <format>1. Verdict table: page, verdict, reason 2. Merge groups, with the proposed surviving title for each 3. Pages you cannot judge from the title alone, listed for me to open 4. Work order, highest clutter reduction first 5. What to move to an archive section rather than delete outright 6. A rule that keeps this section from refilling</format>
Triages a page index into keep, merge, archive, and delete verdicts with an efficient work order.
Pro tip: Archive rather than delete for anything client-facing or contractual. Move it to a section marked archive, keep the dates intact, and OneNote search still finds it when someone disputes what was agreed.
Rewrite Shorthand So Others Can Read It
28/35<context>Notes written in my personal shorthand: [PASTE THEM]. Abbreviations I know I use: [LIST THE ONES YOU CAN THINK OF]. Who needs to read this: [ROLE AND HOW MUCH CONTEXT THEY HAVE].</context> <task>Rewrite it into full sentences a colleague can follow without me in the room, and flag every abbreviation you had to guess at.</task> <format>1. Rewritten notes in full prose 2. Glossary of abbreviations expanded, with a confidence flag on each guess 3. Fragments too cryptic to expand, quoted verbatim for me to fill in 4. Missing context a newcomer needs that the notes assume 5. Names and acronyms to spell out on first use 6. Which sections stay shorthand because only I will ever read them</format>
Expands personal shorthand into readable prose while flagging every abbreviation it had to guess.
Pro tip: Do this before handing over a project, not after. The cryptic-fragment list is a precise inventory of everything only you know, which is exactly what a handover document is supposed to contain.
Knowledge Base & Retrieval
7 promptsSearchable Keyword Header for a Page
29/35<context>Page content: [PASTE IT]. Words I would realistically type when hunting for this in six months: [LIST WHAT COMES TO MIND]. Who else searches this notebook: [SOLO / TEAM].</context> <task>Write a short keyword line to sit under the page title, containing the terms that make this findable, including the wrong words people will try first.</task> <format>1. Keyword line, one row, under fifteen terms 2. Why each cluster of terms is there 3. Synonyms and old project names people still use 4. Common misspellings worth including 5. Improved page title 6. The same treatment applied as a rule I can reuse on other pages</format>
Writes a keyword line that makes a page findable, including synonyms and the wrong terms people try first.
Pro tip: Include the old project name. Teams rename projects and then spend two years searching for the previous name, and OneNote search matches literal text with no notion of synonyms.
Notebook Index Page
30/35<context>Every section and page in the notebook: [PASTE THE LIST]. Who uses this notebook: [DESCRIBE]. The three things people most often need to find: [LIST].</context> <task>Write an index page that sits at the front of the notebook, organized by what people are trying to do rather than mirroring the section order.</task> <format>1. Index page body, grouped by task rather than by section 2. A start here block for someone opening the notebook for the first time 3. Entries that need a link, marked so I know where to paste them 4. Pages that should exist but do not, based on the gaps in the list 5. How often this index needs updating and what triggers it</format>
Builds a task-organized front index for a notebook, including the pages that should exist but do not.
Pro tip: Add the links yourself: right click any page, choose Copy Link to Page, and paste it onto the index entry. Claude can write the index text and mark where each link goes, but the link identifiers only exist inside your notebook.
Onboarding Runbook From Scattered Notes
31/35<context>Everything I have written about how this process works, spread across pages: [PASTE THEM ALL]. The role being onboarded: [TITLE]. How long they have before they are expected to run it solo: [TIME]. What they already know: [DESCRIBE].</context> <task>Assemble a runbook someone can follow without asking me. Fill the gaps you find with explicit questions rather than assumptions.</task> <format>1. Runbook with numbered steps, each stating who does it and in which system 2. Prerequisites: access, permissions, tools, requested before day one 3. Failure modes and what to do about each 4. Gaps where my notes assume knowledge, phrased as questions for me to answer 5. First week, first month checklist 6. Which steps must be watched once before being done alone</format>
Assembles scattered process notes into a followable runbook with the knowledge gaps stated as questions.
Pro tip: The gap questions are the deliverable. Notes written by the person who does the job always skip the steps that feel obvious, and those are precisely the steps that stop a new hire on day three.
FAQ Page From Repeated Questions
32/35<context>Questions I keep getting asked, pulled from chats, emails, and meeting notes: [PASTE THEM]. Who asks them: [ROLE]. What I currently do instead of having an FAQ: [DESCRIBE].</context> <task>Group the questions and write the answers as a page I can point people to instead of answering the same thing weekly.</task> <format>1. Questions grouped into themes 2. Answer per question, written for someone with no context 3. Questions that reveal a broken process rather than a documentation gap, flagged separately 4. Ordering: most-asked first 5. The one-line message I send when pointing someone at this page 6. Review cadence and what makes an answer go stale</format>
Converts recurring questions into an FAQ page and separates documentation gaps from process problems.
Pro tip: Watch the flagged questions closely. If four people a month ask how to get access to something, the answer is not a better FAQ entry, it is that the access process is broken.
Tag Review Routine
33/35<context>Output of the Find Tags summary from my notebook: [PASTE IT]. Tags in use: [LIST]. What I currently do with tagged items: [DESCRIBE, OR ADMIT NOTHING].</context> <task>Turn this tag dump into a working review routine. Group it, tell me what is overdue, and define what happens to each tag type in the weekly pass.</task> <format>1. Grouped review list: what needs action, what needs a decision, what needs filing 2. Items that have clearly been sitting untouched, called out by age 3. Per-tag rule: what a weekly review does with each tag type 4. Tags being applied inconsistently, with the evidence 5. Fifteen-minute weekly routine, step by step 6. What to do with items that survive three reviews unchanged</format>
Turns a Find Tags summary into a grouped review list and a fifteen-minute weekly routine.
Pro tip: Find Tags, in the Home tab, builds a summary page of every tagged line across the notebook. That summary is the highest-signal thing you can paste into Claude, because it is already filtered to the lines you marked as mattering.
Client or Project Brief From Everything You Have
34/35<context>Every page I have on this client or project: [PASTE THEM, MARKING WHERE EACH PAGE STARTS]. Who needs the brief: [ROLE]. Why now: [NEW TEAM MEMBER / HANDOVER / PITCH / REVIEW].</context> <task>Write a single brief that gives the reader everything they need. Separate what I know from what I have assumed, and date the facts that go stale.</task> <format>1. Brief with background, current state, key people, commitments, and open items 2. Timeline of what happened when, built from the dates in my notes 3. Facts with an as-of date, since some of this is old 4. Assumptions I have been treating as facts, flagged 5. What is missing that the reader will immediately ask about 6. Sensitive material to strip before this brief leaves the company</format>
Consolidates every page on a client or project into one dated brief that separates facts from assumptions.
Pro tip: Mark where each page starts when you paste, with a line like PAGE, title, date. Claude uses those boundaries to build the timeline, and without them a two-year history collapses into undated mush.
Audit What the Notebook Is Missing
35/35<context>Full page index with dates: [PASTE IT]. What this notebook is supposed to support: [DESCRIBE THE ROLE, PROJECT, OR PROCESS]. What has bitten me recently because it was not written down: [DESCRIBE].</context> <task>Audit the notebook against its purpose. Tell me what should exist and does not, what is stale, and what is documented far past the point of usefulness.</task> <format>1. Missing pages, ranked by the cost of not having them 2. Stale pages: last modified long ago on topics that certainly moved 3. Over-documented areas where effort is being wasted 4. Single points of failure: things only recorded in one place with no backup 5. Three pages to write this week, with a one-line brief for each 6. A quarterly audit checklist I can rerun</format>
Audits a notebook against its purpose to surface missing pages, stale content, and single points of failure.
Pro tip: Run this before a holiday or a handover. The single-points-of-failure list is the practical answer to what happens if you are unavailable, and it takes ten minutes rather than a planning workshop.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.