Manage stakeholders for voice memo speaker matching. Add, list, lookup, or remove stakeholders used by triage and meeting skills. Use when team members change, to verify current configuration, or to look up "who is [alias]?"
From para-obsidiannpx claudepluginhub nathanvale/side-quest-marketplace-old --plugin para-obsidianThis skill is limited to using the following tools:
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Manage the stakeholder list used for voice memo speaker matching, meeting note classification, and project inference.
Stakeholders are people you interact with regularly. They are stored in ~/.config/para-obsidian/config.json under the stakeholders key. Other skills use them to:
| Field | Required | Description | Example |
|---|---|---|---|
name | Yes | Full name as it appears in transcriptions | "June Xu" |
email | No | Email address for contact lookup | "JXu3@bunnings.com.au" |
role | No | Job title or role | "Developer" |
company | No | Company or organization | "Bunnings" |
squad | No | Squad or team name | "GMS (POS Yellow)" |
project | No | Related project wikilink | "[[GMS]]" |
alias | No | Nickname used in transcriptions | "MJ" |
Show all currently configured stakeholders:
para_stakeholder_list({ response_format: "json" })
If no stakeholders exist, offer to add some.
Accept stakeholders via bulk paste or one-at-a-time entry.
Accept any of these formats and parse into stakeholder objects:
Table format:
Name | Role | Email | Company | Squad
June Xu | Developer | JXu3@bunnings.com.au | Bunnings | GMS (POS Yellow)
Mustafa Jalil | Backend Dev | MJalil@bunnings.com.au | Bunnings | GMS (POS Yellow)
CSV format:
name,role,email,company,squad,project,alias
June Xu,Developer,JXu3@bunnings.com.au,Bunnings,GMS (POS Yellow),[[GMS]],
Mustafa Jalil,Backend Dev,MJalil@bunnings.com.au,Bunnings,GMS (POS Yellow),[[GMS]],MJ
JSON format:
[
{ "name": "June Xu", "role": "Developer", "email": "JXu3@bunnings.com.au" },
{ "name": "Mustafa Jalil", "alias": "MJ", "role": "Backend Dev" }
]
Parsed N stakeholders:
- June Xu (Developer) - Bunnings/GMS
- Mustafa Jalil aka MJ (Backend Dev) - Bunnings/GMS
para_stakeholder_add({ stakeholders: [...], response_format: "json" })
Ask for each field interactively:
After each stakeholder, ask if they want to add another.
Remove by name or alias:
para_stakeholder_remove({ name: "MJ", response_format: "json" })
If the user provides a name that doesn't match, show the error and suggest using para_stakeholder_list to find the correct name.
Search by name, alias, or email prefix:
para_stakeholder_lookup({ query: "MJ", response_format: "json" })
Useful for:
When the user invokes the skill without specifying an operation, check their input:
| User Says | Operation |
|---|---|
| (no argument) | List all stakeholders |
| "add" or pastes data | Add flow |
| "remove [name]" or "delete [name]" | Remove flow |
| A name/alias/question like "who is MJ?" | Lookup flow |
| Error | Recovery |
|---|---|
| No stakeholders configured | Offer to add some |
| Name not found on remove | Show current list, suggest correct name |
| No matches on lookup | Suggest checking spelling or listing all |
| Config file missing | saveStakeholders creates it automatically |