spark-recipe-stakeholder-brief
Build a comprehensive dossier on a person by pulling all meetings they attended and email threads with them into a single relationship brief.
- Installs
- 345
- 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-stakeholder-brief- 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-stakeholder-brief 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: 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
spark contacts "person name"
Note their email address(es) and any other details.
Step 2: Pull recent email threads
spark emails --filter "from:person@co.com newer_than:30d"
Also check emails sent to them:
spark emails --filter "to:person@co.com newer_than:30d"
For the most important threads, read the full conversation:
spark thread <id>
Note open threads (unanswered or pending action) vs. resolved ones.
Step 3: Find shared meetings
spark meetings --filter "newer_than:30d"
Scan meeting titles and participant lists for the person. For each relevant meeting, pull the summary:
spark meeting <id>
If the person's contributions or commitments aren't clear from the summary:
spark meeting <id> --transcript --notes
Step 4: Check upcoming events with them
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-prepwhich 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:14dto keep the brief focused. - For people you haven't spoken to in a while, widen to
newer_than:90dor useafter:yyyy/MM/ddto 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.
FAQ
What does the spark-recipe-stakeholder-brief skill do?
Build a comprehensive dossier on a person by pulling all meetings they attended and email threads with them into a single relationship brief.
How do I install spark-recipe-stakeholder-brief?
Run npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-stakeholder-brief 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-stakeholder-brief/ (personal) or .claude/skills/spark-recipe-stakeholder-brief/ (project).
Which AI agents can use spark-recipe-stakeholder-brief?
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-stakeholder-brief 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-stakeholder-brief?
It is published by readdle in readdle/spark-cli-skills. It has 345 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
Open the skill to read its SKILL.md instructions.
spark-recipe-inbox-by-category
readdle/spark-cli-skills
Open the skill to read its SKILL.md instructions.
spark-recipe-end-of-day
readdle/spark-cli-skills
Open the skill to read its SKILL.md instructions.
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 productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。