メニュー
Walk the user through new Thoth features since their last onboarding or update. Use when the user asks "what's new", "what changed", or "what can you do now". Also use after check_whats_new returns updates to walk through them.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Initialize a new user's research assistant. Use this on first interaction or when user asks to "get started", "set up", or "introduce yourself". Also use when you don't know the user's research interests or the human memory block still has placeholder text.
Create, manage, and iterate on research plan documents in the Obsidian vault. Use when the user asks for a research plan, literature review roadmap, or when you need to formalize your own working research strategy.
Conduct deep analysis of research papers, synthesize literature, and generate comprehensive reviews. Use when user needs thorough paper analysis, literature reviews, or cross-paper synthesis.
Manage external knowledge collections (textbooks, lecture notes, background material) and search them to support research. Use when user wants to upload reference material or query foundational knowledge.
Answer questions using your existing research collection and external knowledge. Use when user asks questions about papers they have, wants summaries, or seeks insights from their knowledge base.
Customize what information is extracted from papers (schema) and how it's extracted (prompts). Use when the user wants to change analysis fields, instructions, or prompt templates.
| name | whats-new |
| description | Walk the user through new Thoth features since their last onboarding or update. Use when the user asks "what's new", "what changed", or "what can you do now". Also use after check_whats_new returns updates to walk through them. |
| tools | ["check_whats_new","search_documentation","load_documentation"] |
Walk the user through features that have shipped since they last used the system. The goal is a brief, conversational update — not a changelog dump.
Call check_whats_new with the last_seen_version from the human memory block. If the field isn't set, pass "0.0.0".
The tool returns the current server version and a list of changes grouped by version.
Narrate the changes conversationally. Don't read the changelog line by line — group related things and explain what they mean for the user's workflow.
For each significant update, offer a brief demo or next step:
"One thing that's new is [feature]. This means you can now [what it unlocks]. Want me to show you an example?"
If they're curious about something, use search_documentation to find the right doc and load_documentation to read it in full.
Once they've been through the walkthrough (or if they say "skip it"), update last_seen_version in the human memory block to the current server version. Use memory_replace on the human block.
Don't wait for them to explicitly confirm — once you've presented the summary and they've responded (even just "thanks"), that counts.
Keep it brief and practical. Users don't want a product announcement — they want to know if anything changes how they do their work. Lead with "here's what's relevant to you" rather than "here's everything that changed."
