Railly/agent-brain / .agents/skills/meeting
meeting
VerifiedProcess meeting notes into structured notes + action items
Process meeting notes: $ARGUMENTS
IMPORTANT: Be direct
- Don't check if folders exist
- Don't search existing notes
- Just create and append
Step 0: Transcribe (if audio/video input)
If the user provides an audio or video file (.mp3, .mp4, .wav, .m4a, .webm, .ogg) or a URL (YouTube, Google Meet recording, etc.), transcribe it first using trx:
trx "$ARGUMENTS" --output json --fields text
This outputs the full transcript as text. Use that as the meeting content for the steps below.
If the user provides text directly, skip this step.
Flow
-
Create meeting note in
03_Garden/meetings/{YYYY-MM-DD}/{slug}.md:--- type: meeting created: {{date}} attendees: - "[[Person 1]]" - "[[Person 2]]" project: --- # {Meeting Title} ## Key Decisions - ## Insights - ## Action Items - [ ] @{person}: {task} ## Notes {summary of discussion} -
Create corrected transcript in
03_Garden/meetings/{YYYY-MM-DD}/{slug}-transcript.md:- Fix common transcription errors (tool names, product names, technical terms)
- Format as dialogue:
**{Person 1}:** .../**{Person 2}:** ... - Keep the natural spoken language as-is
- Add
[Pause],[Screen share],[Laughter]annotations where evident - Frontmatter:
--- type: transcript created: {{date}} meeting: "[[{slug}]]" language: {detected language} coverage: {full (~Xmin) | partial (~Xmin of Ymin)} --- # Transcript: {Title} - {duration} -
Create summary in
03_Garden/meetings/{YYYY-MM-DD}/{slug}-summary.md:- Written in first person reflecting on the conversation
- Structured sections: Context, Key Topics, Learnings, Takeaways
- Frontmatter:
--- type: summary created: {{date}} meeting: "[[{slug}]]" --- -
Create person notes for attendees not yet in
03_Garden/people/ -
Extract YOUR action items -> append to
02_Journal/daily/{{date}}.md:## Action Items (from {meeting}) - [ ] {task 1} - [ ] {task 2}
Example
User pastes meeting notes or provides a recording, run /meeting:
Created: 03_Garden/meetings/2026-01-04/team-sync.md
Created: 03_Garden/meetings/2026-01-04/team-sync-transcript.md
Created: 03_Garden/meetings/2026-01-04/team-sync-summary.md
Attendees: [[Alice]], [[Bob]]
Action items added to daily log:
- [ ] Review API proposal
- [ ] Send follow-up email
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |