obsidian-meeting-router

Routing Obsidian meeting notes automatically requires a skill that detects whether a file is a standup or general meeting based on its filename, then delegates to specialized processing skills. It uses a filename-based detection heuristic to determine the correct routing path.

Filename-based meeting detection works by applying a heuristic to the provided file path to identify if the meeting is a standup or a general meeting. It checks the filename string and then delegates the processing request to the appropriate specialized skill.

Automatic routing triggers when you issue commands like "process meeting," "process obsidian meeting," or "process the meeting" alongside a file path. The router skill intercepts these requests and delegates them without requiring user intervention.

Yes, the meeting router relies on specialized skills like obsidian-meeting-standup and obsidian-meeting-general to function. The router itself does not execute meeting processing but delegates the task to these dependent skills for final execution.

No, you cannot use this routing skill without a filename because it relies on a filename-based detection heuristic to determine the meeting type. You must provide a meeting file path or date reference for the router to correctly identify and delegate the task.