obsidian-workflow

Coordinate multi-agent workflows by building relational memory graphs in Obsidian via MCP tools.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/jfriisj/coding-agents --skill obsidian-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-workflow
Source: https://github.com/jfriisj/coding-agents/tree/main/.github/skills/obsidian-workflow
Command: npx skills add https://github.com/jfriisj/coding-agents --skill obsidian-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Obsidian-based relational memory graphs enable multi-agent workflows to share context and make structured handoffs by linking artifacts without duplicating agent-output content.

Core Features & Use Cases

  • Relational memory graphs to connect agent context within Obsidian MCP
  • Structured handoffs with clear pointers and ownership across WF nodes
  • Artifact linking to tie agent outputs to notes without content duplication

Quick Start

Instruct your agents to build and link memory graphs in Obsidian using MCP tools, while avoiding duplication of artifact content.

Frequently Asked Questions about obsidian-workflow

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

FAQPage Schema
How do I coordinate multi-agent workflows using an Obsidian memory graph?

Coordinate multi-agent workflows in Obsidian by applying MCP tools to build a relational memory graph. This enables structured handoffs and artifact linking between agents without duplicating agent-output content.

What is a structured handoff in a multi-agent Obsidian workflow?

A structured handoff in multi-agent Obsidian workflows uses clear pointers and ownership across WF nodes to transfer relational context. It enforces deterministic WF IDs and 10-line contracts to orchestrate robust collaborations.

Can I link agent outputs to Obsidian notes without duplicating content?

Yes, you can link agent outputs to Obsidian notes without duplicating content by using artifact linking. This ties outputs to notes via a relational memory graph managed through MCP tools.

Do I need frontmatter metadata to orchestrate multi-agent workflows in Obsidian?

Yes, you need frontmatter-driven metadata to orchestrate robust multi-agent collaborations in Obsidian. It works alongside deterministic WF IDs and 10-line WF contracts to manage structured handoffs effectively.

How do I build a relational memory graph in Obsidian for agent context sharing?

Build a relational memory graph in Obsidian by instructing your agents to use MCP tools. This connects agent context by applying deterministic WF IDs and frontmatter-driven metadata for structured artifact linking.