TGPSKI

Flow Indicator — Development skill for Claude Code

Development community

Local meter for when cheap agent steering gives way to repeated correction, constraint restatement, repair, and operator serialization.

How to install Flow Indicator

This entry records only its repository, not the path inside it, so there is no exact command to give. Open TGPSKI/flow-indicator and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Flow Indicator does

Local meter for when cheap agent steering gives way to repeated correction, constraint restatement, repair, and operator serialization.

Alternatives in Development

  • Correction Handler — Correction 处理 Prompt 24k ★
  • Fidelity — Measure how faithfully a clone reproduces a site — pixel-diff plus motion-fidelity into one 0-100 score, a let 3.6k ★
  • Dao Code — Open-source TypeScript terminal coding agent for DeepSeek-V4 — builds on DeepSeek's strong price-performance a 1.3k ★

README

flow-indicator

[pate.sh](https://pate.sh) | [provenance](https://tgp.ski) | [commands](docs/COMMANDS.md) | [herdr](docs/HERDR.md) | [integrations](docs/INTEGRATIONS.md) | [profiles](docs/PROFILES.md) | [inference](docs/INFERENCE.md) | [calibration](docs/CALIBRATION.md) | [events](docs/EVENTS.md) | [metrics](docs/METRICS.md)

A local meter for when cheap agent steering gives way to repeated correction, constraint restatement, repair, and operator serialization.

It answers one question about an interaction stream:

Is the operator advancing the work, or spending increasing effort keeping the agent aligned with work already established?

Stdlib-only Go, one binary.

What it reads

An ordered stream of interaction records, through a harness:

harness input
claude-code a Claude Code session file, ~/.claude/projects//.jsonl
codex a Codex rollout, ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl
opencode a session in opencode's SQLite store, #
qwen a Qwen Code session file, ~/.qwen/projects//chats/.jsonl
generic JSONL with at least stream_id, seq, speaker, text

Each harness owns every field name of its own format. No other package reads them. Replay and the live meter take the same names, so anything that can be replayed can be watched.

What it writes

Per stream, under `$XDG_DATA_HOME/flow-indicator/sessions//`:

file role
observations.jsonl append-only, observed events
classifications.jsonl append-only, classifier candidates
obligations.jsonl append-only, obligation transitions
repairs.jsonl append-only, repair episode transitions
metrics.jsonl append-only, derived metrics, regime and epoch changes
source.json source path, byte offset, record count
summary.json, metrics.json, report.md, timeline.csv projections, rebuilt from the events above

Th