菜单
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.
用 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 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.
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 | query |
| description | 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. |
Answer a question using the wiki as the knowledge base, with citations, and file good answers back in.
/tiro:query [question]
index.md (or search page names/content) to shortlist relevant pages. Don't bulk-read the whole wiki.raw/ originals and the question needs depth, go to the originals.wiki/analyses/ with the original question in the frontmatter. Good answers should not evaporate into chat history; this is how exploration compounds.If the tiro CLI is installed and authenticated, the user's Tiro workspace is a second knowledge base you can search alongside the local wiki:
tiro notes search "<query>" --since 90d --json
tiro wiki search "<query>" --json
Use it when the question touches meetings, decisions, or conversations that haven't been ingested into the local wiki yet. If tiro is not installed, skip this silently.