agentleFS
Rome-1Rome-1/obsidian-claude-starter/.claude/skills/meeting-notes/SKILL.md

meeting-notes

Skill5 starsChanged 34 days agoMITView on GitHub

Turns rough meeting notes, a transcript, or a spoken recap into a structured meeting note in Meetings/, then updates the linked people and project notes and lists the action items. Also preps for an upcoming meeting by pulling the relevant people, project and past-meeting context. Use when the user pastes meeting notes or a transcript, says "write up this meeting", "log my call with X", "notes from today's sync", "prep me for my meeting with X", or runs /meeting-notes.

58 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 9 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

  • LangChainSkill

    web-research

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

    Also in 5 projects that use this

  • TheCraigHewittSkill

    research-brief

    Produces a one-page research brief on a topic, person, or company — what they do, what matters, what's changed recently, sources. Use when the user asks to research, look into, brief me on, or get context on a specific topic, company, competitor, or person. Pulls from the web, any project context, and recent emails involving the subject.

    Also in 3 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

    competitor-analysis

    Analyze competitors in a given market segment. Trigger on: competitive landscape, competitor analysis, market comparison, competitive positioning.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user says "prep", go to the prep section.

    line 10
  2. Distinctive:

    Ask only for what you cannot infer: the date (default today), and the project if it is unclear.

    line 17
  3. Very specific:

    Create Meetings/YYYY-MM-DD-Topic.md from System/Templates/Meeting.md.

    line 27
  4. Distinctive:

    Keep quotes only when the exact wording matters, and mark them as quotes.

    line 33
  5. Distinctive:

    Write a short brief in the chat, not a file, unless asked: who they are and what they care about, what was said or promised last time, open …

    line 50

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

Two modes: write-up (after a meeting) and prep (before one). If the user says "prep", go to the prep section.

Write-up

1. Gather

  • Take the raw notes or transcript the user gave you. If none, ask them to paste or dictate.
  • Ask only for what you cannot infer: the date (default today), and the project if it is unclear.

2. Resolve the people and the project

  • For each attendee, look for People/<First-Last>.md (Grep the name; names in notes are often first names only).
  • Link those that exist. For people without a note, write the plain name and ask whether to create notes for any of them. Do not create person notes unasked.
  • Find the project note the meeting belongs to, if any.

3. Write the note

Create Meetings/YYYY-MM-DD-Topic.md from System/Templates/Meeting.md.

  • Context: one or two sentences on why the meeting happened.
  • Key points: what was learned or discussed that matters later. Not a transcript.
  • Decisions: each one a line. Note who made it if that matters.
  • Action items: - [ ] Who: what, by when. If an owner or date was not stated, write "owner?" or "date?" rather than guessing.
  • Keep quotes only when the exact wording matters, and mark them as quotes.

4. Update linked notes

  • Each tracked attendee: a dated line under ## Interactions linking the meeting; update last_contact; update next_action if the meeting changed it.
  • The project: a line in its ## Log (or Current-State.md), and the user's own action items as - [ ] under ## Next actions.
  • Significant decisions: offer to record them with the decision-record skill.
  • Set updated: on every note you change.

5. Report

Show the action items, the notes you changed (as links), and any open questions (unknown owners, people without notes). Run python3 scripts/check_vault.py.

Prep

  1. Find the person notes, the project notes and the last two or three meetings with the same people or project.
  2. Write a short brief in the chat, not a file, unless asked: who they are and what they care about, what was said or promised last time, open action items on both sides, and two or three things worth raising.
  3. Offer to create the meeting note now with the context section filled in, so notes can go straight into it.

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.