qteam

Resolves Obsidian wikilinks across federated vaults and manages task handoffs via the session-viz MCP server.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/QSchlegel/session-viz --skill qteam-qschlegel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qteam
Source: https://github.com/QSchlegel/session-viz/tree/main/plugins/session-viz/skills/qteam
Command: npx skills add https://github.com/QSchlegel/session-viz --skill qteam-qschlegel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working across multiple Obsidian vaults lose track of where concepts are documented, accumulate broken links after merges or renames, and hand off tasks without the context recipients need. This Skill connects to the hosted session-viz MCP server to resolve links across every vault in a workspace and manage a structured task handoff lifecycle. ## Core Features & Use Cases - Cross-vault link resolution: Register vault indexes (paths, titles, tags, link names only — never note bodies) and resolve any [[wikilink]] against every vault you can see, with ambiguous matches presented for the user to choose. - Dangling link detection: Find links that resolve nowhere after a merge or rename, reporting the count before the list. - Task handoff lifecycle: Create, offer, accept, and complete tasks with a strict draft → offered → accepted → done state machine, including guidance on writing a proper handoff brief. - Use Case: A developer finishing a debugging session offers the follow-up task to a colleague with a brief covering what was attempted, what was ruled out, the exact repo and branch, and what done looks like. ## Quick Start Ask the assistant to resolve a wikilink across all registered vaults or to hand off a task to a teammate using the qteam skill.

Frequently Asked Questions about qteam

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve an Obsidian wikilink across multiple vaults?▼

Use the vault_resolve tool after registering each vault with vault_register. It returns all matching candidates across every vault in the workspace with an obsidian:// URI each, and ambiguous matches are shown for the user to pick rather than chosen automatically.

How do I hand off a task to a teammate with context?▼

Create the task with task_create, then offer it with task_offer naming the recipient. Include a brief covering what was attempted, what was ruled out with evidence, the exact repo and branch, and what done looks like. The task becomes theirs only when they accept it.

Why are the mcp__session-viz__ tools not appearing?▼

The tools are absent when the MCP server is not connected. Exporting SESSION_VIZ_TOKEN does not help because the connection authenticates over OAuth and the shipped .mcp.json entry carries no env block. The browser sign-in flow is implemented but not yet verified end to end against the public host.

Does vault registration upload my note contents to the cloud?▼

No. vault_register sends only paths, titles, tags, and outbound link names. Note bodies must never be sent; the server has a column for them that stays null, preserving the local-first design.

Can a shared vault be hidden from teammates in the workspace?▼

No. The shared flag is stored but not consulted during resolution, so registering a vault with shared: false does not hide its note titles and paths from colleagues in the same workspace. Federation only stops at the workspace boundary.

Why does re-offering an already-offered task fail?▼

The task state machine only allows draft to offered to accepted to done, and task_offer on an already-offered task returns an illegal transition error. To redirect an offer, the task must be withdrawn to draft via a REST route the MCP tools do not expose.