agentleFS
Sign inStart free
prestariusprestarius/jet-skills-stack/skills/meeting-notes/SKILL.md

meeting-notes

Skill1 starsChanged 2 months agoMITView on GitHub

Turn raw meeting notes or a transcript into structured minutes — decisions, action items with owners, open questions — and route them onward (Obsidian note, ADRs, tracker issues). Use whenever the user pastes a transcript or messy notes and says "write this up", "minutes", "notatka ze spotkania", "what did we decide", or wants meeting output captured rather than lost.

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use email-draft, weekly-review 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

  • 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

  • LangChainSkill

    competitor-analysis

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

    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, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 1

    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. Very specific:

    Read ./CONTEXT.md if present — use its glossary for terms and its tracker vocabulary for actions.

    line 5
  2. Distinctive:

    Never attribute opinions to named people unless the source does.

    line 18

“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

Read ./CONTEXT.md if present — use its glossary for terms and its tracker vocabulary for actions.

Produce minutes with these sections, in the language of the source material unless asked otherwise:

  1. Context — what meeting, when, attendees (only if stated in the source).
  2. Decisions — one line each: what was decided and why, as stated.
  3. Action items — owner — action — due ; if owner or due date is not in the source, write TODO: rather than inventing one.
  4. Open questions — unresolved points, each with who can answer it if known.
  5. Parking lot — raised but deferred topics.

Rules:

  • Extract, don't summarize away: if the source is Markdown, the output must be full and exhaustive (per the working agreement) — every decision and action in the source appears here.
  • Never attribute opinions to named people unless the source does.
  • Quote ambiguous statements verbatim instead of interpreting them.

Then offer routing (each opt-in, never automatic): the obsidian-note skill to file it in the vault, the domain-modeling skill for any durable architecture decision, the to-tickets skill for the action items.

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