Agent Browser
quran/quran.com-frontend-next
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
Review a meeting transcript and draft follow-up emails with action items to attendees.
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-meeting-followup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "spark-recipe-meeting-followup" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-meeting-followup into .claude/skills/spark-recipe-meeting-followup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-meeting-followup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-meeting-followupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-meeting-followup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/readdle/spark-cli-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/recipe-meeting-followup .agents/skills/spark-recipe-meeting-followup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spark-recipe-meeting-followup" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-meeting-followup into .agents/skills/spark-recipe-meeting-followup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-meeting-followup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-meeting-followup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/readdle/spark-cli-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/recipe-meeting-followup .cursor/skills/spark-recipe-meeting-followup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spark-recipe-meeting-followup" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-meeting-followup into .cursor/skills/spark-recipe-meeting-followup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-meeting-followup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/readdle/spark-cli-skills.git --path skills/recipe-meeting-followup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-meeting-followup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/readdle/spark-cli-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/recipe-meeting-followup .gemini/skills/spark-recipe-meeting-followup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spark-recipe-meeting-followup" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-meeting-followup into .gemini/skills/spark-recipe-meeting-followup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-meeting-followup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install readdle/spark-cli-skills spark-recipe-meeting-followupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/readdle/spark-cli-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/recipe-meeting-followup .github/skills/spark-recipe-meeting-followup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spark-recipe-meeting-followup" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-meeting-followup into .github/skills/spark-recipe-meeting-followup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-meeting-followup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-meeting-followup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-meeting-followup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/readdle/spark-cli-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/recipe-meeting-followup .opencode/skills/spark-recipe-meeting-followup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spark-recipe-meeting-followup" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-meeting-followup into .opencode/skills/spark-recipe-meeting-followup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-meeting-followup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
spark-recipe-meeting-followupReview 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.
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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cb20383. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from readdle/spark-cli-skills at commit cb20383, republished under its MIT licence (© readdle). 197 words, ~572 tokens.
.claude/skills/spark-recipe-meeting-followup/SKILL.md (or your agent's skills folder).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.
spark meetings --filter "newer_than:1d"Or search by topic:
spark meetings --filter "subject:standup"spark meeting <id>Read the AI-generated summary for key points.
spark meeting <id> --transcript --notesExtract action items, decisions, and follow-up commitments from the full transcript and notes.
spark contacts "attendee name"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.
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"spark meeting <id> (summary only) - the full transcript is often more detail than needed.--notes flag includes any notes taken during the meeting, which often contain the most actionable items.--transcript when the summary doesn't capture something the user remembers discussing.--to) rather than a reply unless there's an existing thread about the same topic.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
Just SKILL.md in skills/recipe-meeting-followup of readdle/spark-cli-skills.
Open the folder on GitHubat commit cb20383
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spark Recipe Meeting Followup this skillreaddle/spark-cli-skills | 149 | — | ~572 | Automated safety check: Pass | MIT | |
| Agent Browserquran/quran.com-frontend-next | 1.9k | 40 repos | ~3.3k | Automated safety check: Pass | None | |
| Dependency Watchtelegramdesktop/tdesktop | 33k | 1 repos | ~2.2k | Automated safety check: Pass | GPL-3.0 | |
| Perform Tasktelegramdesktop/tdesktop | 33k | 2 repos | ~3k | Automated safety check: Pass | GPL-3.0 | |
| Brave Searchbadlogic/pi-skills | 2.6k | 5 repos | ~592 | Automated safety check: Pass | MIT | |
| Garden Inboxpaperclipai/paperclip | 100k | — | ~1.1k | Automated safety check: Pass | MIT |
quran/quran.com-frontend-next
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
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.
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.
badlogic/pi-skills
Web search and content extraction via Brave Search API. An agent skill from badlogic/pi-skills.
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
readdle/spark-cli-skills
Executive assistant persona for Spark. An agent skill from readdle/spark-cli-skills.
readdle/spark-cli-skills
Founder / CEO persona for Spark. An agent skill from readdle/spark-cli-skills.
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.
readdle/spark-cli-skills
Freelancer / solo operator persona for Spark. An agent skill from readdle/spark-cli-skills.
readdle/spark-cli-skills
Meeting manager persona for Spark. An agent skill from readdle/spark-cli-skills.
readdle/spark-cli-skills
Project manager persona for Spark. An agent skill from readdle/spark-cli-skills.
Categories
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.
Spark Recipe Meeting Followup fits situations like: productivity & Automation work in your project.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Spark Recipe Meeting Followup is instructions for the agent only.
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.
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.
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.
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.
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.
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.