lab-meeting-report
Weekly Research Meeting Summaries
Turn the user's scattered weekly research material into a report they can present, discuss, and archive. Keep the default interaction lightweight: the user supplies the material; infer the structure. Apply evidence safeguards in the background instead of making the user complete an audit form.
Choose the output language in this order: follow an explicit language request, otherwise match the language of the user's request, and use English only when a genuinely mixed-language request is ambiguous. Preserve technical terms, model names, abbreviations, metric names, equations, citations, and identifiers in their source form.
Input contract
Accept a natural-language request without forcing the user to fill a form. Treat the source scope as the only required input. Pasted notes, a description of this week's work, and attached material count as sources. Resolve relative paths and globs against the active project.
Extract these optional preferences when supplied:
- Sources: pasted updates, notes, papers, results, figures, screenshots, code changes, or explicitly scoped Feishu/Lark and Notion resources;
- Focus: the message, question, or problem the user wants the group to understand;
- Mode: research progress, paper review, or mixed;
- Meeting context: stage (
before,after, orboth), audience, duration, previous actions, and meeting notes; - Output: language, date, detail (
brief,standard, oraudit), and destination path; - Publishing: local only, Feishu/Lark, Notion, or both;
- Presentation: plain Markdown outline, Marp, Quarto, or editable PPTX when a compatible adapter is available.