meetings-and-clubs
Skill2 starsChanged 2 months agoMITView on GitHub
Use when processing meetings or org/club context.
In this repository16 other files it gives its agents.
- canvas-course-syncSkill
- categorizerSkill
- course-knowledge-baseSkill
- course-study-sessionSkill
- email-draftingSkill
- exam-prepSkill
- grade-calculatorSkill
- homework-checklistSkill
- note-formatting-rulesSkill
- photos-to-pdfSkill
- roadmapSkill
- school-advisorSkill
- study-notes-workflowSkill
- suite-updateSkill
- verification-before-completionSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Keep any group/organization specifics out of the public suite — this section is a template for whoever installs it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Config: resolve
<PLACEHOLDER>tokens from~/.hermes/school-config.md(seecanvas-course-sync→ School config). Never edit SKILL.md with real values.
Meetings & Clubs
Wispr Flow MCP (meeting transcripts) — search/pull meetings & notes
- Wispr Flow (meeting notetaker) is optional: if configured, Wispr MCP tools appear as
mcp_wispr_*(search_meetings, get_meeting, search_calendar_events, list_upcoming_meetings, etc.). Configure on a fresh machine via Hermes MCP setup when the user uses Wispr. - Wispr Flow (meeting notetaker) is optional: if configured, Wispr MCP tools appear as
mcp_wispr_*(search_meetings, get_meeting, search_calendar_events, list_upcoming_meetings, etc.). Configure on a fresh machine via Hermes MCP setup when the user uses Wispr.
Meeting workflow: search_meetings → get_meeting (summary for action items, transcript for verbatim detail) → save important meetings to Classes/<Org>/README.md (e.g. an org folder) with dates/decisions/action items → add calendar-worthy events to the Roadmap balanced calendar → update Roadmap. Wispr timestamps are UTC — convert to user's local time before presenting.
Organization / club context (template)
- <USER_NAME> helps run an <ORG_NAME> (advisor <ORG_ADVISOR>, lead <ORG_LEAD>). He staffs the <ORG_NAME> fair table and does a live demo at the first general meeting. Meeting notes archived in
Classes/<Org>/README.md. Wispr Flow MCP can be connected for meeting transcripts (see the Wispr section above; fresh machines configure it via Hermes MCP setup). - Keep any group/organization specifics out of the public suite — this section is a template for whoever installs it.
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.

