---
name: "task-ops-sync"
type: task
description: "Scheduled deployment of skill-ops-sync — the Claude→claude-ops parity audit. Loader only; the behaviour lives in skill-ops-sync. Cloud scheduled run on the Linear connector, with live reads of origin/main in the claude-ops repository."
license: CC BY-NC-SA 4.0
---

# task-ops-sync

Scheduled deployment of `skill-ops-sync`. This task carries no behaviour of its own — it is a loader.

**Read the canon artefact `skill-ops-sync` (the saved skill of that name; locally at `.claude/skills/skill-ops-sync/SKILL.md`) and follow it verbatim.**

Run context: cloud scheduled run with live reads of `origin/main` — the Linear connector plus a network-capable `claude-ops` checkout, so the parity audit compares canon against the branch rather than against a local mirror of unknown age. This is surface-scoped and not a general claim: it states what *this* task's surface can do, and says nothing about what any other scheduled surface can. The Mac Cowork task is off and its hourly pull is gone, so the old local-clone, no-GitHub-network reading of this line describes nothing that still runs. Propose only — never commit to the repo, never edit Claude, never delete.

To change *what ops-sync does*, edit `skill-ops-sync` — never this file or the scheduled-task config. Add steps **here** only if this task must ever sequence more than the single skill.

## Final step — capture telemetry

On finish, read the canon artefact `skill-telemetry-capture` (the saved skill of that name; locally at `.claude/skills/skill-telemetry-capture/SKILL.md`) and follow it verbatim, passing `task: task-ops-sync` and this run's own `outcome` (e.g. `completed`, `blocked`).