How do I install the Spark Recipe Invitation Manager skill?

Run npx skillmds@latest add readdle/spark-recipe-invitation-manager 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 Invitation Manager safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. 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 Invitation Manager?

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 Invitation Manager free to use?

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

Who published Spark Recipe Invitation Manager?

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

Spark Recipe Invitation Manager by readdle

Name: Spark Recipe Invitation Manager
Rating: 4.5 (4 reviews)
Author: readdle

File contents

Recipe: Invitation Manager

Process pending calendar invitations by checking availability for each and presenting a decision list with recommendations.

Prerequisite: Read the use-spark base skill for command reference and filter syntax.

Access level required: read-only.

Steps

Step 1: List pending invitations

spark emails Inbox --filter "category:invitation"

Collect all pending invitations. Note the senders, subjects, and IDs.

Step 2: Read each invitation

For each invitation, read the thread to understand the meeting details:

spark thread <id>

Note the proposed time, attendees, and purpose.

Step 3: Check availability for each

For each invitation's proposed time, check whether the user is free:

spark events --today

Or for a specific date range:

spark events --start 2026-04-14 --end 2026-04-14

For a broader view:

spark availability --start 2026-04-14 --end 2026-04-14

Step 4: Present a decision list

Summarize each invitation with a recommendation:

Accept - the user is free at the proposed time
Conflict - the user has an overlapping event (name the conflict)
Needs discussion - the user is technically free but the meeting needs clarification

Step 5: Check invitation responses

Review any invitation responses the user has received:

spark emails Inbox --filter "category:invitation_response"

Report who accepted, declined, or proposed alternative times.

Tips

Process invitations daily - they're time-sensitive and forgetting one can mean missing an important meeting.
Use availability to quickly check free slots rather than scanning through events manually.
Invitation responses (category:invitation_response) are a separate category - check them to see who RSVPed.
For recurring meeting invitations, read the thread to check if the pattern works long-term, not just the next occurrence.
When there's a conflict, suggest an alternative time by checking availability around the proposed date.
Combine with recipe-schedule-meeting when an invitation leads to rescheduling.

--- name: spark-recipe-invitation-manager description: >- Process pending calendar invitations: check availability and present a decision list with recommendations. metadata: version: 1.0.0 requires: skills: - use-spark accessLevel: read-only --- # Recipe: Invitation Manager Process pending calendar invitations by checking availability for each and presenting a decision list with recommendations. **Prerequisite:** Read the `use-spark` base skill for command reference and filter syntax. **Access level required:** read-only. ## Steps ### Step 1: List pending invitations ```bash spark emails Inbox --filter "category:invitation" ``` Collect all pending invitations. Note the senders, subjects, and IDs. ### Step 2: Read each invitation For each invitation, read the thread to understand the meeting details: ```bash spark thread <id> ``` Note the proposed time, attendees, and purpose. ### Step 3: Check availability for each For each invitation's proposed time, check whether the user is free: ```bash spark events --today ``` Or for a specific date range: ```bash spark events --start 2026-04-14 --end 2026-04-14 ``` For a broader view: ```bash spark availability --start 2026-04-14 --end 2026-04-14 ``` ### Step 4: Present a decision list Summarize each invitation with a recommendation: - **Accept** - the user is free at the proposed time - **Conflict** - the user has an overlapping event (name the conflict) - **Needs discussion** - the user is technically free but the meeting needs clarification ### Step 5: Check invitation responses Review any invitation responses the user has received: ```bash spark emails Inbox --filter "category:invitation_response" ``` Report who accepted, declined, or proposed alternative times. ## Tips - Process invitations daily - they're time-sensitive and forgetting one can mean missing an important meeting. - Use `availability` to quickly check free slots rather than scanning through `events` manually. - Invitation responses (`category:invitation_response`) are a separate category - check them to see who RSVPed. - For recurring meeting invitations, read the thread to check if the pattern works long-term, not just the next occurrence. - When there's a conflict, suggest an alternative time by checking `availability` around the proposed date. - Combine with `recipe-schedule-meeting` when an invitation leads to rescheduling.

Frequently asked questions

Spark Recipe Invitation Manager