How to save a task you repeat in Cirra as a skill
Type the instructions once, save them as a Cirra skill and test it on new notes, so the format stays and last week's facts don't.
Group it by project. Say what's done, what's stuck and who's next. Keep it plain, don't invent dates. You type some version of that paragraph into Cirra every Friday, then paste in this week's notes. The notes change. The paragraph never does, and you've typed it about forty times.
Save that paragraph as a skill once, and it stops being typing. Tell Cirra to save how the task is done. Then use the skill in a later task: hand it new notes and get the same shape back.
What you need
A Cirra account. Starting is free.
A task you do the same way at least once a week. This example uses a project update.
Last week's notes and this week's notes, so you can test on both.
1. Do it once the long way
Get one good result before you save anything. A skill copies whatever you give it, including the mistakes.
Draft this week's project update from these notes. Group it by project. Under each, list what got done, open decisions and who acts next. Plain language. If a date or owner is missing, say it's missing. Don't send it.
A draft grouped by project, with gaps marked as missing instead of filled with a guess.
Put blocked items first under each project.
2. Save the how, not the what
The structure and the rules are worth keeping. This week's projects and dates aren't. If they end up in the skill, next week's update starts out wrong.
Save how you wrote that update as a skill called Project update draft. Keep the structure and the rules. Leave out this week's projects, names and dates.
A saved skill with a name you'll recognize in a month.
Show me the skill's instructions so I can check them.
3. Test it on notes it hasn't seen
Running it on the same notes proves nothing. Use a different project, or a week where something is missing.
Use the Project update draft skill on these notes for the warehouse move.
The same shape with new facts. If the notes don't name an owner, the draft says so.
Keep the missing-owner line. Don't fill it in.
4. Fix the rule, not the week
If you find yourself making the same correction every time, change the skill. If one project's facts are wrong, fix the notes instead. Rules belong in the skill. Facts belong in the task.
Update the Project update draft skill: end each update with a one-line list of decisions needed this week.
The skill changes once, and every update after it picks up the new line.
Run the updated skill on last week's notes and show me the decisions line.
What it doesn't do yet
A skill doesn't run on its own. It's used when you ask for it.
It doesn't start when something happens in another app.
It only reaches the apps you've connected, with your own access.
It doesn't check your notes. A wrong fact in goes out as a wrong fact.
Type it one last time
Pick the instructions you've typed most often this month. Run them once, save them and test them on next week's notes. Before a saved skill acts in one of your apps, read How to check which account a Cirra connection uses before a task acts.