Agent skill
dialogue-log-observation
Log an observation (measurement, state, or event). Use when recording factual observations during work execution. Triggers on "log observation", "record observation", "note finding", "capture state".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/dialogue-log-observation
SKILL.md
Dialogue: Observation Logger
Log an observation to the observation log.
When to Use
Use this skill when you need to record:
- A measurement (quantitative data)
- A state observation (system/process state)
- An event (something that occurred)
How to Log an Observation
Execute the following bash command:
${CLAUDE_PLUGIN_ROOT}/skills/dialogue-log-observation/scripts/log-observation.sh <type> <observer> <subject> <value> [context] [tags]
Required Parameters
| Parameter | Values | Description |
|---|---|---|
type |
MEASUREMENT, STATE, or EVENT |
Category of observation |
observer |
ai:claude or human:<id> |
Who made the observation |
subject |
text | Brief description of what was observed |
value |
text | The observed data, state, or event details |
Optional Parameters
| Parameter | Description |
|---|---|
context |
Additional surrounding situation |
tags |
Comma-separated categorisation tags |
Observation Types
| Type | Use For | Example |
|---|---|---|
MEASUREMENT |
Quantitative data | "3 tests failed, 47 passed" |
STATE |
System/process state | "Build pipeline is broken" |
EVENT |
Occurrences | "User requested code review" |
Examples
Measurement Observation
${CLAUDE_PLUGIN_ROOT}/skills/dialogue-log-observation/scripts/log-observation.sh MEASUREMENT "ai:claude" "Test results" "3 failed, 47 passed" "After applying fix to auth module" "testing,ci"
State Observation
${CLAUDE_PLUGIN_ROOT}/skills/dialogue-log-observation/scripts/log-observation.sh STATE "ai:claude" "Build status" "Pipeline failing on lint stage" "Since commit abc123" "ci,blocking"
Event Observation
${CLAUDE_PLUGIN_ROOT}/skills/dialogue-log-observation/scripts/log-observation.sh EVENT "ai:claude" "User action" "Requested implementation of feature X" "During planning session" "requirements"
Output
The script returns the generated observation ID (e.g., OBS-20260113-143000).
Sharing
Always commit and push immediately after logging an observation. This ensures team visibility and supports transactive memory—others need to see observations promptly to maintain shared situational awareness.
git add .dialogue/logs/observations/ && git commit -m "OBS-YYYYMMDD-HHMMSS: <subject>" && git push
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?