agentleFS
kronus-techkronus-tech/kronus/.claude/skills/meeting-notes/SKILL.md

meeting-notes

Skill4 starsChanged 7 months agoMITView on GitHub

Extract action items, decisions, and key points from a meeting transcript. Auto-invoked when a meeting transcript is pasted or user says "meeting notes", "extract action items", "summarize this meeting".

Files
SKILL.md

Process the following meeting transcript right now and extract structured notes:

Transcript: $ARGUMENTS

Extract and output:

Summary

2-4 sentence overview of what was discussed and decided.

Key Decisions

  • Decision: [what] — Rationale: [why]

Action Items

  • [Owner]: [task] — Due: [date] — Priority: [high/medium/low]

(Convert relative dates to absolute, e.g. "Friday" → actual date. Flag items missing owners or deadlines with "NEEDS OWNER" or "NEEDS DEADLINE".)

Blockers

  • [what's blocking] → [who's affected] → [resolution needed]

Open Questions

  • [unanswered items for follow-up]

Next Steps

  • [immediate actions, 24-48 hours]

Output as markdown ready to paste into Slack or Notion.

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.