mcpField
S
spark-recipe-meeting-followup

spark-recipe-meeting-followup

github.com/readdleProductivity154317 installsUpdated 6d ago
Repository

About spark-recipe-meeting-followup

A Spark recipe skill for turning meeting transcripts into action items and attendee follow-up email drafts. It guides Spark users through reviewing summaries or full notes, finding contacts, and confirming draft content before creation.

Key features

  1. 01Find meetings by date or topic
  2. 02Review summaries, transcripts, and notes
  3. 03Extract decisions and action items
  4. 04Look up attendee email addresses
  5. 05Draft follow-up emails for confirmation

Use cases

  1. 01Send attendees a recap with owners and deadlines
  2. 02Find the latest recurring meeting transcript
  3. 03Share follow-up action items with a team

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-meeting-followup

After installing, type/spark-recipe-meeting-followupin Claude Code to confirm it loaded.

Details

From the project README

Recipe: Meeting Follow-Up

Review a meeting transcript, extract action items, and draft follow-up emails to attendees.

Prerequisite: Read the use-spark base skill for command reference and filter syntax.

Access level required: triage.

Steps

Step 1: Find the meeting transcript
spark meetings --filter "newer_than:1d"

Or search by topic:

spark meetings --filter "subject:standup"
Step 2: Review the summary
spark meeting <id>

Read the AI-generated summary for key points.

Step 3: Get full details if needed
spark meeting <id> --transcript --notes

Extract action items, decisions, and follow-up commitments from the full transcript and notes.

Step 4: Look up attendee emails
spark contacts "attendee name"
Step 5: Draft the follow-up
spark draft --to "[email protected]" --to "[email protected]" --subject "Follow-up: Meeting Topic - Action Items" --body "Hi team,\n\nHere are the action items from today's meeting:\n\n- [ ] Item 1 (Owner: Alice, Due: Friday)\n- [ ] Item 2 (Owner: Bob, Due: Next week)\n\nLet me know if I missed anything.\n\nBest regards"

Always confirm the draft content with the user before creating it.

Step 6: Share with team if relevant

If the action items should be visible to the team:

spark comment <related-thread-id> --body "Meeting follow-up posted - see action items in the follow-up email"

Tips

  • Start with just spark meeting <id> (summary only) - the full transcript is often more detail than needed.
  • The --notes flag includes any notes taken during the meeting, which often contain the most actionable items.
  • Use --transcript when the summary doesn't capture something the user remembers discussing.
  • Draft the follow-up as a new email (--to) rather than a reply unless there's an existing thread about the same topic.
  • For recurring meetings (standups, weeklies), use spark meetings --filter "subject:standup newer_than:7d" to find the latest.

Comments

Markdown supported