agentleFS
Sign inStart free
Works-HQWorks-HQ/ai-brain-starter-pack/skills/meeting-notes/SKILL.md

meeting-notes

Skill3 starsChanged 3 months agoMITView on GitHub

Turn rough notes into a clean meeting record and prepare its action items for debrief. Use right after a meeting. Triggers on "meeting notes", "clean up these notes", "structure this meeting", and "make a meeting note".

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use email-draft, status-report and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yakatotechSkill

    email-draft

    Create business email drafts. Use when asked to draft emails

    Also in 3 projects that use this

  • AnthropicSkill

    status-report

    Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.

    Also in 3 projects that use this

  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 8 projects that use this

  • vijpatel7Skill

    cold-outreach

    Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.

    Also in 3 projects that use this

  • LangChainSkill

    web-research

    Use this skill for requests related to web research; it provides a structured approach to conducting comprehensive web research

    Also in 4 projects that use this

  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Company mode: use this when operating-system/ exists with operating-system/GLOBAL_TASKS.md.

    line 16
  2. Very specific:

    Personal mode: use this when root-level TASKS.md exists with a personal root or area CLAUDE.md.

    line 17
  3. Distinctive:

    Both detected: ask which mode to use. Write nothing until the user chooses.

    line 18
  4. Distinctive:

    Do not create a structure just to make the skill run.

    line 21
  5. Distinctive:

    Read the raw notes fully. If the meeting's date, title, or area is unclear, ask.

    line 25
  6. Distinctive:

    Do not invent a decision or task.

    line 35
  7. Very specific:

    Personal mode: create meetings/YYYY-MM-DD-title.md.

    line 39
  8. Very specific:

    Company mode: create operating-system/meetings/YYYY-MM-DD-title.md using the shape in operating-system/templates/MEETING_NOTE.md.

    line 40
  9. Distinctive:

    Use a short lowercase filename with hyphens for the title.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 43 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting Notes

Turn rough notes into one clean, findable record without losing signal. This skill creates the record. Debrief files the decisions, tasks, and waiting-for items afterward.

Done when: the cleaned note is filed at its approved destination, and the extracted action items are listed for debrief.

Detect the structure first

Inspect the current folder before planning any write.

  1. Company mode: use this when operating-system/ exists with operating-system/GLOBAL_TASKS.md.
  2. Personal mode: use this when root-level TASKS.md exists with a personal root or area CLAUDE.md.
  3. Both detected: ask which mode to use. Write nothing until the user chooses.
  4. Neither detected: say that this folder does not contain a recognised personal or company structure. Point the user to START-HERE. Write nothing.

Do not create a structure just to make the skill run.

Build the record

Read the raw notes fully. If the meeting's date, title, or area is unclear, ask. Preserve the raw notes and then structure:

  • date, area, attendees, and meeting type
  • a two or three line summary of what happened
  • decisions made
  • the user's tasks
  • things waiting on other people
  • follow-up drafts
  • durable facts worth reviewing for the brain

Do not invent a decision or task. If something was discussed but not decided, label it as discussed. Flag legal, financial, HR, and other sensitive content before proposing a write. Draft follow-ups, never send them.

Route the note

  • Personal mode: create meetings/YYYY-MM-DD-title.md.
  • Company mode: create operating-system/meetings/YYYY-MM-DD-title.md using the shape in operating-system/templates/MEETING_NOTE.md.

Use a short lowercase filename with hyphens for the title. Never overwrite an existing note. If the target exists, propose a distinct filename or ask the user.

Approval gate

Show the complete cleaned note and its exact destination before writing. Wait for approval. Write only the approved note. Then list the extracted action items and offer to run debrief. Do not run debrief or change any other file without a separate request and approval.

Scaling to per-project folders

Company mode deliberately uses one top-level operating-system/meetings/ folder. If the meeting volume later becomes hard to scan, split notes into project folders and update this routing rule after the shared workflow has proved useful.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free