Keep recurring work on track

When to use it#

Use this skill for a recurring activity such as a Friday review, a one-time reminder, marking a specific item done or reviewing routine completion. Ordinary reminders run through OwnPost’s scheduler without an AI runner.

You can also request generated preparation immediately. That workflow needs the connected client to claim and finish the work; saving a routine alone does not launch a model.

What you need#

Full workspace access for managing routines and their completion. Supply the activity and schedule; your saved timezone can be reused. Telegram is optional and must be connected if you want delivery there.

Install or select the skill#

The ownpost entry skill includes this workflow. Use the command above if you want ownpost-routines as a separate shortcut, or select it from your installed plugin.

Try it#

Select the skill in your connected assistant, then adapt these examples to your own content.

Use the ownpost-routines skill to remind me every Friday at 6 PM to review measured posts and choose one experiment. Use my saved timezone and send it to Telegram.

Use the ownpost-routines skill to mark the selected review item done, then show my routine completion for the last seven days.

How it works#

1. 1

   Ask for the routine, occurrence action or progress review. The assistant reads existing definitions and pending items first so it can match the intended record.

2. 2

   For a routine, provide a title, instructions, local schedule and Telegram choice. Existing enabled state and other options stay unchanged unless you ask to change them.

3. 3

   For a due item, request Mark done, Skip or Snooze 10m. The action uses that occurrence’s current revision and appears in the same app and Telegram history.

4. 4

   For analytics, read due, completed and skipped counts and the last-seven-days table. The completion rate is completed items divided by all due items tied to saved routines.

5. 5

   For Prepare now, check that the actual preparation completed and its output was saved. A queued request alone is not the finished result.

Check the result#

The routine has a saved local schedule, the selected occurrence has its confirmed state, or the requested progress review uses aggregate routine statistics. Completed and skipped items remain in history.