Update to Kowalah

{
  "description": "Help someone set up a scheduled task in their AI assistant that brings them something useful from Kowalah on a regular basis — what's new in their accelerator library, a draft of their weekly programme update, the week in their area, progress against their vision, or ideas from their own work. Suggests ideas that fit their role, lets them choose, then writes the task. Use for \"set me up a weekly update\", \"keep me posted on new accelerators\", \"can this run every Friday\", \"remind me each week\", \"automate my steering update\", or \"what could I schedule?\".",
  "included_files": [
    {
      "relative_path": "references/ideas.md",
      "size_in_bytes": 4541
    }
  ],
  "name": "scheduled-tasks",
  "skill_md_contents": "---\nname: scheduled-tasks\ndescription: Help someone set up a scheduled task in their AI assistant that brings them something useful from Kowalah on a regular basis — what's new in their accelerator library, a draft of their weekly programme update, the week in their area, progress against their vision, or ideas from their own work. Suggests ideas that fit their role, lets them choose, then writes the task. Use for \"set me up a weekly update\", \"keep me posted on new accelerators\", \"can this run every Friday\", \"remind me each week\", \"automate my steering update\", or \"what could I schedule?\".\n---\n\n# Scheduled tasks\n\nA scheduled task is a prompt the person's assistant runs on a timetable, on its own: every\nMonday morning, every Friday afternoon, the first of the month. Set up well, it brings\nthem something they'd otherwise have to remember to ask for. This skill suggests tasks\nthat fit them, lets them choose, and writes the task so it works without this\nconversation.\n\n**The person chooses and creates the task.** You suggest; they decide what runs, how\noften and where the results go. Nothing is set up without their yes.\n\n## 1. Who they are\n\nCall `kowalah_get_update` with no query. It gives their role in the organisation (admin,\ncore team or member) and, where set, their home unit. If they belong to more than one\norganisation, ask which one this is for.\n\nThen ask, in one go:\n\n- **What would they like to hear about, or stop doing by hand?** Their answer beats any\n  suggestion.\n- **When?** Which day and time suits them, and how often.\n- **Where should the result go?** A message in their assistant is the default. If they\n  have email, chat or a document store connected, they may want it there instead.\n\n## 2. Suggest a few ideas\n\nRead `references/ideas.md` and suggest two or three ideas that fit their role and what\nthey told you. Say in a sentence what each would give them, and let them pick one. One\ngood task they keep beats four they switch off.\n\nIdeas fall into two kinds:\n\n- **Ones that tell them something:** what's new in their library, the week in their area,\n  progress against the vision. Read only. A good first task for anyone.\n- **Ones that draft something for them:** their programme update, ideas from their own\n  work. The task prepares a draft; the person reviews it and decides what happens next.\n\n## 3. Write the task, then create it\n\nWrite the task prompt from the matching idea's template, filled in for this person. A\nscheduled run starts fresh, with none of this conversation, so the prompt must stand on\nits own:\n\n- **Name the organisation and, if it applies, the unit**, by name, so the run doesn't\n  have to ask.\n- **Say what to call and how to read it**, including \"use the date of the previous run as\n  `since`; on the first run, use seven days ago\".\n- **Say exactly what to report and in what form,** including what to say when there's\n  nothing new. A short \"nothing new this week\" is better than padding.\n- **Include the rules below** that apply to the idea.\n\nShow them the prompt, the timing and where the result goes. Change anything they want.\nThen, once they say yes, ask the assistant to create a scheduled task with that prompt and\ntiming. If their assistant can't create scheduled tasks, or they'd rather do it\nthemselves, give them the prompt and timing to set it up in their assistant's settings.\n\n## Rules for every scheduled task\n\n1. **Nothing is shared or saved on its own.** A scheduled run reads and drafts. Anything\n   that would be written to Kowalah (an opportunity, a process change, an outcome) is put\n   to the person to approve, never submitted by the run.\n2. **Report what was checked.** The \"what's new\" answer lists what it `covers`. Report\n   those, and don't suggest anything else was looked at.\n3. **Steps, not people.** When a task describes work, delays or constraints, it describes\n   steps in a process, never named colleagues.\n4. **Their own work stays theirs.** A task that looks at the person's own calendar or\n   documents leaves personal items out, only suggests, and shows them everything before\n   anything goes further.\n5. **Quiet when there's nothing.** If nothing has changed, say so in a line and stop.\n\n## Hand-offs\n\n- To change or stop a task later, the person does it in their assistant's settings, or\n  asks their assistant.\n- If a run turns up something worth acting on, the person can pick it up with\n  `raise-opportunity`, `process-diagnostic` or `programme-views` in a normal\n  conversation.\n"
}