Observe

Normalize recurring workflow observations into structured JSONL learning records.

1|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/softwaresalt/csv-managed --skill observe-softwaresalt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Observe
Source: https://github.com/softwaresalt/csv-managed/tree/main/.github/skills/observe
Command: npx skills add https://github.com/softwaresalt/csv-managed --skill observe-softwaresalt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It captures and normalizes recurring agent or workflow observations into durable records, so repeated lessons can be clustered and reused rather than re-discovered.

Core Features & Use Cases

  • Normalized observation capture: Records timestamp, source, recurring pattern summary, evidence references, and affected workflow phase/artifact type.
  • Safety-conscious evidence handling: Strips secrets, large payloads, raw credentials, and noise while preserving concise citations or artifact references.
  • Supports multiple capture contexts: Works whether the signal comes from a hook, manual review, runtime verification, closure, or memory, with a fallback to manual capture when hooks are unavailable.

Quick Start

Ask the skill to record a normalized observation of a recurring workflow workaround, including a short reason it matters and any supporting evidence paths or citations.

Frequently Asked Questions about Observe

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

FAQPage Schema
How do I capture recurring workflow observations into structured JSONL records?

Capturing recurring workflow observations into structured JSONL records requires normalizing the agent behavior into a schema with timestamps, source, pattern summaries, and evidence references, then appending it to a date-partitioned file under .autoharness/continuous-learning/observations.

What is the best way to stop repeated workarounds from re-occurring in agent runs?

Stopping repeated workarounds in agent runs involves turning recurring workflow lessons into durable, searchable learning records. By capturing and normalizing these observations, repeated mistakes are clustered and reused rather than re-discovered across planning, build, review, verification, and closure scenarios.

How does evidence normalization handle secrets and large payloads during observation capture?

Evidence normalization during observation capture strips secrets, large payloads, raw credentials, and noise from the data. This safety-conscious process preserves concise citations and artifact references, ensuring secure evidence handling while maintaining useful workflow context.

Can I manually capture workflow observations if automated hooks are unavailable?

Manual capture of workflow observations is fully supported when automated hooks are unavailable. The system works across multiple capture contexts including manual review, runtime verification, closure, and memory, falling back to manual entry to ensure recurring patterns are still recorded.

When do I need continuous learning records for agent behavior?

Continuous learning records for agent behavior are needed when the same workaround or practice keeps repeating across multiple runs. They prevent repeated mistakes by turning these recurring workflow patterns into structured, searchable, and reusable instincts for future sessions.

Does observation capture work across different workflow phases like planning and review?

Observation capture works across multiple workflow phases including planning, build, review, verification, and closure. It normalizes signals from various contexts into a structured schema, ensuring recurring agent behaviors are consistently recorded regardless of the workflow phase.