Update to SHIP

{
  "description": "Use when the user wants to schedule a task that SHIP runs every day, week or month, such as a dependency update. It runs SHIP missions on a schedule. Create a scheduled task from a prompt or a template, change its schedule or prompt, or turn it off and on. Run it now, read what its past runs did and cost, and delete it. For example, the user says \"every Monday, have SHIP update our dependencies\" or \"run a flaky test sweep each week\". Also use it when the user asks what the last scheduled run did, or which scheduled tasks a project has.",
  "included_files": [],
  "name": "ship-scheduled-tasks",
  "skill_md_contents": "---\nname: ship-scheduled-tasks\ndescription: Use when the user wants to schedule a task that SHIP runs every day, week or month, such as a dependency update. It runs SHIP missions on a schedule. Create a scheduled task from a prompt or a template, change its schedule or prompt, or turn it off and on. Run it now, read what its past runs did and cost, and delete it. For example, the user says \"every Monday, have SHIP update our dependencies\" or \"run a flaky test sweep each week\". Also use it when the user asks what the last scheduled run did, or which scheduled tasks a project has.\n---\n\n# Run missions on a schedule\n\nA scheduled task is a prompt with a cadence. At each run, SHIP files an issue with the prompt as its description, and a\nnormal mission starts on it. The board, the review, the tests and the proof of that mission are the same as for any\nother mission.\n\nThis skill needs the `ship` CLI and a `SHIP_API_TOKEN`. If you do not have them, do the setup at\n<https://letsship.ai/SKILL.md> first. If this file has no `version` in its frontmatter, you read the hosted copy, so do\nthe setup too. If its `version` is older than `ship --version`, run `ship init --force`.\n\n| Command | Token scope |\n| --- | --- |\n| `ship schedule list`, `ship schedule get`, `ship schedule runs`, `ship schedule templates` | `scheduled-tasks:read` |\n| `ship schedule create`, `ship schedule update`, `ship schedule delete` | `scheduled-tasks:write` |\n| `ship schedule run` | `missions:run` |\n\nChanges also need the admin or owner role in the organization. Each run uses credits, like any mission.\n\n## See the scheduled tasks\n\n```bash\nship schedule list\nship schedule list --project prj_123\nship schedule get aut_123\nship schedule templates\n```\n\n`ship schedule list` shows each task with its cadence and its next run. With `--project`, it lists the tasks of one\nproject. `ship schedule get` also prints the prompt.\n`ship schedule templates` shows prepared prompts, each with a suggested cadence.\n\n## Create a scheduled task\n\n```bash\nship schedule create --name deps --template dependency-upgrades\nship schedule create --name triage --file triage.md --every weekly --day monday --time 09:00 --timezone Europe/Amsterdam\nship schedule create --name report --file report.md --every monthly --day 1 --time 06:00 --timezone UTC\n```\n\nThe schedule is `--every daily`, `weekly` or `monthly`, with `--time` and `--timezone`. A weekly task also needs `--day`\nwith a weekday. A monthly task needs `--day` with a day from 1 to 28. With `--template`, the task takes the prompt of the\ntemplate, and its suggested schedule unless you give one. With `--file` too, the prompt of the file replaces the prompt\nof the template. Give `--project <id>`, or set `SHIP_PROJECT_ID`.\n\nWrite the prompt like a good issue:\n\n- Write the acceptance criteria as checkboxes, because the QA agent tests against them.\n- Say what an empty result is, for example \"if no dependency has an update, change nothing\".\n- Do not ask the agent to change the CI configuration. Nobody watches a scheduled run, and SHIP blocks that change\n  without a person.\n\nWhile the mission of the last run is still open, SHIP skips the next run. Thus a weekly task cannot open a second pull\nrequest that conflicts with the first.\n\n## Change, stop or delete a scheduled task\n\n```bash\nship schedule update aut_123 --file triage.md\nship schedule update aut_123 --every daily --time 07:30 --timezone UTC\nship schedule update aut_123 --disable\nship schedule update aut_123 --enable\nship schedule delete aut_123\n```\n\nOnly the values that you give change. To change the schedule, give `--every`, `--time` and `--timezone` together, and\n`--day` when the interval needs it. `--disable` stops the runs and keeps the task and its history. Delete a task only\nwhen the user asks for it, because its run history goes with it.\n\n## Run a task now, and read its runs\n\n```bash\nship schedule run aut_123\nship schedule runs aut_123\nship schedule runs aut_123 --limit 20 --cursor eyJhIjoxfQ\n```\n\nThe command `ship schedule run` starts a mission now, outside the schedule. It also runs when the mission of the last\nrun is still open. The command `ship schedule runs` lists the past runs, each with its status, its mission and the cost\nof that mission. When older runs exist, the last line gives the `--cursor` for the next page. A `dispatched` run filed\nits issue, but that does not say whether the work passed. Read the mission\nwith `ship status` for that.\n\n## Exit codes\n\nEvery command also takes `--json`, which prints the raw API response.\n\n| Exit code | Meaning | What to do |\n| --- | --- | --- |\n| 2 | The arguments are wrong, or the API refused the schedule. The message names the problem. | Fix the command. |\n| 3 | The token is not set, or it does not have the scope of the command, or the role cannot change it. | Ask the user for a token with the scope, from an admin. Do not retry. |\n| 4 | SHIP found no such scheduled task, template or project. | Check the id with `ship schedule list`, or give `--project <id>`. |\n| 5 | The organization has no credits for a run now. | Tell the user. Check the balance with `ship credits`. |\n| 6 | The organization did not finish the onboarding. | Ask the user to finish it in the console. |\n| 8 | Too many requests, or the organization reached a daily limit. | Wait, then run the command again. Tell the user about a daily limit. |\n"
}