From research-app-toolkit
Generates slide decks for PhD interviews, professor meetings, and research presentations from CVs, projects, and supervisor info, with slide content and speaking notes.
npx claudepluginhub xujingchen1996/research-app-toolkitThis skill uses the workspace's default tool permissions.
This skill organizes application materials into a professor-meeting or research-interview slide deck.
Generates professional slide decks for pitch decks, business presentations, training materials, and conference talks using each::sense AI.
Builds slide decks for research talks using PowerPoint or LaTeX Beamer. Provides structure, design templates, timing guidance, and visuals for conferences, seminars, thesis defenses.
Builds slide decks for scientific research talks, conferences, seminars, and defenses. Provides structure, design templates, visuals via Nano Banana Pro AI. Supports PowerPoint, LaTeX Beamer, PDF.
Share bugs, ideas, or general feedback.
This skill organizes application materials into a professor-meeting or research-interview slide deck.
It focuses on:
It does not need to generate a .pptx file unless the user explicitly asks for file creation.
Use the following sources in this order:
${CLAUDE_PLUGIN_ROOT}/.local.mdIf the user has not run /ra:cv-analyze but has already provided enough materials in the current conversation, continue directly instead of blocking.
Identify the intended deck mode. If the user does not specify, infer from context:
meeting: first contact, supervisor meeting, informal academic discussionformal-interview: PhD interview, scholarship interview, panel interviewproject-presentation: focused explanation of selected projectsIf uncertain, default to formal-interview.
Decide visual mode before writing the deck. Use this priority order:
$ARGUMENTSSupported explicit switches:
visuals:onvisuals:offwith-visualsno-visualsRules:
on.off even if visuals are mentioned elsewhere.off.on, use any image-generation capability available in the current host. If image generation is unavailable, fall back to image prompts plus layout guidance.First determine:
on or offThen propose a compact deck structure. Prefer concise academic decks rather than CV-like slides.
Typical sections:
For project slides, do not simply repeat documentation sections such as background / aim / summary.
Prefer interview-friendly structures such as:
If the user wants clearer presentation logic, prioritize:
For each slide, provide:
The wording should be academic, direct, and easy to speak aloud.
If the user asks for speaking notes, write short, natural English scripts.
Default speaking-note style:
If visuals are helpful and visual mode is off, suggest one of:
If visual mode is on:
For project visuals, prefer:
When the deck includes a supervisor-fit section:
Good fit slides usually answer:
If the user asks for future research interests, avoid generic keyword-only lists.
Prefer 2 to 3 mini-proposals with:
If the user wants the slide shorter, compress each item into:
Prioritize high-value output in this order:
on, otherwise visual suggestionsWhen the user is already editing a deck, do not regenerate the whole presentation unless asked. Focus on the specific slide or section being revised.