Recipes

Each recipe below gives a prompt you could actually type, the tools it will reach for, and the lowest permission that lets it run. Grant only what the recipes you use need — see the permission groups for what each grant costs you.

A note that applies to almost all of these: notes are stored against field IDs, not field names, so a well-behaved assistant reads the notebase schema before its first write. If it guesses instead, tell it to read the schema first.

Capture

Save a word from the conversation

We just talked about "hedge" in the financial sense. Save that to my English notebase, filled in the way the existing notes are.

get_notebase_schema → create_notes · notes:write

The assistant reads your fields, then writes one note in the shape they describe. If you own several notebases that would fit, say which one. Any card templates already on that notebase turn the new note into cards immediately.

Turn a PDF or an article into structured notes

Here's a PDF of a chapter. Pull out the vocabulary I'd plausibly not know at B2 level, and save each one to my English notebase with a definition and the sentence it came from.

get_notebase_schema → create_notes · notes:write

Your assistant reads the document with its own file or browsing tools; Read Frog only saves what comes out. create_notes writes up to 50 notes per call and rolls the whole batch back if any of them collide, so a long chapter arrives in a few clean batches rather than one all-or-nothing write.

Find a note you half remember

I saved something a while back about a word meaning "to walk aimlessly". Find it in my English notebase.

list_notes · notes:read

Search is a literal, case-insensitive substring of at least two characters, it runs against one notebase at a time, and it only looks inside text fields — a number, date, checkbox or select value will never match. For anything fuzzier, have the assistant list the notebase and judge for itself.

Shape the notebase

Have the assistant design a notebase and its fields

I'm starting Japanese. Set up a notebase for it with the fields you'd want for vocabulary — but tell me the plan before you create anything.

create_notebase → create_notebase_field · notebases:write

create_notebase makes an empty notebase, optionally with its first fields; notes are always a separate step. Asking for the plan first is worth the extra turn, because a field's type cannot be changed afterwards — only its name and its options.

Generate a card template

Look at my Japanese notebase and build a recognition card: the word on the front, meaning and example on the back.

get_notebase_schema → create_card_template · card_templates:write with notebases:read

Templates reference fields by ID, which is why the schema read comes first. Creating a template generates cards for every note already in the notebase, so a 400-note notebase gains 400 cards the moment the template lands.

Fix a template that renders badly

The back of my Japanese cards is showing the raw field instead of the example sentence. Look at one card and fix the template.

get_card → get_card_template → update_card_template · card_templates:write with notes:read and study:read

get_card is what makes this possible: it returns the rendered front and back, so the assistant can see the actual output rather than reasoning about the pattern in the abstract.

Tidy up the fields

The "part of speech" field in my English notebase is free text and it's a mess. Turn it into a select with the options actually in use.

get_notebase_schema → list_notes → update_notebase_field · notebases:write with notes:read

A field's type is fixed, so this is a rename-and-reconfigure, not a conversion. Removing a select option clears that value from every note that held it, and a field that a template refers to cannot be deleted at all.

Fill in what is missing

Backfill examples, part of speech and phonetics

Go through my English notebase and fill in any note that's missing an example sentence, part of speech or phonetics. Leave everything else alone.

list_notes → update_note · notes:write

update_note merges: fields you do not mention keep their values, and null clears one deliberately. Each update carries the note's current timestamp, so if something changed in between, the write fails rather than overwriting your edit — the assistant should re-read that note and try again. This runs one note per call, so expect it to work through a large notebase in batches.

Study

What should I review today

What's waiting for me today, and roughly how long will it take?

get_study_stats → list_cards · study:read with notes:read for the card contents

get_study_stats gives you the queue counts per notebase for a given day, and list_cards can filter by schedule status to show what those counts contain.

Review inside the conversation

Quiz me on ten due cards from my Japanese notebase. Show me the front, wait for my answer, then record how I did.

list_cards → record_review → undo_review · study:write with notes:read

This works, and it is the recipe to be most deliberate about. Every rating the assistant records is a real review: FSRS updates the card's stability, difficulty and next due date from it, exactly as if you had pressed the button yourself. Recording a review also needs a time zone, because it decides which study day the review belongs to — if your account has never stored one, the call fails and asks for it rather than guessing. undo_review rolls back the latest review of a single card when you were misgraded, and only that one.

Bury or suspend a card that is too hard

That last card isn't sticking and I keep failing it. Take it out of rotation for now.

set_card_suspended / set_card_buried · study:write

Bury hides a card for the rest of the day; suspend takes it out until you put it back. Both are reversible with the same tools.

Review my recent progress

How has the last two weeks gone? Anything I'm consistently getting wrong?

get_study_stats → list_review_history · study:read

list_review_history returns your review records — ratings and timing, filterable by notebase or card — without note content. Pair it with list_cards if you want the assistant to name the words you keep missing, which adds notes:read.

Change the daily limits

Twenty new cards a day is too many with everything else going on. Halve it for my Japanese notebase.

get_study_settings → update_study_settings · study:write

These two reach only the daily new-card limit, the daily review limit and the desired retention. They cannot rename or delete anything.

Housekeeping

Check which account is connected

Which Read Frog account are you connected to?

whoami · account:read

Worth one turn when you have more than one account, or before letting an assistant write anything.

Clean out what you no longer want

I've got duplicate entries in my English notebase. List them and delete the redundant ones, but show me the list first.

list_notes → delete_note · notes:write

Deletions here are permanent and they cascade: a deleted note takes its cards and their review history with it. delete_notebase goes further and removes the notebase whole — fields, notes, templates, cards, review records. Ask for the list before the delete.