meeting-minutes-export
Skill1 starsChanged 4 months agoMITView on GitHub
Orchestrator that runs meeting-minutes then exports the result to Word (.docx). Use when the user wants both structured meeting minutes and a Word document. Depends on the local meeting-minutes skill and the md-exporter pip package.
- Installs packages
In this repository4 other files it gives its agents.
- eddx-translateSkill
- kb-ingestSkill
- meeting-minutesSkill
- pptx-translateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Follow the meeting-minutes skill workflow:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meeting Minutes Export
Convert a meeting transcript into both structured meeting minutes (.md) and a
Word document (.docx). This is a thin orchestrator that chains two steps.
Dependencies
| Dependency | Type | Role |
| meeting-minutes | Local skill | Extracts structured data, fills template → .md |
md-exporter (pip install md-exporter) | Python package | Converts .md → .docx via Pandoc |
Workflow
Step 1: Run meeting-minutes
Follow the meeting-minutes skill workflow:
- Gather transcript + template
- Extract structured data (attendees, agenda, discussion, decisions, action items, etc.)
- Fill template →
output.mdin CWD
Step 2: Install md-exporter (if missing)
pip install md-exporterStep 3: Convert to .docx
markdown-exporter md_to_docx <output.md> <output.docx>Custom style template — if the user provides a .docx style reference:
markdown-exporter md_to_docx <output.md> <output.docx> --template custom_style.docxUsers can create the template in Word or LibreOffice by styling the built-in
names (Heading 1/2/3, Normal, Table Grid), saving it as .docx, and uploading
it. Under the hood md_to_docx passes --reference-doc=<path> to Pandoc.
Priority:
- User-provided template (
--template/docx_template_fileparameter) - Bundled default template (
md_exporter/assets/template/docx_template.docx) - Pandoc built-in default (fallback)
Step 4: Present outputs
Present both the .md (for editing/review) and the .docx (for sharing/printing).
Summarize: # attendees, # decisions, # action items, and any TBD items.
Output files
| Artifact | Pattern | Example |
| Markdown minute | YYYYMMDD_{MeetingPurpose}_Minutes.md | 20250709_Sprint_Retro_Minutes.md |
| Word document | YYYYMMDD_{MeetingPurpose}_Minutes.docx | 20250709_Sprint_Retro_Minutes.docx |
Both files are saved to the working directory (CWD).
Typical user prompts
| Language | Example |
| English | "Summarize this transcript into meeting minutes and export as Word" |
| Chinese | "把这份会议录音整理成会议纪要，并导出为 Word 文档" |
| Chinese | "整理会议记录并生成 docx 文件" |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.