Skip to content
Skills Library
AI & agents · Automation

schedule-sync

/schedule-sync

Use when the user wants Tiro notes to flow into their LLM Wiki automatically on a schedule — registers a recurring job (agent scheduled task or cron) that runs the sync workflow daily or at a chosen cadence.

Repository
skills ↗
Licence
MIT
Last repository change
19.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user wants Tiro notes to flow into their LLM Wiki automatically on a schedule — registers a recurring job (agent scheduled task or cron) that runs the sync workflow daily or at a chosen cadence.

Original author description

Use when the user wants Tiro notes to flow into their LLM Wiki automatically on a schedule — registers a recurring job (agent scheduled task or cron) that runs the sync workflow daily or at a chosen cadence.

How it works

  1. Usage
  2. Workflow
  3. Notes
Original SKILL.md headings · 26 lines, 264 words
SKILL.md preview
---
name: schedule-sync
description: Use when the user wants Tiro notes to flow into their LLM Wiki automatically on a schedule — registers a recurring job (agent scheduled task or cron) that runs the sync workflow daily or at a chosen cadence.
---

# Schedule Sync — recurring Tiro → wiki sync

Register a recurring job so `/tiro:sync` runs without anyone remembering to run it. A wiki that stays current by itself is the difference between a knowledge base and a graveyard.

## Usage

```
/tiro:schedule-sync [optional: cadence, e.g. "daily 7am", "weekdays 9am"]
```

## Workflow

1. **Confirm prerequisites.** The Tiro CLI must be installed and authenticated (`tiro auth status`), and the wiki root must be known. If either is missing, fix that first (`/tiro:sync` prerequisites).
2. **Pick the cadence.** Default: daily at 07:00 local time. Honor whatever the user asks.
3. **Register the job**, preferring the most native mechanism available:
   - **Agent scheduler** — if your harness supports scheduled/recurring tasks (e.g. Claude Code scheduled tasks / cron-style jobs), register the sync prompt there: run the `/tiro:sync` workflow against `<wiki-root>`, non-interactively, ingesting everything new since the last run.
   - **System cron fallback** — otherwise, offer a crontab entry that invokes the agent CLI headlessly with the same prompt. Show the exact line before installing it; never edit crontab without showing the user first.
4. **Dry-run once.** Execute one sync immediately so the user sees it work before trusting the schedule.
5. **Report.** What was registered, when it runs, how to list/remove it.

## Notes

- Scheduled runs must be non-interactive: skip discussion steps, ingest everything new, log to `log.md` as usual so the user can audit what happened while they were away.
- If a scheduled run hits an auth failure, it should stop and leave a clear note in `log.md` rather than retrying in a loop.

Versions

The database has no other skills named schedule-sync.

Database snapshot: 13.11.2026 · package version c828aa06a152 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100sync
    Use when syncing Tiro meeting notes and transcripts into an LLM Wiki — discovers notes not yet ingested, downloads them into raw/ via the Tiro CLI, and runs the ingest workflow on each, idempotently and without ever modifying existing raw files.
  • 100cron-scheduler
    Schedules recurring or delayed agent tasks. Use for: schedule this, run daily, cron job, set timer.
  • 100scheduling
    Set up recurring or scheduled work — anything the user wants run on a schedule, repeatedly, or at a future time ("every morning", "each weekday at 9am", "daily digest", "weekly report", "remind me", "run this on a cron"). Teaches how to make a routine — the person's own flow, a…
  • 100autonomous-sync
    Use this skill when the user wants to keep their Aicoo agent updated automatically, set up scheduled syncs, configure triggers for knowledge updates, use CRON jobs, /loop commands, file watchers, or hooks to push changes to Aicoo. Triggers on: 'auto sync', 'keep updated',…
  • 86wiki-ingest
    把 agent 会话里的知识摄入 Meiqiu 知识库(个人 LLM Wiki)。当用户要求把会话摄入知识库、提炼知识到 wiki 时使用。
  • 100loopify
    When you want to set up an agent loop, cron-scheduled task, or recurring workflow that runs autonomously. Judgment layer on top of Claude Code's ScheduleWakeup, CronCreate, and /loop — or, on other hosts, cron/GitHub Actions plus a headless agent CLI. Picks dynamic pacing, fixed…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.