Daily Workflows

Choose a recipe by the result you need, then adapt its inputs, safety limits, and completion checks. Start with copied files or a narrow data set before using a workflow on important work.

How these recipes are built

Every recipe on this site follows the same three-part structure: what you need before starting (accounts, files, access), the steps in order with the points where Claude needs your supervision, and how to verify the result before you trust it. If a recipe ever skips the verification part, treat that as a mistake and tell us.

What the complexity badge means

Low recipes need no special access and finish in one sitting. Medium recipes touch real accounts or recurring schedules, so they deserve a dry run first. High recipes run many steps across important files — read the whole recipe before starting, and keep the first runs supervised from beginning to end.

Picking your first recipe

  • Start with a Low complexity card. Smart Meeting Notes needs almost no setup and teaches you the rhythm of delegating a task.
  • Then try a Medium one on copied data. The Morning Briefing or Docs Auto-Generator shows how recurring tasks behave without touching anything important.
  • Save High complexity for later. PDF Research and Code Review pay off most once you are comfortable supervising multi-step runs.

Adapting a recipe safely

  1. Run the unmodified recipe once on copied files or a small sample, exactly as written.
  2. Change one input at a time — your folder, your calendar, your repo — and re-verify after each change.
  3. Tighten the safety limits before widening the scope, not after something goes wrong.
  4. Write down the tweaks that mattered; next month you will not remember them otherwise.

Recipes pair well with skills, which standardize the review steps inside them, and connectors, which control the sources a recipe can read. See the skill marketplace and the connectors hub.