Agent skill

Spark Recipe Meeting Followup

by readdle in readdle/spark-cli-skills

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

MITAuto-check passedProductivity & Automation

Install Spark Recipe Meeting Followup

skills CLI
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install readdle/spark-cli-skills spark-recipe-meeting-followup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/readdle/spark-cli-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/recipe-meeting-followup .claude/skills/spark-recipe-meeting-followup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
spark-recipe-meeting-followup
GitHub stars
149
Token cost
~572 tokens
SKILL.md length
197 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 6 steps: Find the meeting transcript → Review the summary → Get full details if needed → …
  • Productivity & Automation work in your project
  • SKILL.md covers Steps and Tips
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spark Recipe Meeting Followup is an agent skill from readdle/spark-cli-skills. Review a meeting transcript and draft follow-up emails with action items to attendees.

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation. The licence is MIT.

When your agent uses it

  • Productivity & Automation work in your project

Example prompts

  • “/spark-recipe-meeting-followup”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Find the meeting transcript
  2. Review the summary
  3. Get full details if needed
  4. Look up attendee emails
  5. Draft the follow-up
  6. Share with team if relevant

What it can do on your machine

Read from SKILL.md and the folder at commit cb20383. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spark Recipe Meeting Followup loads about 572 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 197 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~572

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from readdle/spark-cli-skills at commit cb20383, republished under its MIT licence (© readdle). 197 words, ~572 tokens.

Download SKILL.mdSave it as .claude/skills/spark-recipe-meeting-followup/SKILL.md (or your agent's skills folder).
name
spark-recipe-meeting-followup
description
Review a meeting transcript and draft follow-up emails with action items to attendees.
metadata.version
1.0.0

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
bash
spark meetings --filter "newer_than:1d"

Or search by topic:

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

Read the AI-generated summary for key points.

Step 3: Get full details if needed
bash
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
bash
spark contacts "attendee name"
Step 5: Draft the follow-up
bash
spark draft --to "attendee1@co.com" --to "attendee2@co.com" --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:

bash
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.

© readdle, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/recipe-meeting-followup of readdle/spark-cli-skills.

Open the folder on GitHubat commit cb20383

Compare with similar skills

Spark Recipe Meeting Followup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spark Recipe Meeting Followup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spark Recipe Meeting Followup this skillreaddle/spark-cli-skills149—~572Automated safety check: PassMIT
Agent Browserquran/quran.com-frontend-next1.9k40 repos~3.3kAutomated safety check: PassNone
Dependency Watchtelegramdesktop/tdesktop33k1 repos~2.2kAutomated safety check: PassGPL-3.0
Perform Tasktelegramdesktop/tdesktop33k2 repos~3kAutomated safety check: PassGPL-3.0
Brave Searchbadlogic/pi-skills2.6k5 repos~592Automated safety check: PassMIT
Garden Inboxpaperclipai/paperclip100k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Agent Browser

    quran/quran.com-frontend-next

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    1.9k GitHub starsUsed in 40 repos~3.3k tokens
    Productivity & AutomationAuto-check passed
  • Dependency Watch

    telegramdesktop/tdesktop

    Audit Telegram Desktop dependencies on freshly fetched origin/dev for releases and security fixes, including upstream lag and backport candidates in patched forks.

    33k GitHub starsUsed in 1 repo~2.2k tokens
    Productivity & AutomationAuto-check passed
  • Perform Task

    telegramdesktop/tdesktop

    Resolve, start or resume, implement, review, test, and publish exactly one existing ai-tdesktop task by short slug or full dated id, including rare blocked retries and split-required results.

    33k GitHub starsUsed in 2 repos~3k tokens
    Productivity & AutomationAuto-check passed
  • Brave Search

    badlogic/pi-skills

    Web search and content extraction via Brave Search API. An agent skill from badlogic/pi-skills.

    2.6k GitHub starsUsed in 5 repos~592 tokens
    Productivity & AutomationAuto-check passed
  • Garden Inbox

    paperclipai/paperclip

    Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.

    100k GitHub stars~1.1k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Continue

    telegramdesktop/tdesktop

    Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.

    33k GitHub starsUsed in 2 repos~9.4k tokens
    Productivity & AutomationAuto-check passed

More from readdle/spark-cli-skills

All 34 skills in this repo
  • Spark Persona Exec Assistant

    readdle/spark-cli-skills

    Executive assistant persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~775 tokensUpdated 4 days ago
    Auto-check passed
  • Spark Persona Founder

    readdle/spark-cli-skills

    Founder / CEO persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed
  • Use Spark

    readdle/spark-cli-skills

    Use the spark CLI to access the user's Spark email data - list emails, search by topic, read threads, check calendar events, find availability, look up contacts, and view team info.

    149 GitHub stars~14k tokensUpdated 4 days ago
    Auto-check: warnings
  • Spark Persona Freelancer

    readdle/spark-cli-skills

    Freelancer / solo operator persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed
  • Spark Persona Meeting Manager

    readdle/spark-cli-skills

    Meeting manager persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed
  • Spark Persona Project Manager

    readdle/spark-cli-skills

    Project manager persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed

Questions about Spark Recipe Meeting Followup

What does Spark Recipe Meeting Followup do?

Review a meeting transcript and draft follow-up emails with action items to attendees. Spark Recipe Meeting Followup is an agent skill from readdle/spark-cli-skills. Review a meeting transcript and draft follow-up emails with action items to attendees.

When should I use Spark Recipe Meeting Followup?

Spark Recipe Meeting Followup fits situations like: productivity & Automation work in your project.

How do I install Spark Recipe Meeting Followup in Claude Code?

Run `npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a claude-code`. Or copy the skill folder (skills/recipe-meeting-followup in readdle/spark-cli-skills) into .claude/skills/spark-recipe-meeting-followup in your project. Claude Code loads it when a task matches its description.

How do I install Spark Recipe Meeting Followup in Codex?

Run `npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a codex`. Or copy the skill folder (skills/recipe-meeting-followup in readdle/spark-cli-skills) into .agents/skills/spark-recipe-meeting-followup in your project. Codex loads it when a task matches its description.

Can I use Spark Recipe Meeting Followup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spark-recipe-meeting-followup, .gemini/skills/spark-recipe-meeting-followup, .github/skills/spark-recipe-meeting-followup and .opencode/skills/spark-recipe-meeting-followup in your project.

What does Spark Recipe Meeting Followup need to run?

SKILL.md names no scripts, command-line tools or credentials: Spark Recipe Meeting Followup is instructions for the agent only.

Does Spark Recipe Meeting Followup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spark Recipe Meeting Followup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Spark Recipe Meeting Followup use?

Spark Recipe Meeting Followup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spark Recipe Meeting Followup use?

About 572 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spark Recipe Meeting Followup?

Skills that share tags, products or a category with Spark Recipe Meeting Followup: Agent Browser (quran/quran.com-frontend-next, 1.9k stars), Dependency Watch (telegramdesktop/tdesktop, 33k stars), Perform Task (telegramdesktop/tdesktop, 33k stars) and Brave Search (badlogic/pi-skills, 2.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spark Recipe Meeting Followup?

readdle (a GitHub organization) maintains it in readdle/spark-cli-skills, which has 149 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 7, 2026.

Source: readdle/spark-cli-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.