Recipe Create Meet Space
googleworkspace/cli
Create a Google Meet meeting space and share the join link. An agent skill from googleworkspace/cli.
Build a chronological narrative for a topic by interleaving meeting transcript excerpts and email thread summaries across a time range.
MITAuto-check passed
Install Spark Recipe Topic Timeline
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-topic-timeline -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-topic-timeline --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-topic-timeline .claude/skills/spark-recipe-topic-timeline && 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-topic-timeline" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-topic-timeline into .claude/skills/spark-recipe-topic-timeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-topic-timeline", 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-topic-timelineType 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-topic-timeline -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-topic-timeline --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-topic-timeline .agents/skills/spark-recipe-topic-timeline && 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-topic-timeline" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-topic-timeline into .agents/skills/spark-recipe-topic-timeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-topic-timeline", 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-topic-timeline -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-topic-timeline --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-topic-timeline .cursor/skills/spark-recipe-topic-timeline && 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-topic-timeline" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-topic-timeline into .cursor/skills/spark-recipe-topic-timeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-topic-timeline", 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-topic-timeline--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-topic-timeline -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install readdle/spark-cli-skills spark-recipe-topic-timeline --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-topic-timeline .gemini/skills/spark-recipe-topic-timeline && 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-topic-timeline" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-topic-timeline into .gemini/skills/spark-recipe-topic-timeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-topic-timeline", 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-topic-timelineInstalls 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-topic-timeline -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-topic-timeline .github/skills/spark-recipe-topic-timeline && 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-topic-timeline" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-topic-timeline into .github/skills/spark-recipe-topic-timeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-topic-timeline", 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-topic-timeline -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-topic-timeline --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-topic-timeline .opencode/skills/spark-recipe-topic-timeline && 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-topic-timeline" agent skill from https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-topic-timeline into .opencode/skills/spark-recipe-topic-timeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spark-recipe-topic-timeline", 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.
Facts
- Skill name
spark-recipe-topic-timeline- GitHub stars
- 149
- Token cost
- ~806 tokens
- SKILL.md length
- 375 words
- Files
- 1
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a chronological narrative for a topic by interleaving meeting transcript excerpts and email thread summaries across a time range.
- Works in 6 steps: Define the scope → Gather meeting data → Gather email data → …
- SKILL.md covers Steps and Tips
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Spark Recipe Topic Timeline is an agent skill from readdle/spark-cli-skills. Build a chronological narrative for a topic by interleaving meeting transcript excerpts and email thread summaries across a time range.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The licence is MIT.
Example prompts
- “/spark-recipe-topic-timeline”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
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 Topic Timeline loads about 806 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 375 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.
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). 375 words, ~806 tokens.
Download SKILL.mdSave it as
.claude/skills/spark-recipe-topic-timeline/SKILL.md (or your agent's skills folder).- name
- spark-recipe-topic-timeline
- description
- Build a chronological narrative for a topic by interleaving meeting transcript excerpts and email thread summaries across a time range.
- metadata.version
- 1.0.0
Recipe: Topic Timeline
For a given project or topic, build a unified chronological narrative by interleaving meeting discussions and email threads. Useful for catching up, briefing someone new, or preparing a status update.
Prerequisite: Read the use-spark base skill for command reference and filter syntax.
Access level required: read-only.
Steps
Step 1: Define the scope
Ask the user for:
- The topic or project name (keywords to search on)
- The time range (default to 30 days if unspecified)
Step 2: Gather meeting data
spark meetings --filter "subject:topic-keyword newer_than:30d"If the subject filter misses relevant meetings, broaden:
spark meetings --filter "newer_than:30d"For each relevant meeting, read the summary:
spark meeting <id>Pull full detail only for meetings where the topic was a major agenda item:
spark meeting <id> --transcript --notesRecord: date, participants, and the key points related to the topic.
Step 3: Gather email data
spark search "topic keyword"For threads that are clearly relevant, read the full conversation:
spark thread <id>If there are specific people associated with the topic, also pull their threads:
spark emails --filter "from:person@co.com subject:keyword newer_than:30d"Record: date of each message, participants, and the substance.
Step 4: Merge into a timeline
Combine all entries (meetings and emails) and sort by date. For each entry:
- Date
- Channel: Meeting / Email
- Participants
- What happened: one or two sentences summarizing the key substance
Step 5: Annotate the timeline
Layer on editorial notes:
- Mark turning points where direction changed
- Flag open threads that don't have a resolution
- Note gaps — periods with no activity that might indicate stalled progress
Show full SKILL.md (148 more words)Show less
Step 6: Present the timeline
Start with a one-paragraph executive summary of where the topic stands now, then present the full timeline oldest-to-newest. End with:
- Current status: the latest known state
- Open items: anything still unresolved
- Next touchpoint: upcoming meeting or pending email that will advance the topic
Tips
spark searchis relevance-ranked and returns full bodies — it's the best starting point for email discovery.- Meeting summaries usually capture the topic well enough. Reserve
--transcriptfor meetings where you need exact quotes or attribution. - For topics that span many months, work in chunks (e.g., month by month) to avoid overwhelming the output.
- This pairs well with
recipe-decision-tracker— use that recipe when you only need the decision points, and this one when you need the full narrative. - If building this for someone else (e.g., onboarding a new team member), call out any assumed context that an outsider wouldn't have.
© 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-topic-timeline of readdle/spark-cli-skills.
Open the folder on GitHubat commit cb20383
Compare with similar skills
Spark Recipe Topic Timeline 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 Topic Timeline this skillreaddle/spark-cli-skills | 149 | — | ~806 | Automated safety check: Pass | MIT | |
| Recipe Create Meet Spacegoogleworkspace/cli | 31k | — | ~189 | Automated safety check: Pass | Apache-2.0 | |
| Recipe Review Meet Participantsgoogleworkspace/cli | 31k | — | ~222 | Automated safety check: Pass | Apache-2.0 | |
| Meetingsalirezarezvani/claude-skills | 28k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Meeting Ingestiongarrytan/gbrain | 31k | — | ~7.7k | Automated safety check: Pass | MIT | |
| Recipe Reschedule Meetinggoogleworkspace/cli | 31k | — | ~243 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Recipe Review Meet Participants
googleworkspace/cli
Review who attended a Google Meet conference and for how long.
Meetings
alirezarezvani/claude-skills
A skill your agent uses when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into…
Meeting Ingestion
garrytan/gbrain
Ingest meeting transcripts from ANY meeting recorder into brain pages with attendee enrichment, entity propagation, and timeline merge.
Recipe Reschedule Meeting
googleworkspace/cli
Move a Google Calendar event to a new time and automatically notify all attendees.
Meeting Distiller Pro
sickn33/agentic-awesome-skills
Transform messy meeting notes and transcripts into structured action items, decisions, and follow-ups.
More from readdle/spark-cli-skills
All 34 skills in this repoSpark Persona Exec Assistant
readdle/spark-cli-skills
Executive assistant persona for Spark. An agent skill from readdle/spark-cli-skills.
Spark Persona Founder
readdle/spark-cli-skills
Founder / CEO persona for Spark. An agent skill from readdle/spark-cli-skills.
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.
Spark Persona Freelancer
readdle/spark-cli-skills
Freelancer / solo operator persona for Spark. An agent skill from readdle/spark-cli-skills.
Spark Persona Meeting Manager
readdle/spark-cli-skills
Meeting manager persona for Spark. An agent skill from readdle/spark-cli-skills.
Spark Persona Project Manager
readdle/spark-cli-skills
Project manager persona for Spark. An agent skill from readdle/spark-cli-skills.
Questions about Spark Recipe Topic Timeline
What does Spark Recipe Topic Timeline do?
Build a chronological narrative for a topic by interleaving meeting transcript excerpts and email thread summaries across a time range. Spark Recipe Topic Timeline is an agent skill from readdle/spark-cli-skills. Build a chronological narrative for a topic by interleaving meeting transcript excerpts and email thread summaries across a time range.
How do I install Spark Recipe Topic Timeline in Claude Code?
Run `npx skills add readdle/spark-cli-skills --skill spark-recipe-topic-timeline -a claude-code`. Or copy the skill folder (skills/recipe-topic-timeline in readdle/spark-cli-skills) into .claude/skills/spark-recipe-topic-timeline in your project. Claude Code loads it when a task matches its description.
How do I install Spark Recipe Topic Timeline in Codex?
Run `npx skills add readdle/spark-cli-skills --skill spark-recipe-topic-timeline -a codex`. Or copy the skill folder (skills/recipe-topic-timeline in readdle/spark-cli-skills) into .agents/skills/spark-recipe-topic-timeline in your project. Codex loads it when a task matches its description.
Can I use Spark Recipe Topic Timeline 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-topic-timeline -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-topic-timeline, .gemini/skills/spark-recipe-topic-timeline, .github/skills/spark-recipe-topic-timeline and .opencode/skills/spark-recipe-topic-timeline in your project.
What does Spark Recipe Topic Timeline need to run?
SKILL.md names no scripts, command-line tools or credentials: Spark Recipe Topic Timeline is instructions for the agent only.
Does Spark Recipe Topic Timeline 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 Topic Timeline 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 Topic Timeline use?
Spark Recipe Topic Timeline 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 Topic Timeline use?
About 806 tokens (SKILL.md is roughly 3.2k 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 Topic Timeline?
Skills that share tags, products or a category with Spark Recipe Topic Timeline: Recipe Create Meet Space (googleworkspace/cli, 31k stars), Recipe Review Meet Participants (googleworkspace/cli, 31k stars), Meetings (alirezarezvani/claude-skills, 28k stars) and Meeting Ingestion (garrytan/gbrain, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Spark Recipe Topic Timeline?
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.