diff --git a/_skill-index.md b/_skill-index.md
index e4be09d..1599e92 100644
--- a/_skill-index.md
+++ b/_skill-index.md
@@ -25,6 +25,7 @@ description: Master index of all skills in your robot assistant system. Your ass
 | "write a POV doc," "create a proof of value document," "POV criteria," "proof of concept criteria," "generate a POC document" | **pov-doc** |
 | "submit an expense," "navan expense," "file an expense," "upload receipt" | **navan-expense** |
 | "update the SE radar report," "add a column to the SE report," "edit the vNotes report," "run the SE radar report," "check SE validation stage," "update technical validation" | **update-salesforce-tech-validation** |
+| "create a meeting note," "make meeting notes," "add a meeting to my daily note," "set up a meeting note" | **meeting-notes** |
 
 ---
 
@@ -108,6 +109,12 @@ description: Master index of all skills in your robot assistant system. Your ass
 **File:** `skills/update-salesforce-tech-validation/SKILL.md`
 **Dependencies:** Chrome browser with active Salesforce session (Okta SSO)
 
+### Meeting Notes
+**Purpose:** Create and update meeting notes in `mt/` with the `YYMMDD-account-description.md` naming convention, and link them in the corresponding daily note under the meetings section.
+**Triggers:** "create a meeting note," "make meeting notes," "add a meeting to my daily note," "set up a meeting note"
+**File:** `skills/meeting-notes/SKILL.md`
+**Dependencies:** None
+
 ---
 
 ## Adding New Skills
diff --git a/meeting-notes/SKILL.md b/meeting-notes/SKILL.md
new file mode 100644
index 0000000..58f7583
--- /dev/null
+++ b/meeting-notes/SKILL.md
@@ -0,0 +1,77 @@
+---
+name: meeting-notes
+description: This skill should be used when the user asks to "create a meeting note," "make meeting notes," "set up a meeting note," "add a meeting to my daily note," or any request to create or update notes for an upcoming or past meeting.
+version: 1.0.0
+---
+
+# Meeting Notes
+
+Create and update meeting notes in the user's notes system. Meeting notes are individual markdown files linked from daily notes.
+
+## File Locations
+
+- **Meeting notes:** `~/notes/mt/`
+- **Daily notes:** `~/notes/dn_YYMMDD.md`
+
+## Naming Convention
+
+Meeting note files use the format:
+
+```
+mt/YYMMDD-account-description.md
+```
+
+- `YYMMDD`: date of the meeting (two-digit year, zero-padded month and day)
+- `account-description`: the account name or general topic, lowercase, hyphen-delimited
+- Example: `260414-tdcj-demo.md`, `260209-berlick-1on1.md`
+
+If the user mentions a specific account that has an existing note in `~/notes/`, check if the account note has a wikilink to the meeting note under a meeting section. If so, also add a reverse link from the meeting note back to the account note.
+
+## Daily Note Link
+
+After creating the meeting note, link it in the corresponding daily note (`~/notes/dn_YYMMDD.md`) under the `## meetings` section:
+
+```markdown
+## meetings
+- [[mt/YYMMDD-account-description|Display Name]]
+```
+
+Use the meeting note's heading (usually `# Meeting Title`) as the display name. If the daily note does not exist yet, create it following the daily note template (see existing `dn_*.md` files for the format).
+
+## Meeting Note Template
+
+Use this structure when creating a new meeting note. Only include sections that have content.
+
+```markdown
+# Meeting Title
+
+**Date:** YYYY-MM-DD
+**Attendees:** (comma-separated list of people)
+
+## Agenda / Demo Flow / Topics
+- (list of topics, agenda items, or demo flow steps)
+
+## Notes
+- (key points, decisions, takeaways)
+
+## Next Steps
+- [ ] (action items with owners if known)
+```
+
+Sections should be tailored to the meeting type:
+- **Demos:** use "Demo Flow" instead of "Agenda"
+- **1:1s:** use a simpler structure with key discussion points
+- **Planning calls:** include "Planning Notes" and "Next Steps"
+- **General meetings:** use "Agenda" and "Notes"
+
+## Updating Existing Meeting Notes
+
+If the user asks to update a meeting note that already exists:
+1. Find it in `~/notes/mt/` by date and/or account name
+2. Read the existing content
+3. Append new information or edit existing sections as requested
+4. Do not remove existing content unless explicitly asked
+
+## Finding Meeting Notes
+
+When the user references a meeting by account name or topic, search `~/notes/mt/` for matching files. You can also search account notes (e.g., `~/notes/NISD Northside ISD.md`) for wikilinks to meeting notes in the format `[[mt/...]]`.