agentleFS
Sign inStart free
kyluskylus/agentport/skills/meeting-notes/SKILL.md

meeting-notes

Skill0 starsChanged 3 months agoMITView on GitHub

Turn a meeting transcript or chat-thread-of-a-meeting into structured notes: background, key discussion points, decisions, todos, open questions, risks, understanding changes, and a short summary pastable back to the channel. Triggers: "整理會議", "meeting notes", "transcript", "/meeting".

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

1 rule. 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't invent attendees / times the source didn't state — say "未知".

    line 73

“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

Extract structured value from a meeting record: what was decided, what was merely proposed, and what changed in the team's understanding.

Input

One of:

  • A chat thread the owner references — pull it with the enabled channel's fetch tool (mcp__discord__fetch_messages, or mcp__slack__fetch_messages when the external Slack adapter is wired in)
  • Raw transcript text the user pastes
  • A Google Doc URL of notes (use ingest-source first to pull into sources/)

Output template

Render in this exact shape — plain text pastable back into the chat channel, no markdown bold:

會議紀錄：<one-line topic of meeting>
時間：<YYYY-MM-DD HH:MM if known>
參與：<@U1>, <@U2>, ...
來源：<thread permalink / doc URL>

背景：
- <為什麼開這個會 + 之前到哪一步>

討論重點：
- <bullet 1>
- <bullet 2>

決策：
- <YYYY-MM-DD: decision> · 決策者：<@who>
- (or: 沒有任何決策)

待辦：
- <todo> · owner：<@who> · 預計：<when>
- (or: 沒有待辦)

未解問題：
- <question>
- (or: 沒有)

風險：
- <risk + likelihood + impact>
- (or: 沒有新風險)

理解變更：
- 原本：<old belief>
- 現在：<new belief>
- 變更原因：<what new info caused this>
- 來源：<link>
- (or: 沒有理解變更)

是否寫入長期記憶：是 / 否
- 是的話：建議寫進 <section>，內容預擬如下 ...
- 否的話：原因（如：屬於單次事件、未確認、無關 topic）

Behaviour rules

  1. Don't invent attendees / times the source didn't state — say "未知".
  2. "理解變更" 段最關鍵：仔細比對會議內容 vs memory/current_understanding.md 與 memory/decisions.md，如果新內容推翻舊的，明確列出來。如果只是補充細節，標 "細化" 不是 "推翻"。
  3. 「是否寫入長期記憶」由 agent 預判，但「不主動寫」— 由 owner 接手決定後走 propose / approve flow。
  4. 結尾追加一段「短摘要」(3 行內，可以貼回原 thread / 頻道給其他人看)。

When NOT to invoke

  • 只是 ad-hoc 聊天，非正式會議 → 不用走這 skill
  • 內容跟 topic 完全無關 → 走 hard refusal

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