# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-plato-corp-skills-schedule-sync`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [plato-corp](https://agentstack.voostack.com/s/plato-corp)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [plato-corp](https://github.com/plato-corp)
- **Source:** https://github.com/plato-corp/skills/tree/main/plugins/tiro/skills/schedule-sync

## Install

```sh
agentstack add skill-plato-corp-skills-schedule-sync
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## 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

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 ``, 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.

## 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](https://github.com/plato-corp)
- **Source:** [plato-corp/skills](https://github.com/plato-corp/skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-plato-corp-skills-schedule-sync
- Seller: https://agentstack.voostack.com/s/plato-corp
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.