Research Institute Office Buddy

Problem

Researchers in institutes often lose time to meeting notes, fragmented progress updates, procurement, reimbursement, and hazardous-materials approvals. The hard part is not drafting formal documents, but converting informal speech, internal jargon, and process requirements into complete task lists without missing nodes, deliverables, or risks.

How it works

The skill uses dual-engine routing: fast translation for everyday fragments and deep review for administrative workflows.
- Engine A: reads glossary.md and examples.md, then turns phrases such as “扯皮” and “排个期” into structured documents or task lists without follow-up questions.
- Engine B: when input involves procurement, reimbursement, safety checks, equipment changes, or project initiation, it retrieves knowledge_processes.md and outputs process steps, compliance requirements, and key deliverables.
- Experience capture: it records new jargon and pitfall notes implicitly, then exports them as Markdown blocks only when the user triggers 整理知识库 or 导出待入库清单; human review is required before adding them to files.

Boundaries

• Output quality depends on how well glossary.md, examples.md, and knowledge_processes.md are maintained.
• It does not write files automatically and does not replace legal, finance, or safety review.
• If SOPs are missing or outdated, the generated task list may still omit institute-specific steps.