spark-recipe-end-of-day — Claude Code skill: wrap up your day
This skill closes out the workday in Spark: unreplied mail, pinned items, and tomorrow's calendar in one pass.
npx skills add readdle/spark-cli-skills --skill spark-recipe-end-of-day -a claude-code
npx skills add readdle/spark-cli-skills --skill recipe-end-of-day -a claude-codeWhat spark-recipe-end-of-day does
The skill walks through Spark mail and calendar at the end of the day. First it pulls unread people mail from the last day with spark emails Inbox --filter "category:personal is:unread newer_than:1d", then checks unread priority mail on its own. Next it lists pinned emails and points out which ones look resolved, so you can unpin them in Spark. The last step runs spark events --tomorrow and flags meetings that need prep.
Access is read-only. You need the base use-spark skill first, since it holds the command reference and filter syntax the steps rely on.
It finishes with a summary: how many emails await a reply, with senders and subjects; how many pins are active versus resolved; which meetings are on tomorrow and which need preparation. When the unreplied pile is large, it helps you pick the one or two most urgent. Think of it as the evening half of recipe-morning-standup.
What it helps with
- find unreplied people mail from today
- surface unread priority emails
- clear out stale pinned emails
- preview tomorrow's meetings
- flag meetings that need prep
Example prompts for the agent
- show me what's still unreplied from today
- which pinned emails can I unpin now
- what's on my calendar tomorrow and what needs prep
How to install spark-recipe-end-of-day
1Skills CLI (Vercel)
npx skills add readdle/spark-cli-skills --skill spark-recipe-end-of-day -a claude-codenpx skills add readdle/spark-cli-skills --skill recipe-end-of-day -a claude-code2Manually: put the files in place
~/.claude/skills/recipe-end-of-day/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/recipe-end-of-day/
1Skills CLI (Vercel)
npx skills add readdle/spark-cli-skills --skill recipe-end-of-day -a codex2Manually: put the files in place
.agents/skills/recipe-end-of-day/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add readdle/spark-cli-skills --skill recipe-end-of-day -a cursor2Manually: put the files in place
.cursor/skills/recipe-end-of-day/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install readdle/spark-cli-skills recipe-end-of-day2Manually: put the files in place
.github/skills/recipe-end-of-day/SKILL.md1Skills CLI (Vercel)
npx skills add readdle/spark-cli-skills --skill recipe-end-of-day -a gemini-cli2Platform CLI
gemini skills install https://github.com/readdle/spark-cli-skills --path skills/recipe-end-of-dayManually: put the files in place
.devin/skills/recipe-end-of-day/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add readdle/spark-cli-skills --skill recipe-end-of-day -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about spark-recipe-end-of-day
How do I install spark-recipe-end-of-day in Claude?
Run npx skills add readdle/spark-cli-skills --skill spark-recipe-end-of-day -a claude-code. The skill lands at ~/.claude/skills/recipe-end-of-day/SKILL.md.
What does spark-recipe-end-of-day do?
It runs an end-of-day review: unreplied people and priority mail, pinned items, and tomorrow's calendar. Then it reports a summary of all three.
What does the skill need to work?
The base use-spark skill for command reference and filter syntax. Access is read-only, so it never sends mail.
Source text
SKILL.md · MIT
---
name: spark-recipe-end-of-day
description: >-
End-of-day review: check for loose ends, review pinned items,
and preview tomorrow's calendar.
metadata:
version: 1.0.0
requires:
skills:
- use-spark
accessLevel: read-only
---
# Recipe: End of Day
Close out the workday by reviewing loose ends, checking pinned items, and previewing tomorrow's schedule.
**Prerequisite:** Read the `use-spark` base skill for command reference and filter syntax.
**Access level required:** read-only.
## Steps
### Step 1: Check for unreplied people mail from today
```bash
spark emails Inbox --filter "category:personal is:unread newer_than:1d"
```
Any unread people mail from today likely needs a response. Flag these for the user.
### Step 2: Check unreplied priority mail
```bash
spark emails Inbox --filter "category:priority is:unread"
```
Priority items that are still unread at end of day need explicit attention or deferral.
### Step 3: Review pinned items
```bash
spark emails Inbox --filter "is:pinned"
```
Are any pinned items now resolved? Note which ones can be unpinned so the user can clean them up in Spark.
### Step 4: Preview tomorrow's calendar
```bash
spark events --tomorrow
```
Flag any meetings that need preparation. If a meeting needs prep, note it so the user can use `recipe-meeting-prep` in the morning.
### Step 5: Present the summary
Report to the user:
- **Loose ends:** N unreplied people/priority emails (list senders and subjects)
- **Pinned items:** M active, K look resolved
- **Tomorrow:** P meetings (list times and titles), any needing prep
## Tips
- This recipe is the bookend to `recipe-morning-standup` - start with standup, end with this.
- The goal is to surface everything the user needs to know so they can close out the day with confidence.
- If there are many unreplied items, help the user prioritize which 1-2 are most urgent.
- Reviewing pinned items prevents pin buildup - items stay pinned long after they're relevant.
- The tomorrow calendar preview helps the user mentally prepare and wake up ready for the first meeting.
© readdle · MIT · readdle/spark-cli-skills