meeting

Name: meeting
Author: aleksander-dytko

31stars4forks

How to install meeting?

aleksander-dytko/ai-pm-workspace/meeting

$npx -y skills add aleksander-dytko/ai-pm-workspace --skill meeting

Installs into the current project.

Summary

Process raw meeting notes into structured meeting note with in-repo tasks

Files · 1

View on GitHub

SKILL.md

1	# Process Meeting Notes
2
3	You are helping process raw meeting notes into a structured meeting note. Action items for the user land in `Dashboard/tasks.md`.
4
5	## Input Modes
6
7	The skill operates in one of three modes based on `$ARGUMENTS`:
8
9	\| Mode \| Arguments \| When to use \|
10	\|------\|-----------\|-------------\|
11	\| Browse \| (none) or `browse` \| List recent files in `Meetings/` that look unprocessed \|
12	\| Specific file \| File path or partial name \| Process notes from a specific file \|
13	\| Paste \| Pasted text (long string) \| Meeting notes pasted directly into the prompt \|
14
15	---
16
17	## Workflow
18
19	### Step 0: Determine mode and get raw notes
20
21	If no arguments (Browse mode):
22	1. Use the `Glob` tool with pattern `Meetings/*.md` to list meeting files. Do NOT use `Bash ls` - Glob is quieter and shows results already sorted.
23	2. Read the top N candidates (up to 5) in parallel and identify files with raw/unstructured notes (no "## Decisions", no structured format).
24	3. Show a numbered list of unprocessed files.
25	4. Ask: "Which meeting do you want to process?"
26
27	If specific file path:
28	1. Read the file.
29	2. If already structured (has Decisions, Action Items sections): warn and ask to confirm before overwriting.
30	3. If raw notes: proceed directly.
31
32	If pasted text:
33	- Use the pasted text as raw input.
34	- Ask for meeting date and title if not obvious from the text.
35
36	---
37
38	### Step 1: Analyze raw notes
39
40	Extract:
41	- Meeting title (from filename or content)
42	- Date (from filename or content)
43	- Attendees (mentioned names)
44	- Key topics discussed
45	- Decisions made (explicit or implicit)
46	- Action items (tasks, follow-ups, commitments - with owners)
47	- Open questions (unresolved topics)
48
49	### Step 2: Cross-reference attendees
50
51	- Read `Dashboard/people-profiles.md` to verify attendee names and roles.
52	- Use tags (e.g., `#FirstName`) when mentioning people.
53
54	### Step 3: Search for related context
55
56	- Search `Loose Notes/Work/` for related decisions or notes.
57	- Check `Dashboard/Weekly P-Tasks.md` for related P-tasks.
58	- Identify which existing notes this meeting relates to - used in the "Related" section.
59
60	### Step 4: Create structured meeting note
61
62	- Location: `Meetings/YYYY-MM-DD - [Meeting Title].md` (or overwrite the source file if processing in-place).
63	- Template: `templates/meeting-note.md`.
64	- Date: the meeting's actual date, not today's date.
65	- Fill all sections:
66	- Attendees (verified names, correct tags)
67	- Topics (high-level)
68	- Meeting notes (organized by topic)
69	- Decisions (extracted explicitly)
70	- Action Items (checkboxes with owners and deadlines)
71	- Open Questions
72	- Related (wikilinks to relevant notes)
73
74	### Step 5: Link in the meeting's journal
75
76	- Journal path: `journals/YYYY/MM-Month/DD-MM-YYYY.md` for the meeting's date.
77	- Add under `## Notes`: `- [[YYYY-MM-DD - Meeting Title]] - [One-line summary]`.
78	- If the journal for that date doesn't exist, skip.
79
80	### Step 6: Prepare tasks for the user (confirm before writing)
81
82	- Only prepare tasks for the vault owner - skip tasks owned by others.
83	- Avoid duplicates: scan `Dashboard/tasks.md` (all three sections) for matching task content.
84	- Prepare a proposed list:
85	- Text: "[Action item]"
86	- Optional due date (if a deadline was mentioned)
87	- Optional priority (P2 critical / P3 normal / P4 low)
88	- Source link back to the meeting note (`source: [[YYYY-MM-DD - Meeting Title]]`)
89
90	Show the proposed list and wait for confirmation before writing.
91
92	After confirmation, append the tasks to `Dashboard/tasks.md` under the "This week" section, using this format:
93
94	```
95	- [ ] Action description - source: [[YYYY-MM-DD - Meeting Title]] - due: YYYY-MM-DD - priority: P3
96	```
97
98	Priority and due date are optional - include only when meaningful.
99
100	---
101
102	## Output Format
103
104	When reporting results to the user in chat, reference files with backtick-wrapped paths, not markdown links with spaces and not `[[wikilinks]]`. Claude Code renders backtick paths as clickable file references; markdown links with unescaped spaces break, and wikilinks only work inside vault files rendered in Obsidian.
105
106	In chat:
107
108	```
109	Meeting note created: `Meetings/YYYY-MM-DD - Meeting Title.md`
110	Linked in journal: `journals/YYYY/MM-Month/DD-MM-YYYY.md` (or "skipped - no journal for that date")
111
112	Proposed tasks for Dashboard/tasks.md (your action items only):
113	1. [Task] - due YYYY-MM-DD - P2
114	2. [Task] - P3
115
116	Already in Dashboard/tasks.md (skipping):
117	- [Existing task]
118
119	Tasks for others (not added to your list):
120	- [Task] - [Person]
121
122	Confirm: add tasks to Dashboard/tasks.md? (Y / N / pick numbers like 1,3)
123	```
124
125	After confirmation, append tasks to the "This week" section of `Dashboard/tasks.md`.
126
127	Inside the meeting note file itself (the Markdown being written to disk), keep using `[[wikilink]]` style for the Related section and task `source:` fields - those a

People who liked this also viewed

6 picks

Type

meeting

31stars4forks

View on GitHub

How to install meeting?

aleksander-dytko/ai-pm-workspace/meeting

$npx -y skills add aleksander-dytko/ai-pm-workspace --skill meeting

Installs into the current project.

Summary

Process raw meeting notes into structured meeting note with in-repo tasks

Files · 1

View on GitHub

SKILL.md

1	# Process Meeting Notes
2
3	You are helping process raw meeting notes into a structured meeting note. Action items for the user land in `Dashboard/tasks.md`.
4
5	## Input Modes
6
7	The skill operates in one of three modes based on `$ARGUMENTS`:
8
9	\| Mode \| Arguments \| When to use \|
10	\|------\|-----------\|-------------\|
11	\| Browse \| (none) or `browse` \| List recent files in `Meetings/` that look unprocessed \|
12	\| Specific file \| File path or partial name \| Process notes from a specific file \|
13	\| Paste \| Pasted text (long string) \| Meeting notes pasted directly into the prompt \|
14
15	---
16
17	## Workflow
18
19	### Step 0: Determine mode and get raw notes
20
21	If no arguments (Browse mode):
22	1. Use the `Glob` tool with pattern `Meetings/*.md` to list meeting files. Do NOT use `Bash ls` - Glob is quieter and shows results already sorted.
23	2. Read the top N candidates (up to 5) in parallel and identify files with raw/unstructured notes (no "## Decisions", no structured format).
24	3. Show a numbered list of unprocessed files.
25	4. Ask: "Which meeting do you want to process?"
26
27	If specific file path:
28	1. Read the file.
29	2. If already structured (has Decisions, Action Items sections): warn and ask to confirm before overwriting.
30	3. If raw notes: proceed directly.
31
32	If pasted text:
33	- Use the pasted text as raw input.
34	- Ask for meeting date and title if not obvious from the text.
35
36	---
37
38	### Step 1: Analyze raw notes
39
40	Extract:
41	- Meeting title (from filename or content)
42	- Date (from filename or content)
43	- Attendees (mentioned names)
44	- Key topics discussed
45	- Decisions made (explicit or implicit)
46	- Action items (tasks, follow-ups, commitments - with owners)
47	- Open questions (unresolved topics)
48
49	### Step 2: Cross-reference attendees
50
51	- Read `Dashboard/people-profiles.md` to verify attendee names and roles.
52	- Use tags (e.g., `#FirstName`) when mentioning people.
53
54	### Step 3: Search for related context
55
56	- Search `Loose Notes/Work/` for related decisions or notes.
57	- Check `Dashboard/Weekly P-Tasks.md` for related P-tasks.
58	- Identify which existing notes this meeting relates to - used in the "Related" section.
59
60	### Step 4: Create structured meeting note
61
62	- Location: `Meetings/YYYY-MM-DD - [Meeting Title].md` (or overwrite the source file if processing in-place).
63	- Template: `templates/meeting-note.md`.
64	- Date: the meeting's actual date, not today's date.
65	- Fill all sections:
66	- Attendees (verified names, correct tags)
67	- Topics (high-level)
68	- Meeting notes (organized by topic)
69	- Decisions (extracted explicitly)
70	- Action Items (checkboxes with owners and deadlines)
71	- Open Questions
72	- Related (wikilinks to relevant notes)
73
74	### Step 5: Link in the meeting's journal
75
76	- Journal path: `journals/YYYY/MM-Month/DD-MM-YYYY.md` for the meeting's date.
77	- Add under `## Notes`: `- [[YYYY-MM-DD - Meeting Title]] - [One-line summary]`.
78	- If the journal for that date doesn't exist, skip.
79
80	### Step 6: Prepare tasks for the user (confirm before writing)
81
82	- Only prepare tasks for the vault owner - skip tasks owned by others.
83	- Avoid duplicates: scan `Dashboard/tasks.md` (all three sections) for matching task content.
84	- Prepare a proposed list:
85	- Text: "[Action item]"
86	- Optional due date (if a deadline was mentioned)
87	- Optional priority (P2 critical / P3 normal / P4 low)
88	- Source link back to the meeting note (`source: [[YYYY-MM-DD - Meeting Title]]`)
89
90	Show the proposed list and wait for confirmation before writing.
91
92	After confirmation, append the tasks to `Dashboard/tasks.md` under the "This week" section, using this format:
93
94	```
95	- [ ] Action description - source: [[YYYY-MM-DD - Meeting Title]] - due: YYYY-MM-DD - priority: P3
96	```
97
98	Priority and due date are optional - include only when meaningful.
99
100	---
101
102	## Output Format
103
104	When reporting results to the user in chat, reference files with backtick-wrapped paths, not markdown links with spaces and not `[[wikilinks]]`. Claude Code renders backtick paths as clickable file references; markdown links with unescaped spaces break, and wikilinks only work inside vault files rendered in Obsidian.
105
106	In chat:
107
108	```
109	Meeting note created: `Meetings/YYYY-MM-DD - Meeting Title.md`
110	Linked in journal: `journals/YYYY/MM-Month/DD-MM-YYYY.md` (or "skipped - no journal for that date")
111
112	Proposed tasks for Dashboard/tasks.md (your action items only):
113	1. [Task] - due YYYY-MM-DD - P2
114	2. [Task] - P3
115
116	Already in Dashboard/tasks.md (skipping):
117	- [Existing task]
118
119	Tasks for others (not added to your list):
120	- [Task] - [Person]
121
122	Confirm: add tasks to Dashboard/tasks.md? (Y / N / pick numbers like 1,3)
123	```
124
125	After confirmation, append tasks to the "This week" section of `Dashboard/tasks.md`.
126
127	Inside the meeting note file itself (the Markdown being written to disk), keep using `[[wikilink]]` style for the Related section and task `source:` fields - those a

People who liked this also viewed

6 picks

Type