agentsclimarketplace

Meeting to actions

Skill tmusser/context-to-action-skills/skills/meeting-to-actions

Claude skills for turning messy business context into clear asks, decisions, owners, updates, and follow-ups.

Install
npx -y skills add tmusser/context-to-action-skills --skill meeting-to-actions

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

One thing to look at

  • 2 stars2 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

Turn meeting notes or transcripts into decisions, action items, owners, dates, blockers, and follow-ups.

SKILL.md

2.0 KB, as published. Nobody here has run it

meeting-to-actions

Purpose

Turn meeting content into a compact action record without making the user reread the whole transcript.

Use For

  • Zoom transcripts
  • Meeting notes
  • Slack threads
  • Email chains
  • Doc comment threads
  • Ticket discussions
  • Post-meeting cleanup
  • Preparing follow-up messages or ticket updates

Inputs

  • Zoom transcript
  • Notes
  • Agenda
  • Related ticket or doc context when useful
  • A reduce-to-facts ledger or conversation-state record

Guardrails

  • Read before write.
  • Do not send follow-ups or update tickets unless explicitly asked.
  • Separate decisions made from open decisions.
  • Name owners and dates only when the source supports them.
  • Surface missing owners, due dates, and unclear blockers.
  • Do not dump raw transcript content by default.

Portable Output Contract

  • Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the suggested next action.
  • Use the smallest useful output.
  • Label assumptions and preserve source gaps, source anchors, and confidence labels.
  • When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a fact, decision, commitment, owner, or deadline without new source support.
  • Keep unresolved approvals, owners, timing, and blockers explicit in the action record.
  • Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.

Output

  • Decisions made
  • Open decisions
  • Action items with owner and due date
  • Blockers
  • Follow-up drafts
  • Tickets/docs to update if applicable
  • Source gaps

If the user wants a reusable record, use the optional CONVERSATION_STATE.md template from this pack when it is available.

Success Standard

The user should leave the meeting with an action record they can send or use immediately.

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.