Wake up to flashcards made from yesterday’s notes

Read as Markdown

Replace the [brackets] with your details, then paste this into your assistant.

Create a nightly pipeline from [selected notes folder] to flashcards for [learning goal and spaced-repetition app]. Use [time and timezone], make at most [ten] new cards per run, and exclude [folders, tags or sensitive content]. Start with a dry run and show me a sample batch before saving a recurring schedule or importing anything.

First verify the notes access, the app's documented import format or supported connection, and where the pipeline's state can persist. If direct app access is unavailable, produce an import-ready file and clear manual steps. A prepared file is not an imported deck; report each state accurately. For the first run, use [the last seven days or a chosen folder] rather than converting the entire archive.

Keep a manifest of stable note identities where available, file hashes or versions, processed sections, source references and managed card IDs. Each night compare with the last successful run, process only relevant new or changed material and skip unchanged content. Handle renamed files without treating every note as new. Preserve failed or partially completed items for a safe retry, with a run log that shows what was read, generated, skipped and imported.

Write one clear question per card with a concise answer, enough context to stand alone, a source link or filename and heading, and a topic tag. Prefer ideas I said I want to remember. Include a few application questions where the source supports them, not only isolated definitions. Flag ambiguous, contradictory or unsupported notes for review instead of inventing a confident answer. Exclude private personal details from examples. Deduplicate against both the existing deck and earlier generated cards, using stable IDs and a meaning check.

Put new cards and changed-card proposals in a review batch. My import policy is [review every batch, or automatically add only new cards that meet the explicit rules we approve after the sample]. Verify the destination deck and exact scope before enabling writes. Updates to existing cards require review and must preserve their study history through a documented supported method; never delete cards, reset review progress, overwrite an entire deck or publish it. Source deletions become review items, not automatic card deletions.

For an approved import, read back the resulting card IDs and counts when the connection supports it. Reconcile with the manifest before retrying so a timeout does not create duplicates. Leave unverified writes marked unresolved. If the app cannot provide a reliable update or readback path, keep the batch as a manual import for review.

Finish with a short morning report: notes changed, cards proposed, cards actually imported, skipped ambiguities and one preview. Configure delivery only to [approved destination], and verify the saved schedule's status. If scheduling is unsupported, return the working conversion steps and a manual run checklist instead of promising overnight execution.

Automatic copying is unavailable. Select the prompt text above and copy it.