AGI-comming/functional-skill-creator / examples/meeting-notes-to-actions
meeting-notes-to-actions
VerifiedConvert meeting notes into owners, action items, decisions, and follow-up messages.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
| functions/draft_follow_up.md | markdown | 793 B |
| functions/extract_action_items.md | markdown | 942 B |
| functions/load_meeting_notes.md | markdown | 1.2 KB |
| logs/runs/.gitkeep | other | 1 B |
| references/shared-glossary.md | markdown | 530 B |
| scripts/.gitkeep | other | 1 B |
| scripts/normalize_meeting_notes.mjs | script | 620 B |
| scripts/normalize_meeting_notes.test.mjs | script | 704 B |
| testcases/unit/extract_action_items.basic.case.json | config | 1.1 KB |
SKILL.md
View on GitHub---
name: meeting-notes-to-actions
description: Convert meeting notes into owners, action items, decisions, and follow-up messages.
---
# meeting-notes-to-actions
## Goal
Convert raw meeting notes into a structured follow-up plan. This example demonstrates a functional skill that is not tied to any specific agent runtime or business domain.
## Principles
- Orchestration stays in `SKILL.md`.
- Function behavior lives in `functions/*.md`.
- Do not fabricate owners, due dates, or decisions that are missing from the meeting notes.
- Only use trace logs when the caller enables reporting.
- Deterministic input normalization belongs in `scripts/`, not in prompt judgment.
## References
| Resource | Load Timing | Purpose |
|---|---|---|
| `shared_glossary` | On demand | Shared terminology for this example. |
## External Inputs
| Field | Source | Description |
|---|---|---|
| `meeting_notes` | user | Raw meeting notes text. |
| `default_due_date` | user | Optional fallback due date label. |
| `report_mode` | user | `off`, `local`, or `remote`; defaults to `off`. |
## Execution Pipeline
| Step | Function | Purpose | Input | Output |
|---:|---|---|---|---|
| 1 | `load_meeting_notes` | Normalize raw notes and source metadata. | `meeting_notes` | `notes_context` |
| 2 | `extract_action_items` | Extract owners, actions, decisions, and open questions. | `notes_context`<br>`default_due_date` | `action_items`<br>`decisions`<br>`open_questions` |
| 3 | `draft_follow_up` | Draft a concise follow-up message. | `action_items`<br>`decisions`<br>`open_questions` | `follow_up_message` |
## Output Scope
This example returns structured data and does not write project files.
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: 119k | 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 |