meetings
Skill0 starsChanged 8 months agoMITView on GitHub
Review synced meeting notes. Finds unprocessed notes, suggests routing, and reports sync status.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- magnus919/agent-skillstheir own version, first seen Nov 1, 2026
- butterbase-ai/butterbase-plugintheir own version, first seen Oct 8, 2026
- treylom/ThisCodetheir own version, first seen Sep 5, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
- butterbase-ai/butterbase-skillstheir own version, first seen Jun 10, 2026
- manager-dot-dev/manager-skillstheir own version, first seen Apr 11, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- butterbase-ai/butterbase-plugin★ 535same name
- butterbase-ai/butterbase-skills★ 535same name
- magnus919/agent-skills★ 172same name
- manager-dot-dev/manager-skills★ 114same name
- treylom/ThisCode★ 41same name
- Hassaan146/claude-skills★ 18same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- applySkill
- daySkill
- exploreSkill
- goalsSkill
- idea-validatorSkill
- linkedin-post-writerSkill
- outreachSkill
- product-designerSkill
- projectsSkill
- prompt-engineerSkill
- status-update-writerSkill
- tasksSkill
- triageSkill
- weekSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 11 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read the last 10 lines of 99_System/scripts/sync_granola.log and report:
- Distinctive: line 15
When the last sync ran
- Distinctive: line 28
Read the note content and suggest:
- Very specific: line 39
Update Domain in frontmatter
- Very specific: line 40
Remove processed: false if present
- Very specific: line 41
Add or update Related: line after frontmatter
- Distinctive: line 42
If subfolder was approved and differs from current location, move the file
- Distinctive: line 43
Add entity wikilinks in the content body where appropriate
- Distinctive: line 47
After processing all notes, show:
- Very specific: line 54
Use these rules when suggesting Domain and subfolder (loaded from 99_System/scripts/granola_routing.json):
- Distinctive: line 68
When processing note content, convert recognized mentions to wikilinks:
- Distinctive: line 74
Only link first occurrence in each section.
- Distinctive: line 78
Start with sync status, then list unprocessed notes
- Distinctive: line 79
If no unprocessed notes, just report status and exit
- Distinctive: line 81
If user says "approve all", batch-apply all suggestions
- Distinctive: line 82
If user says "skip", move to next note
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/meetings - Meeting Notes Review
You are helping the user review and process meeting notes synced from Granola.
Behavior
1. Report sync status
Read the last 10 lines of 99_System/scripts/sync_granola.log and report:
- When the last sync ran
- How many notes were created in the last run
2. Find unprocessed notes
Scan 99_System/Meeting Notes/ (including subdirectories) for notes that have granola_id in frontmatter AND either:
processed: falsein frontmatter, OR- Missing
Domainfield in frontmatter
List them with title, date, and current location.
3. For each unprocessed note
Read the note content and suggest:
- Domain: Which Domain MOC to link (e.g.,
[[D - Career & Job Search]]) - Related links: Relevant wikilinks based on content (people, projects, etc.)
- Subfolder: Where it should live under
99_System/Meeting Notes/ - Entity links: Convert plain text mentions to wikilinks in the content body
Present suggestions to the user and ask to approve / edit / skip each one.
4. Apply approved changes
For each approved note:
- Update
Domainin frontmatter - Remove
processed: falseif present - Add or update
Related:line after frontmatter - If subfolder was approved and differs from current location, move the file
- Add entity wikilinks in the content body where appropriate
5. Summary
After processing all notes, show:
- How many notes were processed
- How many were skipped
- Any that need manual attention
Routing Reference
Use these rules when suggesting Domain and subfolder (loaded from 99_System/scripts/granola_routing.json):
| Keywords / People | Domain | Subfolder |
| Mark R., JaredMark | [[D - Career & Job Search]] | Mark_R. |
| Nate B. Jones, NateBJ | [[D - Tech & AI]] | NateBJones |
| Legata, Alesia, Bryan, Tim | [[D - Career & Job Search]] | Legata |
| Theron, Mitch, branding, website, HPM | [[D - Property Management]] | HPM |
| Omaya, admissions | [[D - Family]] | (root) |
| SaaS, playbook | [[D - Side Hustles]] | (root) |
| Equip, outreach | [[D - Career & Job Search]] | Outreach_Calls |
Entity Linking
When processing note content, convert recognized mentions to wikilinks:
- "Legata" / "Alesia" / "Bryan" →
[[Legata Index|Legata]]etc. - "Nate" / "Nate B" →
[[People Index|Nate]] - "Theron" / "Mitch" →
[[People Index|Theron]]etc. - "Mark R" / "Mark Reveley" →
[[People Index|Mark R.]]
Only link first occurrence in each section. Don't link inside transcript sections.
Conversation Style
- Start with sync status, then list unprocessed notes
- If no unprocessed notes, just report status and exit
- Be concise - show suggestions as a table or short list
- If user says "approve all", batch-apply all suggestions
- If user says "skip", move to next note
Example
Claude: Last sync: 2 min ago (3 notes created).
Found 2 unprocessed notes:
1. **Prop Tech** (2025-12-09) - currently in Meeting Notes root
Suggest: Domain [[D - Tech & AI]], subfolder: none, Related: [[Meeting Index]] | [[People Index]]
2. **continuing product management conversation** (2026-01-29) - currently in Legata/
Suggest: Domain [[D - Career & Job Search]], Related: add [[Legata Index]]
Approve all, or review individually?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.