How do I install the Dialogue Log Observation skill?

Run npx skillmds add majiayu000/dialogue-log-observation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dialogue Log Observation safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dialogue Log Observation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dialogue Log Observation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dialogue Log Observation?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dialogue Log Observation by majiayu000

Name: Dialogue Log Observation
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

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".

majiayu000 ee732ef 2 files · 3.5 KB Updated Sep 9, 2026 567 repo stars

File contents

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

---name: dialogue-log-observationdescription: 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".--- # 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: ```bash ${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 ```bash ${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 ```bash ${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 ```bash ${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. ```bash git add .dialogue/logs/observations/ && git commit -m "OBS-YYYYMMDD-HHMMSS: <subject>" && git push ```

Frequently asked questions