ob

Capture session decisions into architecture and configuration markdown files.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill ob-aesopscott
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ob
Source: https://github.com/AesopScott/mojo/tree/main/skills/ob
Command: npx skills add https://github.com/AesopScott/mojo --skill ob-aesopscott

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of losing critical architectural decisions and configuration settings that occur during ephemeral AI chat sessions by formalizing them into a persistent Obsidian knowledge base.

Core Features & Use Cases

  • Durable Documentation: Automatically categorizes and writes session-based decisions into architecture or configuration folders.
  • Context Awareness: Resolves project-specific paths using foundation preferences or project-foundation files to ensure notes are saved in the correct location.
  • Use Case: After finalizing a new API integration strategy or updating a system path during a coding session, use this skill to instantly generate a structured, timestamped note in your project's architecture folder.

Quick Start

Use the ob skill to capture the architectural decisions and configuration changes we just discussed in this session.

Frequently Asked Questions about ob

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

FAQPage Schema
How do I save architectural decisions from AI chat sessions into Obsidian?

To save architectural decisions into Obsidian, this Skill captures ephemeral session insights and writes them as durable, timestamped markdown notes. It automatically categorizes technical content into standardized architecture or configuration folders.

What is the best way to document project configuration changes automatically?

Documenting project configuration changes automatically requires resolving project-specific paths via foundation files. This Skill classifies technical content and generates structured markdown files within your project's designated configuration documentation folders.

Can I use this to organize session knowledge without manually copying markdown files?

Yes, you can organize session knowledge without manual copying by using this Skill to identify project memory contracts. It automatically extracts decisions from your current context and places them directly into the correct Obsidian project structure.

Do I need project-foundation files to generate architecture documentation with this tool?

Yes, project-foundation files or user-defined paths are required to generate accurate architecture documentation. The Skill relies on these inputs to resolve project-specific locations and ensure technical notes are saved correctly.

Why does my architecture note get saved to the wrong project folder?

Architecture notes may save to the wrong folder if project-foundation files or user-defined paths are missing or misconfigured. The Skill needs accurate path resolution to properly categorize and place technical documentation within the Obsidian structure.