observer

Analyze session transcripts to model user workflow patterns and decision branches.

40|6|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/magnus919/agent-skills --skill observer-magnus919
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observer
Source: https://github.com/magnus919/agent-skills/tree/main/bundles/workflow-architect/skills/observer
Command: npx skills add https://github.com/magnus919/agent-skills --skill observer-magnus919

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of manual workflow documentation by silently observing user sessions to infer and catalog processes without interrupting the flow of work.

Core Features & Use Cases

  • Passive Inference: Automatically scans session history to identify entry patterns, phases, and branching logic.
  • Pattern Recognition: Detects pain points and tool usage to build a structured workflow state model.
  • Use Case: A developer wants to document their debugging process; they load this skill in passive mode, work normally, and later ask the agent to catalog the workflow based on the session history.

Quick Start

Load the observer skill in passive mode and then ask the agent to catalog your workflow after completing a task.

Frequently Asked Questions about observer

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

FAQPage Schema
How do I automatically document workflow patterns from session history?

Passive workflow inference observes your session transcripts and message history to automatically identify entry patterns, phases, and branching logic. It builds a structured workflow state model by detecting pain points and tool usage without requiring manual documentation input.

Can I detect cross-session workflow patterns automatically?

Cross-session pattern detection requires access to session search and context scanning capabilities. The skill analyzes session transcripts and message history to extract entry points, decision branches, and tool usage across multiple sessions for process documentation.

What is passive workflow discovery and how does it work?

Passive workflow discovery silently observes user sessions to infer and catalog processes without interrupting work. It operates within the workflow-architect framework to extract entry points, decision branches, and tool usage for process documentation.

Do I need session search capabilities to infer workflow state models?

Yes, session search and context scanning capabilities are required to perform cross-session pattern detection and build workflow state models. The skill analyzes session transcripts and message history to infer user workflow patterns.

What's the best way to document a debugging process without manual overhead?

Load a passive workflow inference skill, work normally through your debugging process, and then ask the agent to catalog the workflow from session history. This avoids manual documentation overhead by silently observing and inferring process patterns.

Are there limitations to passive workflow inference for process documentation?

Passive workflow inference is limited by its dependency on session search and context scanning capabilities. Without these, cross-session pattern detection cannot occur, and the skill cannot extract entry points or decision branches for workflow state modeling.