agentleFS
Sign inStart free
Kuan-AI-comKuan-AI-com/agent-skills/skills/meeting-notes/SKILL.md

meeting-notes

Skill0 starsChanged 6 days agoMITView on GitHub

Turn a meeting transcript, recording summary or rough notes into structured notes. Use when the user pastes a transcript, says "summarize this meeting", "write the minutes", "recap", "what are the action items", or wants a follow-up email after a call.

57 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 8 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

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 2

    Distinctive

    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
  1. Distinctive:

    Decisions: only what was clearly agreed ("let's go with X", "agreed", no objection after a proposal by the person who owns it).

    line 17
  2. Distinctive:

    Write in the language of the transcript unless asked otherwise.

    line 37

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

Before writing

  • Find the meeting date (transcript header, file name, or ask). You need it to turn "next Friday" into a date. Without it, keep the relative phrase in quotes.
  • Identify speakers. If the transcript uses "Speaker 1/2" or labels are unreliable, keep those labels; never guess who said something.
  • Transcripts from speech recognition mangle names, product names and numbers. When something looks misheard, keep it and mark it [?].

Output (exactly these sections, in this order)

Summary: up to 3 sentences: purpose of the meeting and what came out of it.

Decisions: only what was clearly agreed ("let's go with X", "agreed", no objection after a proposal by the person who owns it). A suggestion nobody confirmed is not a decision: put it in Open questions as "Proposed: ...".

Action items

TaskOwnerDueSource
Send revised quote to ACMEMaria2026-11-14 (said "Friday")~12:40
  • Task starts with a verb and is specific enough to do without the transcript.
  • Owner: the person who committed ("I'll do it") or was explicitly assigned. Otherwise unassigned.
  • Due: only if said. Otherwise no date. Never invent one.
  • Source: timestamp or a short quote, so it can be checked.

Open questions: raised but not resolved, with who raised them.

Numbers and commitments (only if any): prices, dates, quantities, promises to customers, quoted exactly.

Rules

  • Nothing that is not in the source. No "next steps" you think would be wise; if you have a suggestion, put it after the notes under "Suggestion (not from the meeting)".
  • Long meetings with several topics: group Decisions and Action items by topic heading.
  • Write in the language of the transcript unless asked otherwise.
  • Drop small talk, but keep anything that changes a task, a date or a risk.

Follow-up email (only if asked)

Subject "Recap: <topic> (<date>)", 2 lines of context, then Decisions and Action items as above. No added commitments.

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