01 ·Context
The problem was never discipline. It was the typing.
The good idea always shows up at the worst possible time. Merging onto the highway. Walking the floor. Three minutes before a call. And the friction of stopping to write it down is exactly high enough that you do not.
Here is the part nobody admits about the task manager they bought: they stopped opening it. Not because it was a bad app. Because capturing a thought in it costs too much. Stop what you are doing, unlock the phone, find the app, pick a list, type the thing, set a due date you will ignore. Six steps to save one sentence. So the sentence does not get saved.
This workflow separates a quick capture from the work of sorting it. Dictate a thought or save a link when you can safely pause. A supported connection writes it to one inbox. A routine reads that inbox later and proposes a numbered list for your review.
02 ·Architecture
Three parts and one rule.
Three parts and one rule.
Part 01 · The captureIt files. That is all.
Say a short phrase and provide the note, URL or file. The capture saves it to the agreed inbox, without analyzing or classifying it. Test a fast available model for this small job.
Part 02 · The inboxA folder that does nothing.
One folder that holds things and does nothing else. No sorting, no notifications, no priorities, no due dates. It sits there and collects. This is the part people skip, because a folder that does nothing feels like a missing feature. It is the opposite.
Part 03 · The routineIt wakes up on a clock.
Twice a day, on a clock, a scheduled task wakes up on its own, reads everything in the inbox, works out what each item is, and leaves a numbered list. Nobody triggers it. This is the same move as playbook 04, Schedule Your Skill, pointed at a different job.
Then you verify. You read the list and fix anything it got wrong, in one line. That is the only part that costs you attention, and it costs about a minute.
03 ·Setup
What you build, and what you connect once.
The capture halfOne phrase, one folder.
You need a saved instruction, a skill, that fires on one short phrase and writes what you gave it into your inbox folder. Two things matter about the phrase: it has to be short enough to say one-handed, and it has to be a phrase you would never say by accident. Do not make it clever. Make it fast.
The modelA fast option that passes the test.
Capture should preserve the words and save them reliably. Test an available fast model on a few notes before choosing it. The sorting step needs more judgment and may benefit from a more capable model.
The inboxResist the urge to structure it.
One folder. That is it. Resist every urge to give it structure. Subfolders, tags, and priorities all reintroduce the decision you are trying to remove.
The routine halfTwo times, picked deliberately.
A scheduled task that runs twice a day and reads the inbox. Pick your two times deliberately: one early enough that the night's captures are sorted before you sit down, one midday so the morning's captures do not wait until tomorrow. Mine runs at 04:45 and 12:45.
Where it runsYour phone, and a clock.
Use dictation on your phone when you can safely pause. Confirm that your chosen app and connection can actually save a file to the inbox. For the routine, verify where its scheduled task runs and whether it can read that destination.
What you connect onceWherever the folder lives.
Use a connection that supports creating files in the inbox and reading them back. Search-only access is not enough. Test the write and verify the saved file before building the sort.
Product instructions checked October 26, 2026. Install and enable Claude skills ↗
04 ·Decisions
Four calls you make when you build one.
Decision 01Voice, or typing.
Both work. Voice removes typing, while a typed note is useful at your desk. Use whichever makes it easiest to preserve the thought accurately when you can safely pause.
Decision 02One inbox, or one per topic.
One. Every extra inbox is a decision at capture time, which is the thing you are removing. Sort later, in a batch, or let the routine do it.
Decision 03How often the routine runs.
Twice a day is the sweet spot. Once means the morning's captures wait until tomorrow. Every hour means you are back to being interrupted by your own system, and the sorted list stops being a thing you read and starts being a thing you dismiss.
Decision 04Cheap model, or good model.
Choose a fast model that reliably preserves and files the input. Test a more capable option for sorting if the first model misclassifies notes. Judge both on your examples.
05 ·Runbook
Build the capture yourself. Hand off the routine.
Build and test the capture before scheduling the sort. The instructions below define both jobs. The connection that actually writes the file is part of the setup, not something a skill adds by itself.
Part 01Build the capture yourself.
Use Claude’s current skill creation or upload flow under Customize → Skills. The name, description and instructions below are the content to give it. For a packaged skill, put the instructions in SKILL.md with name and description in YAML frontmatter, zip the enclosing folder and upload it.
Choose one writable inbox.
Test the connection with a harmless note. Confirm that the saved file exists.
Add the capture instructions.
Use the three boxes below. Enable the skill and test the phrase on the device you will use.
Use these three pieces to create the skill, then enable it. Test the phrase with a sample note, open the resulting file and check every word.
capture-to-inbox
Capture a URL, a note, or a dictated thought into my capture inbox. Use when I say "send this to inbox", "add this to inbox", or "capture this". Files the item and nothing else: does not read it, sort it, classify it, or decide anything about it. Not for saving a whole conversation.
Take whatever I just handed you and file it. Nothing else. WHAT TO ACCEPT: a URL, a note I typed or dictated, a file I dropped in, or any combination of those. WHERE TO PUT IT: write one file into my capture inbox folder at [YOUR FOLDER PATH]. Name it with the date and time so it sorts on its own, for example "Chat Jul 15 2026, 11 12 37". WHAT TO WRITE: the URL on its own line, if there is one. My note verbatim, if there is one. Do not summarize it. Do not tidy it up. Do not add your own commentary. WHAT NOT TO DO: do not open the link. Do not sort, tag, or classify. Do not ask me which folder, which project, or how urgent. If the destination is missing or inaccessible, say so and keep my note in the conversation. Do not claim it was saved. WHEN DONE: reply with one line. Name the file you verified was saved. State the next sort time only if you can verify the schedule. Otherwise say it is not set. Then stop.
Replace [YOUR FOLDER PATH] with the destination your connection can write to. A folder path alone does not grant access. If saving is unavailable, keep the note in the conversation and transfer it manually until the connection is working.
Part 02Hand the routine to a builder.
The routine is a scheduled task, not a form, so this half stays a brief. Hand it to whoever builds your skills, or to Claude directly. It is a complete spec.
THE JOB: Sort my capture inbox and hand me a list.
WHEN IT RUNS: twice a day, 04:45 and 12:45. Nobody triggers it. [Pick your
own two times. One early enough that the night's captures are done before
you sit down, one midday so the morning's captures do not wait until
tomorrow.]
WHAT IT READS: everything sitting in the capture inbox. Nothing else.
WHAT IT DOES WITH EACH ITEM: work out what it actually is.
- For a link: read the page and say in one line what it is and why I might
have kept it.
- For a dictated note: clean up the transcription without changing what I
meant. Do not improve my idea. Do not expand it.
- For anything you cannot identify: say so plainly. Do not guess.
WHAT IT HANDS BACK: one numbered list. For each item: what it is, one line
on what it is about, and where it should go. Numbered, so I can act on one
by saying its number back to you.
DUPLICATES: if I captured the same thing twice, and I will, show it once.
THE HARD RULE: it sorts and proposes. It does not file anything into its
final home, delete anything, or act on anything until I say so.
WHEN IT IS DONE: leave the list where I will see it with coffee. Do not
notify me at 11pm. The whole point is that it waits for me, not the
reverse.06 ·Gotchas
The five that catch everyone.
Sorting at capture time.
The one that will kill your build, and it killed mine for two weeks. My first version sorted each item the instant I captured it. It felt smart. It turned every capture back into a decision, which is the exact friction the build exists to remove, and I stopped using it. Slow it down. Capture files, the routine sorts, and those two never meet.
An inbox with opinions.
If your folder has subfolders, tags, or a priority field, you have not built an inbox, you have built a task manager with extra steps. It holds things. That is the feature.
Expecting images to just work.
The capture will file a screenshot without complaint, but making an image genuinely useful later takes a separate enrichment pass that reads the picture and writes down what is in it. That is its own build. Do not assume it is included.
A trigger phrase you say by accident.
If your phrase is close to something you say in normal conversation, you will file things you did not mean to file. Pick a phrase with a verb and a destination in it.
Scheduling it before it works by hand.
Same rule as any scheduled skill. Run the sort manually a few times on a real inbox first. A schedule runs your build every day exactly as it is, flaws and all. Prove it, then set it loose.
07 ·What's next
Capturing one idea saves you one idea. The pattern is bigger.
Capturing one idea saves you one idea. The pattern is bigger than that.
Start with one dictated thought that is still there when you sit down. Test the capture, then the sort, then the schedule.
Before you call it done.
Check the result against the job you set out to do.
Product notes and sources · Checked October 26, 2026
Features and interface labels can vary by account. Use the current product guidance for installation, access and scheduling.