skill-observe
The skill-observe tool records lightweight usage evidence for skills in the Mnemon system when a turn produces reusable workflow signals or lifecycle data. Use it after the HostAgent determines that evidence recording is warranted according to GUIDE.md guidelines. It appends JSON objects to a usage log file with fields like timestamp, skill identifier, event type, outcome, and source, enabling later analysis of skill effectiveness and reusability without modifying the skills themselves.
git clone --depth 1 https://github.com/mnemon-dev/mnemon /tmp/skill-observe && cp -r /tmp/skill-observe/harness/loops/skill/skills/skill-observe ~/.claude/skills/skill-observeSKILL.md
# skill-observe
Use this skill only after the HostAgent has decided, according to `GUIDE.md`,
that skill evidence should be recorded.
## Boundary
This skill records evidence only. It does not create, patch, move, archive, or
restore skills.
Resolve the usage log as:
```text
$MNEMON_SKILL_LOOP_USAGE_FILE
```
If the variable is unavailable, use the path injected by Prime. Do not guess a
host-specific default.
## Procedure
1. Identify the smallest evidence item worth keeping.
2. Append one JSON object per line to `$MNEMON_SKILL_LOOP_USAGE_FILE`.
3. Use these fields when available:
- `time`: ISO-8601 timestamp
- `skill`: skill id, or `null` for missing-skill evidence
- `event`: `used`, `helped`, `missing`, `misleading`, `outdated`, `duplicate`, `workflow`, `feedback`, or `patched`
- `outcome`: `positive`, `negative`, `neutral`, or `unknown`
- `note`: short evidence note
- `source`: `user`, `agent`, `repo`, or `manual`
4. Use `source: "user"` only for explicit user feedback or user-requested
lifecycle evidence. Use `source: "agent"` when the agent infers reusable
workflow evidence from its own turn.
5. Keep notes short and avoid raw conversation excerpts.
6. If evidence is sensitive or uncertain, skip it or record a sanitized note.
## Example
```json
{"time":"2026-05-14T10:00:00Z","skill":"release-checklist","event":"helped","outcome":"positive","note":"Reusable release verification checklist matched the current task.","source":"agent"}
```
## Safety
Never store secrets. Evidence is input for later review, not authority.Analyze Mnemon harness eval reports, classify outcomes, and extract improvement evidence.
Turn stable Mnemon harness eval findings into scoped project, loop, adapter, docs, or eval asset improvements.
Design a scenario-driven Mnemon harness eval with target, hypothesis, HostAgent, loop configuration, evidence, and rubric.
Execute or supervise a planned Mnemon harness eval run in an isolated HostAgent workspace.
Manage project-scoped Mnemon goal state, evidence, verification, completion, blockers, and host goal links.
Recall long-term memory from Mnemon when GUIDE.md indicates that prior memory may help the current task.
Maintain prompt-facing working memory by editing MEMORY.md when GUIDE.md indicates that durable information should be kept.
Draft or revise high-quality SKILL.md content for approved or proposed Mnemon skill changes.