repo-schedules-test

End-to-end smoke test for the `tessl launch skill --cloud` pipeline. Reads one Linear issue (read-only) via the Linear API to prove `LINEAR_TOKEN` is wired into the sandbox, appends a single run-marker line to a log file, then opens a GitHub pull request with that one-line change to prove `GITHUB_TOKEN` and the publish path work. Use whenever you need to verify a cloud launch can reach Linear and GitHub and open a PR end to end -- dogfooding the launch pipeline, checking that credentials forward into the sandbox, or as a minimal known-good skill to launch when debugging the launch flow itself. Self-contained: driven by launcher-supplied inputs plus `LINEAR_TOKEN` and `gh` credentials in the environment. Makes no Linear writes; its only change is the one appended log line in the PR it opens.

Pulls recently updated Linear issues (read-only) and writes them into a Markdown digest file in this repo, then opens a pull request with that change. Use to prove a scheduled run can reach Linear, turn what it read into a repo artifact, and publish it through a PR. Runs unattended: it asks no questions and makes no Linear writes.

Triage Linear issues in a team's Triage state. Categorizes issues as straightforward, needs-discussion, or stale/duplicate. Optionally scopes the straightforward ones with effort estimates via parallel sub-agents, then recommends which to delegate to the Oz Linear agent. Use when the user asks to triage a Linear team's triage inbox.

Reads recently edited pages from the notion MCP server (read-only) and writes what it found into a Markdown digest in this repo, then opens a pull request with that change. Runs unattended: it asks no questions and makes no writes to notion.

Reads recent project insights and events from the posthog MCP server (read-only) and writes what it found into a Markdown digest in this repo, then opens a pull request with that change. Runs unattended: it asks no questions and makes no writes to posthog.