aget-capture-observation

Capture research observations into the AGET knowledge base with ISO 8601 timestamps.

1|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-capture-observation-gmelli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aget-capture-observation
Source: https://github.com/gmelli/public-OpenAI-DeepResearch-aget/tree/main/.claude/skills/aget-capture-observation
Command: npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-capture-observation-gmelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill preserves transient research signals generated during active sessions by capturing vocabulary candidates, research questions, web findings, patterns, and general observations into the AGET knowledge base so they are not lost or prematurely committed to formal specifications.

Core Features & Use Cases

  • Autonomous scanning: When invoked without arguments, scan the recent session and surface the top 3-5 valuable signals prioritized by novelty and governance value.
  • Time-budgeted depth: Support shallow-to-deep capture modes (2–30+ minutes) that scale classification, linking, and formalization effort to the allotted time.
  • Explicit capture & classification: Accept direct input signals (vocabulary, RQs, web findings, patterns, gaps) and append timestamped, typed entries to session files or a scratchpad while enforcing non-edit constraints on specs.
  • Governance-safe operation: Enforce INVIOLABLE constraints to prevent direct modification of specs, vocabulary files, or backlog artifacts and require ISO 8601 timestamps and source attribution for web findings.

Quick Start

Use the aget-capture-observation skill to append the highlighted finding about model behavior to the current session file as a classified observation.

Frequently Asked Questions about aget-capture-observation

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

FAQPage Schema
How do I capture research observations during an active session without editing formal specs?

To capture research observations safely, append timestamped, typed entries to session files or a scratchpad. This preserves transient signals like vocabulary candidates and web findings while enforcing constraints that prevent direct edits to formal specs or vocabulary files.

What is the best way to preserve transient research signals and vocabulary candidates before they are lost?

Preserving transient research signals involves classifying them by type and appending ISO 8601 timestamped entries to a knowledge base. This prevents premature commits to formal specifications and ensures valuable patterns or process gaps are retained for later review.

Can I automatically scan my research session to surface valuable web findings and patterns?

Yes, autonomous scanning can surface valuable web findings and patterns. When invoked without arguments, the system scans recent session history and prioritizes the top 3-5 signals based on novelty and governance value for immediate capture.

How do I record time-budgeted research observations when I have limited time for classification?

Time-budgeted capture modes scale classification and formalization effort to your allotted time. Shallow-to-deep modes ranging from 2 to 30+ minutes allow you to record research observations with appropriate linking and typing based on available time.

Does capturing web findings require source attribution and specific timestamp formats?

Yes, capturing web findings requires ISO 8601 timestamps and source attribution. These governance-safe constraints ensure that all web findings appended to session files or scratchpads maintain traceability and comply with knowledge base standards.

When should I not use a scratchpad for capturing research questions and process gaps?

You should not use a scratchpad if you intend to directly modify formal specs, vocabulary files, or backlog artifacts. The capture mechanism enforces inviolable constraints against direct edits, meaning scratchpads are strictly for preserving observations, not committing changes.