agentleFS
Sign inStart free
jholhewresjholhewres/devclaw-skills/skills/meeting-notes/SKILL.md

meeting-notes

Skill4 starsChanged 9 months agoMITView on GitHub

Structured meeting notes with action items extraction

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use write_file, read_file, edit_file, and memory_save for meeting notes.

    line 7
  2. Very specific:

    Use write_file to create ~/.devclaw/meetings/YYYY-MM-DD-<title>.md:

    line 10
  3. Very specific:

    Create dir on first use: mkdir -p ~/.devclaw/meetings

    line 50
  4. Distinctive:

    When user pastes raw meeting notes, restructure into template

    line 53

“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

Use write_file, read_file, edit_file, and memory_save for meeting notes.

Create Meeting Note

Use write_file to create ~/.devclaw/meetings/YYYY-MM-DD-<title>.md:

# Meeting: <Title>
**Date:** YYYY-MM-DD HH:MM
**Attendees:** Name1, Name2, Name3
**Type:** standup | planning | retro | 1:1 | brainstorm | review

## Agenda
1. ...
2. ...

## Notes
- ...

## Decisions
- [ ] Decision 1

## Action Items
- [ ] @Name1 — Task description (due: YYYY-MM-DD)
- [ ] @Name2 — Task description (due: YYYY-MM-DD)

## Follow-up
- Next meeting: YYYY-MM-DD

Search Meetings

ls -lt ~/.devclaw/meetings/ | head -20
grep -rl "TERM" ~/.devclaw/meetings/ --include="*.md"
grep -rl "@PersonName" ~/.devclaw/meetings/ --include="*.md"

Extract Action Items

grep -h "\- \[ \]" ~/.devclaw/meetings/*.md | sort
grep -h "\- \[ \] @Name" ~/.devclaw/meetings/*.md   # by person

Tips

  • Create dir on first use: mkdir -p ~/.devclaw/meetings
  • Save key decisions with memory_save for long-term recall
  • Extract action items and offer to create reminders (cron_add)
  • When user pastes raw meeting notes, restructure into template

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