What problem does it solve? Keeping track of colleagues, their aliases, roles, and squads is tedious, and voice memo transcriptions often reference people by nicknames that are hard to resolve. This Skill maintains a centralized stakeholder list so speaker matching, meeting note classification, and project inference work consistently across your PARA Obsidian workflows. ## Core Features & Use Cases - List, Add, Remove, and Lookup Stakeholders: Full CRUD operations against the stakeholder configuration stored in ~/.config/para-obsidian/config.json. - Bulk Import in Multiple Formats: Paste stakeholders as a table, CSV, or JSON and have them parsed, previewed, and confirmed before saving. - Alias and Email Lookup: Answer questions like "who is MJ?" by searching names, aliases, or email prefixes. - Use Case: After joining a new squad, paste your team's roster as CSV to register everyone at once, so future voice memos automatically match speakers like "MJ" to "Mustafa Jalil" and infer the correct project. ## Quick Start Ask the assistant to list your current stakeholders, or paste a table of team members and say "add these stakeholders" to register them for speaker matching.