菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when setting up a new personal LLM Wiki — an agent-maintained, interlinked markdown knowledge base. Interviews the user about their domain, scaffolds the raw/wiki/schema structure, writes a tailored schema file (CLAUDE.md / AGENTS.md), and seeds the index, log, and overview.
Use when integrating a new source (article, paper, note, meeting transcript, book chapter) into an LLM Wiki — reads the source, writes a summary page, updates entity/concept/topic pages, maintains cross-references, and records the work in the index and log.
Use when health-checking an LLM Wiki — finds contradictions, stale claims, orphan pages, broken links, missing cross-references, and schema violations, then produces a prioritized report and offers fixes.
Use when answering a question from an LLM Wiki — navigates the index, reads relevant pages, synthesizes a cited answer, and offers to file valuable answers back into the wiki as analysis pages so explorations compound.
Use when the user wants to deeply learn a concept, form an opinion, or stress-test their understanding through fact-grounded Socratic dialogue — a 50:50 mix of providing information and challenging with counterarguments, grounded in their wiki and web research.
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.
| 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. |
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.
/tiro:schedule-sync [optional: cadence, e.g. "daily 7am", "weekdays 9am"]
tiro auth status), and the wiki root must be known. If either is missing, fix that first (/tiro:sync prerequisites)./tiro:sync workflow against <wiki-root>, non-interactively, ingesting everything new since the last run.log.md as usual so the user can audit what happened while they were away.log.md rather than retrying in a loop.