who-is-speaking

who-is-speaking

Identify the family member for the current session on a shared family vault, then lock + set mode.

Examples / Exemples

Moved here from the frontmatter: the Agent Skills specification caps description at 1024 characters, and worked examples are activation-time guidance, not discovery-time metadata — the body is where they belong under progressive disclosure.

• EN: "I'm Karine, let's go" → identify as Karine, lock to vault_tribu, set Hybrid mode.
• FR: "c'est Roland, on enchaîne" → identifie comme Roland, lock vault_tribu, mode Hybrid.
• EN: "who's speaking today?" → ask the user (don't guess), then identify.

Pre-conditions

This skill only makes sense when the current default vault is a shared family/multi-user vault that has the tribu-routing convention installed in its CLAUDE.md. Detect this by:

1. Reading the vault's CLAUDE.md and looking for an H2 heading matching Family-member auto-routing (case-insensitive)
2. OR by recognizing the structure wiki/People/<N>/ with multiple member subfolders

If neither, this skill doesn't apply — push back with: "This skill is for shared family vaults using the tribu-routing convention. The current default vault (<name>) doesn't appear to use this pattern. If you want to install it, run /obsidian-router:conventions install tribu-routing."

Argument parsing from $ARGUMENTS

• bare member name or alias (Roland, roro, papa, karine, max, nico, …) → match against the vault CLAUDE.md table
• empty / "qui parle?" / "who is speaking?" → ASK the user explicitly: "Qui parle dans cette session ? (membres reconnus : Roland, Karine, Maxence, Nicolas, Amelie + leurs alias)". Wait for the answer before proceeding.

Always

1. Read the vault's CLAUDE.md to get the canonical members + alias table. Never hardcode the list — it's per-vault.
2. Match the user's input (case-insensitive) against the table. Both canonical names and aliases are valid. If match found, store the canonical name (e.g., roro → Roland).
3. No match → DON'T guess. Tell the user the list of recognized members and ask them to clarify. Refuse to proceed.
4. After successful match, in sequence:
   • Call mcp__obsidian-router__lock_vault({ vault: '<vault-name>' }) (use the slug of the current default family vault, typically tribu)
   • Call mcp__obsidian-router__set_auto_enrich_mode({ mode: 'Hybrid' })
   • Confirm to the user: "Identifié comme . Vault verrouillé sur <vault-slug>, mode auto-enrich Hybrid. Les saves auto routent vers wiki/People/<Canonical Name>/." (or EN equivalent if user is speaking EN)
5. For the rest of the session, treat the identified member as the active speaker. When auto-enrichment proposes saves (triggers 1/2/3 of the auto-enrichment consigne), prefix paths with wiki/People/<member>/. Items that are explicitly collective → wiki/Family/.
6. Medical sensitivity guard stays in force even in Hybrid mode. This skill switches the vault to Hybrid, which auto-saves type-safe items without asking. But per the tribu-routing convention, health/medical data (sleep, medications, diagnoses, symptoms) must NEVER be auto-saved without explicit user confirmation — the sensitivity filter overrides Hybrid's auto-save. When in doubt about whether an item is medical, ask before saving.