agentsclimarketplace

Meeting to actions

Skill moses607/skillforge/skills/meeting-to-actions

SkillForge — production-ready Claude & Claude Code skills for developers, knowledge workers, and marketers. 9 free skills (MIT) + a Pro pack.

Install
npx -y skills add moses607/skillforge --skill meeting-to-actions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Convert meeting notes, a transcript, or a rough recap into a clean record of decisions, owned action items, and a follow-up message. Use whenever the user pastes meeting notes or a transcript, says "summarize this meeting", "what did we decide", "pull the action items", "who owns what", or asks for a recap email after a call. Trigger even from messy or partial notes.

SKILL.md

2.2 KB, as published. Nobody here has run it

Meeting to Actions

A meeting only pays off if decisions and owners survive it. Extract signal (decisions + actions), drop chit-chat, and make every commitment traceable to a person.

Extraction rules

  • Decision = a choice the group settled ("we'll go with Postgres"). Capture the decision AND its rationale if stated — future readers ask "why".
  • Action item = something a specific person will do by some time. Every action needs an owner. If the notes name no owner, write owner: UNASSIGNED — surfacing the gap is the point.
  • Open question = unresolved, needs a decision later. Don't fabricate resolutions.
  • Discard: greetings, tangents, re-litigated points that were then dropped, filler.

Output template

ALWAYS produce these three blocks:

## <Meeting> — <date>

### Decisions
1. <decision> — rationale: <if given, else "not stated">

### Action items
| # | Action | Owner | Due | Notes |
|---|--------|-------|-----|-------|
| 1 | <verb-first, concrete> | <name> | <date or "TBD"> | |

### Open questions
- <question> — <who needs to answer / by when>

Then, unless told not to, draft a follow-up message (Slack-length by default; email if the meeting was external):

### Follow-up draft
Subject: <meeting> — decisions & next steps
<2-3 line recap. Then the action list, each line "@owner: <action> (by <date>)". Close with the next checkpoint.>

Rules

  • Actions start with a verb: "Draft the RFC", not "RFC".
  • Never invent an owner or a due date. UNASSIGNED / TBD are correct answers.
  • If two people seem jointly responsible, name a single directly responsible owner and list the other as support — shared ownership means no ownership.
  • Keep the recap skimmable: a busy attendee should get the gist in 15 seconds.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.