Skip to content
Back to skills

Observe

ASecurity

Measure cost and context before justifying any harness change (P7). Read /context, /cost, /status and the tool-failure log to get before/after numbers; roll back anything that worsens a metric. Use when adding tools, evaluating a phase, or diagnosing quota burn.

  • 28 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 7, 2026
ai-agentsgit

Security analysis

A100/100

Scanned September 7, 2026

npx -y skills add move-hoon/claude-pro-minmax --skill observe --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Observe?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Observe
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/move-hoon-observe/badge)](https://www.skillsdirectory.com/skills/move-hoon-observe)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: observe
description: Measure cost and context before justifying any harness change (P7). Read /context, /cost, /status and the tool-failure log to get before/after numbers; roll back anything that worsens a metric. Use when adding tools, evaluating a phase, or diagnosing quota burn.
---

# Observe Skill (P7 — peak KPI = verified results / quota)

## Purpose
No addition is justified by intuition. Every tool, skill, or hook must pay for itself in a measured metric; if a change worsens a number, revert it (P7).

## Metrics to capture
| Metric | Source |
|---|---|
| Files read / task | session transcript count |
| Output tokens | `/cost` |
| Peak context fill % | `/context` |
| Message count | `/cost`, `/status` |
| Turn count | session |
| Retry rate | tool-failure log |
| Failure blast radius | files touched per failed change |

## Workflow (per phase / per addition)
1. **Baseline** — record metrics on a fixed sample task *before* the change.
2. **Change** — apply one thing (a tool, a skill, a hook).
3. **After** — re-run the same sample task, record metrics.
4. **Gate** — any single metric regresses → roll back the change (git boundary).

## Inputs
- `/context` — token budget + peak fill.
- `/cost`, `/status` — messages, output tokens.
- `scripts/hooks/tool-failure-log.sh` output — retries, failure patterns.

## Rule
One change at a time, measured. Bundled changes hide which one regressed. Keep a short before/after note in `HANDOFF.md` (P5), not auto-injected.

## Measured escalations (don't adopt by default)
Default memory is file-based (`HANDOFF.md` + `.serena/memories`). Only if a metric shows it's insufficient: **claude-mem** (auto session memory) — watch for auto-injection noise. Adopt via the before/after gate above, never preemptively (ADR-010/P7).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.