agentleFS
Memories-ai-labsMemories-ai-labs/Luci-skills/skills/official/summarize-meeting/SKILL.md

summarize-meeting

Skill8 starsChanged 4 months agoMITView on GitHub

Write a meeting into ~/.Life/reflections/meetings/. Use when the user says summarize this meeting, or pastes Luci's meeting-end prompt.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    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:

    Read ~/.Life/RULES.md first if it exists — the user's hand-written rules for these notes (who is who, who and what to leave out).

    line 14
  2. Distinctive:

    Use the luci skill to pull screen activity and transcripts from that window, then write one markdown file on disk — do not stop at a chat …

    line 18
  3. Distinctive:

    Use [] for an empty list. Body after the frontmatter is free markdown (who was there, what was discussed, decisions, action items, open …

    line 46
  4. Very specific:

    Create ~/.Life and the meetings / entities folders if they are missing.

    line 57
  5. Very specific:

    Read ~/.Life/entities/ first.

    line 59
  6. Distinctive:

    Do not create a person file for the user (Zoom labels like (你), (You), Me) or for recording bots (Fathom, Otter, Fireflies, Notetaker).

    line 80
  7. Very specific:

    Do not edit reflections/daily/.

    line 82

“Common” is measured: kept by at least 6 in 10 of the 9 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
<!-- luci-skill-version: 1.0.0 -->

Summarize this meeting with Luci.

The user will name when and where it ran (app, start, end).

Read ~/.Life/RULES.md first if it exists — the user's hand-written rules for these notes (who is who, who and what to leave out). Follow them for this write-up; they win over anything below. Never write to that file.

Use the luci skill to pull screen activity and transcripts from that window, then write one markdown file on disk — do not stop at a chat reply.

Pull the transcript with transcript --tr <RANGE> and no keywords: that returns every segment in the window in the order it was spoken. Keyword searches are for looking something up afterwards, not for reading the meeting.

Path: ~/.Life/reflections/meetings/YYYY-MM-DD-slug.md (Windows: %USERPROFILE%.Life\reflections\meetings\YYYY-MM-DD-slug.md) Slug: lowercase ASCII, digits, hyphens. Reuse the file if this window already has one.

YAML frontmatter is required:

---
title: Memories.ai Website Discussion
date: 2026-08-25
start: "23:02"
end: "23:12"
platform: Zoom
people:
  - shawn-shen
orgs:
  - memories-ai
projects:
  - luci-page
---

Use [] for an empty list. Body after the frontmatter is free markdown (who was there, what was discussed, decisions, action items, open questions — include a section only when you have something to put in it). ## Action items is the exception: write it every time.

## Action items
- [ ] <what, one line> @<owner-slug or me> due:<YYYY-MM-DD or none> ^[HH:MM]

One item per line. @me is the user; any other owner is the slug of an entities/people/<slug>.md file. Use - [x] for anything already finished during the call. ^[HH:MM] is the local time the item came up, read off the transcript. If nothing was assigned, write the section with the single line - none.

End every bullet under ## Decisions and ## Open questions with the same ^[HH:MM] anchor.

Create ~/.Life and the meetings / entities folders if they are missing. Do not delete anything already there.

Read ~/.Life/entities/ first. For every person, organization, and project that appeared in the evidence, reuse the existing file (match YAML name or the # heading). If none exists, create one:

  • people → ~/.Life/entities/people/<slug>.md
  • orgs → ~/.Life/entities/orgs/<slug>.md
  • projects → ~/.Life/entities/projects/<slug>.md

New entity file:

---
name: Shawn Shen
kind: person
---

# Shawn Shen

- 2026-08-25: Memories.ai Website Discussion

kind is person, org, or project. If today's date is not already a bullet, append - YYYY-MM-DD: <meeting title>. Never edit existing bullets.

Do not create a person file for the user (Zoom labels like (你), (You), Me) or for recording bots (Fathom, Otter, Fireflies, Notetaker).

Do not edit reflections/daily/. The day's capture blocks stay as distill wrote them.

Ground every claim in Luci results. If a Luci command exits non-zero, follow the luci skill's error rule: stop, write no file, and show the user the CLI's message verbatim. If a source is uncertain, leave it out. Never fabricate.

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.