How do I install the Spark Recipe Priority Tuning skill?

Run npx skillmds add readdle/spark-recipe-priority-tuning in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spark Recipe Priority Tuning safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spark Recipe Priority Tuning?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spark Recipe Priority Tuning free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spark Recipe Priority Tuning?

readdle (@readdle) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spark Recipe Priority Tuning by readdle

Name: Spark Recipe Priority Tuning
Rating: 4.666666666666667 (3 reviews)
Author: readdle

File contents

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

markContactAsPrimary is the strongest signal - it guarantees the contact's emails land in priority.
markContactAsImportant controls 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 / changeCategoryNewsletters to reclassify all future mail from that sender.
A well-tuned priority category means the user can check just category:priority for a reliable "must-read" view.

---name: spark-recipe-priority-tuningdescription: Fine-tune Spark's priority category by marking key contacts as primary and adjusting notification importance.--- # 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 ```bash 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: ```bash 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: ```bash spark contact-action unmarkContactAsPrimary noisy-sender@example.com ``` ### Step 5: Adjust notification importance For contacts where the user wants push notifications: ```bash spark contact-action markContactAsImportant boss@company.com ``` For contacts that are priority but don't need notifications: ```bash spark contact-action unmarkContactAsImportant low-urgency@example.com ``` ### Step 6: Verify the changes ```bash 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 - `markContactAsPrimary` is the strongest signal - it guarantees the contact's emails land in priority. - `markContactAsImportant` controls 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` / `changeCategoryNewsletters` to reclassify all future mail from that sender. - A well-tuned priority category means the user can check just `category:priority` for a reliable "must-read" view.

Frequently asked questions