Skip to main content
skill CX Codex

spark-recipe-stakeholder-brief — Claude Code skill: person dossier

Pulls a person's meetings and email threads into one relationship brief. Handy before a 1:1 or when reconnecting after a gap.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add readdle/spark-cli-skills --skill spark-recipe-stakeholder-brief -a claude-code
npx skills add readdle/spark-cli-skills --skill recipe-stakeholder-brief -a claude-code
Open on GitHub

What spark-recipe-stakeholder-brief does

Give the skill a name and it walks your Spark data: looks up the contact, then emails from and to them, then meetings they attended, then upcoming events. The output is a brief split into contact details, last interaction, open items, recent topics and what is already scheduled.

Six steps drive it, using spark contacts, spark emails --filter, spark thread <id>, spark meetings --filter, spark meeting <id> and spark events --week. When a meeting summary leaves commitments unclear, it pulls spark meeting <id> --transcript --notes. You need read-only access and the base use-spark skill, which documents the filter syntax.

The default window is 30 days. The author suggests newer_than:14d for people you talk to often, and newer_than:90d or after:yyyy/MM/dd for those you have not spoken to in a while. This is person-centric, unlike recipe-meeting-prep, which preps a single event.

What it helps with

  • build a history of talks with a colleague before a 1:1
  • surface commitments left open across email and meetings
  • prepare for a performance review from records, not memory
  • reconnect with someone after a long gap
  • check what is already scheduled with this person this week

Example prompts for the agent

  • Build a stakeholder brief on Anna Petrova for the last 30 days
  • What is still unanswered in my threads with [email protected]?
  • Put together a dossier on Ivan before tomorrow's meeting

How to install spark-recipe-stakeholder-brief

1Skills CLI (Vercel)

npx skills add readdle/spark-cli-skills --skill spark-recipe-stakeholder-brief -a claude-code
npx skills add readdle/spark-cli-skills --skill recipe-stakeholder-brief -a claude-code

2Manually: put the files in place

~/.claude/skills/recipe-stakeholder-brief/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/recipe-stakeholder-brief/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about spark-recipe-stakeholder-brief

How do I install spark-recipe-stakeholder-brief in Claude?

Run npx skills add readdle/spark-cli-skills --skill spark-recipe-stakeholder-brief -a claude-code, then npx skills add readdle/spark-cli-skills --skill recipe-stakeholder-brief -a claude-code. The skill file lands at ~/.claude/skills/recipe-stakeholder-brief/SKILL.md.

What does spark-recipe-stakeholder-brief do?

Given a person's name, it gathers their meetings and email threads into one brief covering contact details, last interaction, open items, topics and upcoming events.

What do I need for it to work?

Read-only access and the base use-spark skill, which covers the filter syntax. Without it the spark emails --filter and spark meetings --filter steps have no reference.

Source text

SKILL.md · MIT
---
name: spark-recipe-stakeholder-brief
description: >-
  Build a comprehensive dossier on a person by pulling all meetings they
  attended and email threads with them into a single relationship brief.
metadata:
  version: 1.0.0
  requires:
    skills:
      - use-spark
    accessLevel: read-only
---

# Recipe: Stakeholder Brief

Given a person's name, compile all recent interactions — meetings and emails — into a relationship brief. Useful before 1:1s, performance reviews, or re-engaging with someone after a gap.

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

**Access level required:** read-only.

## Steps

### Step 1: Look up the person

```bash
spark contacts "person name"
```

Note their email address(es) and any other details.

### Step 2: Pull recent email threads

```bash
spark emails --filter "from:[email protected] newer_than:30d"
```

Also check emails sent to them:

```bash
spark emails --filter "to:[email protected] newer_than:30d"
```

For the most important threads, read the full conversation:

```bash
spark thread <id>
```

Note open threads (unanswered or pending action) vs. resolved ones.

### Step 3: Find shared meetings

```bash
spark meetings --filter "newer_than:30d"
```

Scan meeting titles and participant lists for the person. For each relevant meeting, pull the summary:

```bash
spark meeting <id>
```

If the person's contributions or commitments aren't clear from the summary:

```bash
spark meeting <id> --transcript --notes
```

### Step 4: Check upcoming events with them

```bash
spark events --week
```

Note any upcoming meetings where this person is an attendee.

### Step 5: Compile the brief

Organize into sections:

- **Contact:** name, email, role (if known from context)
- **Last interaction:** date and channel (meeting or email)
- **Open items:** threads awaiting response, commitments not yet fulfilled
- **Recent topics:** what you've discussed across meetings and email (grouped by theme)
- **Upcoming:** any scheduled meetings with them
- **Key context:** notable decisions made together, recurring discussion themes

### Step 6: Present the brief

Lead with the most actionable information — open items and upcoming meetings — then provide the fuller context. Flag anything that looks like it needs attention before the next interaction.

## Tips

- This recipe is person-centric, unlike `recipe-meeting-prep` which is event-centric. Use this when you want to understand the full relationship, not just prep for one meeting.
- For people you interact with frequently, narrow the time window to `newer_than:14d` to keep the brief focused.
- For people you haven't spoken to in a while, widen to `newer_than:90d` or use `after:yyyy/MM/dd` to capture the last meaningful period.
- Use `spark search "person name"` as a supplementary search to catch threads where they're mentioned but not in the from/to fields.
- If the person is a teammate, `spark team "Team Name"` may show their current email assignments.

© readdle · MIT · readdle/spark-cli-skills

Similar skills

Everything for Notes, tasks and projects →

From the same set19

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor