Start, resume, or manage a guided tour of the project. Creates an interactive walkthrough with narrative and runnable code for each topic. Use when the user says "start tour", "give me a tour", "continue tour", "where were we", "tour status", or when presenting the project to someone.
How this skill is triggered — by the user, by Claude, or both
Slash command
/computational-research:start-tourThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
An interactive walkthrough of the project.
An interactive walkthrough of the project. Each section has narrative (what it is, why it matters) and runnable code (demonstrations, experiments). The LLM stops after each section for user feedback — this is the revision loop applied to presentation.
Wiki/ must exist with articles to tour.
If the wiki is empty, suggest running init-wiki and populating it first.
Tour/
Tour.md plan + position + progress
Sections/ one .md per section (narrative)
Code/ one file per section (runnable code)
Tour/ is gitignored — it's local, on-demand state.
If Tour/ doesn't exist, create it with Sections/ and Code/ subdirectories.
Read Wiki/Index.md and Wiki/Status.md to understand the project.
Order topics from simplest → most complex (prerequisites first).
Write Tour/Tour.md:
# Tour Plan
## Sections
1. [ ] Topic A — one-line summary
2. [ ] Topic B — one-line summary
3. [ ] Topic C — one-line summary
## Position
Current section: 1
Last interaction: YYYY-MM-DD
## Log
| Date | Section | Action |
|---|---|---|
| YYYY-MM-DD | — | Tour plan created |
Show the section list to the user. Wait for feedback — they may want to reorder, skip topics, or add sections.
For each section:
Generate narrative: Tour/Sections/NN_Name.md
Generate code: Tour/Code/NN_Name.wl (or .py, .lean, etc.)
Present to user: > "Section N: [Topic].
Narrative in Tour/Sections/NN_Name.md, > code in Tour/Code/NN_Name.wl.
Any feedback before we move on?"
Wait for response:
[x], update position, advance[-], advanceUpdate Tour.md after each interaction (position, log entry)
If Tour/Tour.md exists, read it to find the current position.
Tell the user where they left off and continue from there:
"Welcome back. Last time we covered [Topic N]. Ready for section N+1: [Next Topic]?"
# Section N: Topic Name
## Overview
What this is and why it matters. 2-3 paragraphs.
## Key concepts
- Concept A — brief explanation
- Concept B — brief explanation
## In the codebase
- `Code/File.wl` — what it contains
- `Wiki/Domain/Article.md` — deeper reading
## Try it
Run `Tour/Code/NN_Name.wl` to see [what the code demonstrates].
Self-contained Wolfram Language file (or whatever language the project uses). Should run without errors and produce visible output (plots, printed results, tables). Include brief inline comments for presentation context.
After each section interaction, update:
[ ] → [x] (or [-] for skipped)Current section: N+1| YYYY-MM-DD | N | Presented, user approved |
| YYYY-MM-DD | N | Presented, user revised: changed code example |
| YYYY-MM-DD | N | Skipped by user |
npx claudepluginhub wolframinstitute/claudepluginmarketplace --plugin computational-researchGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.