agentleFS
tboome33tboome33/obsidian-mcp-router/skills/who-is-speaking/SKILL.md

who-is-speaking

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Identify the family member speaking in a shared family vault (e.g., `vault_tribu`), then lock the router to that vault + set auto-enrich mode to `Hybrid` so subsequent auto-saves route to `wiki/People/<member>/`. Companion skill for the `tribu-routing` convention.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If neither, this skill doesn't apply — push back with: *"This skill is for shared family vaults using the tribu-routing convention.

    line 33
  2. Very specific:

    Call mcp__obsidian-router__lock_vault({ vault: '<vault-name>' }) (use the slug of the current default family vault, typically tribu)

    line 46
  3. Distinctive:

    If the user later says *"c'est <autre>"* / *"this is <other> speaking now"* / *"switch to <other>"*, re-trigger the skill with the new name.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 <Canonical Name>. 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.

Re-identification mid-session

If the user later says "c'est <autre>" / "this is <other> speaking now" / "switch to <other>", re-trigger the skill with the new name. Don't keep the previous identity. Don't unlock the vault unless the user explicitly asks — just switch the active member.

Push back if

  • The named member isn't in the vault's CLAUDE.md table → push back with the canonical list + offer to add the new member (via editing CLAUDE.md + creating wiki/People/<Name>/README.md).
  • The current default vault doesn't have the tribu-routing convention → push back with the installation hint.
  • The user tries to lock to a different vault simultaneously → ask which vault is the family vault first. The lock target is the FAMILY vault, not whatever else they have open.

Anti-patterns

  • ❌ Guessing the member based on chat history clues (greeting style, topic) instead of asking
  • ❌ Defaulting to "Roland" when uncertain
  • ❌ Failing silently when no match (must surface the canonical list + refuse to save)
  • ❌ Re-asking identity on every turn — once identified, it's stable for the session
  • ❌ Routing all saves to wiki/People/<member>/ blindly — collective items go to wiki/Family/, judgment call

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.