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.
Install
$ agentstack add skill-plato-corp-skills-schedule-sync ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-plato-corp-skills-schedule-sync) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- 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:syncprerequisites). - Pick the cadence. Default: daily at 07:00 local time. Honor whatever the user asks.
- 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:syncworkflow against ``, 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.
- Dry-run once. Execute one sync immediately so the user sees it work before trusting the schedule.
- 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.mdas 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.mdrather than retrying in a loop.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: plato-corp
- Source: plato-corp/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.