meeting-assistant
Skill0 starsChanged 25 days agoMITView on GitHub
Turn meeting transcripts or raw notes into chronological minutes with confirmed decisions, pending items, disagreements, and an owner/deadline action table.
In this repository60 other files it gives its agents.
- 21st-aiSkill
- 21st-cli-useSkill
- 21st-design-syncSkill
- 21st-registrySkill
- 21st-ui-buildSkill
- 21st-ui-exploreSkill
- 21st-ui-reviewSkill
- ab-testingSkill
- ad-creativeSkill
- adsSkill
- ainoteSkill
- ai-seoSkill
- analyticsSkill
- asoSkill
- attributionSkill
- cavemanSkill
- churn-preventionSkill
- cold-emailSkill
- co-marketingSkill
- community-marketingSkill
- competitor-profilingSkill
- competitorsSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- croSkill
- customer-researchSkill
- directory-submissionsSkill
- emailsSkill
- eventsSkill
- free-toolsSkill
- imageSkill
- influencer-marketingSkill
- launchSkill
- lead-magnetsSkill
- marketing-councilSkill
- marketing-ideasSkill
- marketing-loopsSkill
- marketing-planSkill
- marketing-psychologySkill
- offersSkill
- onboardingSkill
- paywallsSkill
- pedrojaimot-file-organizerSkill
- popupsSkill
- pricingSkill
- product-marketingSkill
- programmatic-seoSkill
- prospectingSkill
- public-relationsSkill
- referralsSkill
- revopsSkill
- sales-enablementSkill
- schemaSkill
- seo-auditSkill
- signupSkill
- site-architectureSkill
- smsSkill
- socialSkill
- videoSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 17
Normalize input: - prefer timestamps and speaker labels.
- Distinctive: line 28
Never mix confirmed decisions with pending items.
- Very specific: line 29
Every action item has an Owner (use Unassigned if unknown) and a Deadline (use TBD if unknown).
- Distinctive: line 30
Use only content from the provided material.
- Distinctive: line 33
If inputs are missing or unreadable, say exactly what is missing and stop.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Source: https://github.com/aipoch/medical-research-skills (scientific-skills/Other/meeting-assistant), MIT, AIPOCH. Trimmed for general use.
Meeting Assistant
When to Use
- Meeting minutes from raw notes or transcripts, with a clear timeline of what was discussed.
- Action item tracking after recurring meetings (weekly syncs, standups, steering committees, client/partner calls) where owners and deadlines must be captured.
- Cross-team project sync: consolidate decisions, disagreements, and follow-ups into one output.
- Decision logging where confirmed decisions must be separated from items still pending confirmation.
- Post-meeting follow-up prep: concise next steps and unresolved questions.
Workflow
- Normalize input - prefer timestamps and speaker labels; if missing, infer order from paragraphs and explicit time cues.
- Timeline - sort entries by timestamp (or inferred order); write a concise chronological summary that keeps key context.
- Extract
- Decisions: statements of approval, confirmation, or commitment.
- Pending: proposals, open questions, "to be confirmed" items.
- Disagreements: explicit objections, conflicting views, unresolved trade-offs.
- Action items: task + owner + deadline (+ optional status).
- Structure output in this fixed order: Basic Info -> Timeline Summary -> Decisions (Confirmed) -> Items Pending Confirmation -> Disagreements / Open Issues -> Action Items table.
Output Rules
- Timeline follows meeting order.
- Never mix confirmed decisions with pending items.
- Every action item has an Owner (use
Unassignedif unknown) and a Deadline (useTBDif unknown). - Use only content from the provided material. No invented facts, owners, or dates.
- Preserve numbers, dates, and commitments exactly.
- Mask emails and phone numbers in the output unless the user asks to keep them.
- If inputs are missing or unreadable, say exactly what is missing and stop.
Output Template
# Meeting Minutes
## Basic Information
- Meeting Subject:
- Date:
- Participants:
- Recorder:
## Timeline Summary (Chronological)
1. [time] ...
## Decisions (Confirmed)
1. ...
## Items Pending Confirmation
1. ...
## Disagreements / Open Issues
- ...
## Action Items
| Task | Owner | Deadline | Status |
|------|-------|----------|--------|End with a one-line note of any assumptions made (e.g., inferred order, missing deadlines marked TBD).
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.

