spark-recipe-priority-tuning
Fine-tune Spark's priority category by marking key contacts as primary and adjusting notification importance.
- Installs
- 323
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-priority-tuning- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads spark-recipe-priority-tuning automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Recipe: Priority Tuning
Fine-tune who gets auto-prioritized by reviewing the current priority category and adjusting contact-level settings.
Prerequisite: Read the use-spark base skill for command reference and filter syntax.
Access level required: triage.
Steps
Step 1: Review current priority mail
spark emails Inbox --filter "category:priority newer_than:14d"
Look at which senders appear in the priority category. Ask the user: are these the right people? Anyone missing? Anyone who shouldn't be here?
Step 2: Check who's currently marked as primary
Browse priority mail to identify the senders Spark is auto-prioritizing. Note any patterns - are important contacts missing, or are low-priority senders appearing?
Step 3: Add missing VIPs
For contacts whose emails should always be prioritized:
spark contact-action markContactAsPrimary vip@company.com
This tells Spark to auto-prioritize all future email from this sender.
Step 4: Remove false priorities
For contacts that are showing up in priority but shouldn't be:
spark contact-action unmarkContactAsPrimary noisy-sender@example.com
Step 5: Adjust notification importance
For contacts where the user wants push notifications:
spark contact-action markContactAsImportant boss@company.com
For contacts that are priority but don't need notifications:
spark contact-action unmarkContactAsImportant low-urgency@example.com
Step 6: Verify the changes
spark emails Inbox --filter "category:priority is:unread"
Check that the priority category now reflects the user's preferences. New mail from adjusted contacts will appear in the correct category.
Tips
markContactAsPrimaryis the strongest signal - it guarantees the contact's emails land in priority.markContactAsImportantcontrols push notifications, which is separate from category placement.- Changes apply to all future mail from the contact, not retroactively to existing emails.
- Run this recipe after onboarding a new client, joining a new team, or changing roles - priority contacts change with context.
- When contacts are in the wrong category entirely (not just missing from priority), use
spark contact-action changeCategoryPersonal/changeCategoryNotification/changeCategoryNewslettersto reclassify all future mail from that sender. - A well-tuned priority category means the user can check just
category:priorityfor a reliable "must-read" view.
FAQ
What does the spark-recipe-priority-tuning skill do?
Fine-tune Spark's priority category by marking key contacts as primary and adjusting notification importance.
How do I install spark-recipe-priority-tuning?
Run npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-priority-tuning in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/spark-recipe-priority-tuning/ (personal) or .claude/skills/spark-recipe-priority-tuning/ (project).
Which AI agents can use spark-recipe-priority-tuning?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is spark-recipe-priority-tuning safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains spark-recipe-priority-tuning?
It is published by readdle in readdle/spark-cli-skills. It has 323 recorded installs.
More 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. Use when the user asks about their emails, calendar, contacts, meetings, or scheduling.
spark-recipe-morning-standup
readdle/spark-cli-skills
Morning standup briefing: today's events, unread people and priority mail, and team assignment status.
spark-recipe-inbox-by-category
readdle/spark-cli-skills
Process inbox in priority order by Spark's smart categories: priority first, then people, invites, notifications, newsletters.
spark-recipe-end-of-day
readdle/spark-cli-skills
End-of-day review: check for loose ends, review pinned items, and preview tomorrow's calendar.
spark-recipe-weekly-digest
readdle/spark-cli-skills
Open the skill to read its SKILL.md instructions.
spark-recipe-meeting-prep
readdle/spark-cli-skills
Prepare for an upcoming meeting: check agenda, search for email context, look up attendee details, and flag open threads that should be raised.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available