Repeat tasks by your own rules

Already taught the agent a task? Save that work

In Octodus, a saved way of working is called a skill. It is an instruction for the agent: a sequence of actions, decision rules, your clarifications, samples and a check of the result. You can save a small routine task or a process with several steps.

For example, you taught Octodus to sort requests by priority, prepare a briefing on a client, adapt texts to your style or collect feedback on a mockup. Once the result works for you, ask it right in that conversation to turn the whole process into a skill. You do not need to write the instruction by hand.

We have refined this task. Save the whole agreed process as a skill, so you can run it the same way from now on without me explaining it again.

Include my corrections, the sequence of actions, the selection rules, the formatting requirements and the result checks. Use the latest agreed version of the process.

Also tell me what I need to provide as input for each run. Take new dates, figures, files and other variables from the next task.

Suggest a clear name, create and save the skill. Show me its contents, where it is available and which short phrase I can use to run it.

What to prepare

• Pick a repeatable task and open the conversation where you will set it up. Show Octodus the source materials and an example of a result you are happy with.
• Below, we walk the whole path with a weekly report: set it up, save the process and repeat it on another file. For the exercise, download the data for two weeks.
• The practice report needs a short summary, a table of metrics and questions for the manager. For your own task, set the steps and format you are used to.

The source files contain practice data. Replace it with your own once you have the process down.

Teach Octodus to prepare a report your way

Start with week 1. Ask Octodus to check the source and prepare a report. Then refine the result in the same conversation: "Cut the summary to three points," "Show the count first, then the share," "Move unanswered questions to the end."

These corrections teach the agent your way of working. Explain both the step itself and the condition that triggers it: for example, if there is no data to compare against, Octodus should say what is missing. Keep refining until the result meets your requirements.

Prepare a weekly report from the attached file. Start with a short summary, then a table of inquiries, meetings and deals, and finish with questions for the manager. Use only data from the file. Do not invent reasons for changes. If there is not enough data for a comparison or calculation, say so.

Lock the whole process into a skill

When the report works for you, ask Octodus to save the way it is prepared, together with all the agreed corrections. The agent builds an instruction from the conversation: what to receive as input, in what order to act, how to format the result and what to check.

Read the saved rules. Make sure the important clarifications from the conversation made it in. Set the period, project name and metrics again for every run, so the skill works with different sources.

Save our refined process as a skill called "Weekly Report". Include all the corrections we agreed on in this conversation: the order of work, the report structure, the calculation rules, how to handle missing data and the result check.

For every run, take the dates, project and metrics from the new files. Show me the saved rules and how to call the skill in the next task.

Next time, hand over new data

Now it is enough to name the skill and attach the sources. Use the way of calling it that Octodus showed you when it saved the skill. You no longer need to explain the workflow in detail again.

For the exercise, attach the second file and the week 1 data for comparison. Check that Octodus followed the familiar sequence, kept your corrections and took the current figures from the new file.

Prepare a report using the "Weekly Report" skill. I am attaching the data for August 31 to September 6 and the previous week for comparison.

Example result

The catch, and how to check

Ask specifically to create and save the skill, then check its contents and a repeat run. That way you confirm the rules you need are available for future tasks. Provide current sources on every run. If the work should run on a schedule, set the schedule up separately.

Before you use the result

• The skill exists and has a clear name and a way to run it.
• The saved instruction contains your steps, conditions, corrections and requirements for the result.
• Dates and metrics come from the new files, and calculations are checked against the source.
• A repeat run follows your pattern without you explaining all the rules again.

How to repeat this on your own task

A skill can evolve together with the process. For example: "From now on, put the three main changes at the top of the report. Update the 'Weekly Report' skill so this rule applies to future runs." Ask to see the updated instruction and test it on a new task. That is how your way of working gets sharper over time.