| name | htools-htask-sync |
| description | Run every htask source-sync in one go — GitHub issues assigned to me and commitments I made in Slack — then print a single combined report. Use when asked to sync my tasks, sync everything, pull all my work, or run the syncs. |
htools-htask-sync
The umbrella over the per-source syncs. It runs each in turn and prints one
combined report; it owns no sync logic of its own. Each source's semantics —
join key, what's created vs skipped, create-only vs mirror — live in that
source's skill and must not be duplicated here.
Run
Invoke each source-sync skill, in order, as its own step:
htools-htask-gh-issue-sync — GitHub issues assigned to me.htools-htask-slack-commitment-sync — commitments I made in Slack.
Run them independently: a failure or a needed interaction in one must not abort
the other. Do GitHub first so its result is already banked, then Slack — the
Slack sync may stop for an OAuth prompt (the claude.ai Slack connector), and
if it can't complete right now, finish the report with GitHub's numbers and flag
the gap rather than stopping. Each leaf skill is idempotent, so re-running the
whole thing is always safe.
Report
One combined summary — a labeled line per source carrying that skill's own
buckets, and nothing else:
github: created N · text-updated N · done N · archived N
slack: created N · skipped N · rejected N
Append anything odd either skill surfaced (truncated search, auth needed, a ref
left flagged). If a source was skipped entirely, say which and why.
Adding a source
A new source joins the suite as its own htools-htask-<source>-sync skill that
owns its semantics; wiring it in here is one more numbered invoke above and one
more line in the report. Keep this skill a coordinator — no source logic leaks
in.
