Run any Skill in Manus with one click

Get Started

runtime-state-reader

Stars38

Forks14

UpdatedJune 3, 2026 at 03:50

Safe read-only navigation of pi-crew run state.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

baphuongna

baphuongna/pi-crew

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	runtime-state-reader
description	Safe read-only navigation of pi-crew run state.
origin	pi-crew
triggers	["inspect manifest","read tasks","trace events","examine state","diagnostics"]

runtime-state-reader

Use this skill when debugging or auditing a pi-crew run.

Source patterns distilled

src/state/types.ts, src/state/contracts.ts, src/state/state-store.ts
src/state/event-log.ts, src/state/artifact-store.ts, src/runtime/crew-agent-records.ts
src/extension/run-index.ts, src/extension/team-tool/status.ts, src/extension/team-tool/inspect.ts

Rules

Prefer exported state APIs over direct file parsing: loadRunManifestById(cwd, runId), run index/list helpers, event readers, and agent readers.
Treat state as append-mostly/durable. For review and debugging, do not mutate manifests/tasks/events.
Validate run IDs and path-derived IDs; never concatenate untrusted path segments outside state helpers.
Read events as JSONL; expect partial/corrupt trailing lines in crash scenarios and handle gracefully.
Check status contracts before inferring behavior: terminal vs active run/task statuses matter.
Agent aggregate records (agents.json) and per-agent status files can disagree briefly; prefer the latest loaded run state plus event log for final conclusions.
Include exact paths inspected and distinguish direct evidence from inference.

Common inspection order

Load manifest/tasks.
Check run/task statuses and timestamps.
Read recent events.
Read agent records and per-agent output/status if needed.
Inspect artifacts/diagnostics only through contained paths.
Report root cause and smallest safe remediation.

Enforcement — Runtime State Reader Gate

Before inspecting or reporting on run state, verify:

Using exported state APIs (not direct file parsing where helpers exist)
State treated as append-mostly (no mutations during review/debugging)
runId validated before use (no untrusted path concatenation)
Corrupt JSONL handled gracefully (skip malformed lines)
Terminal vs active statuses distinguished (critical for conclusions)
Exact paths inspected reported with direct evidence vs inference labeled

If ANY answer is NO → Stop. Verify state access method before proceeding.

Verification

For code changes to state readers:

cd pi-crew
npx tsc --noEmit
node --experimental-strip-types --test test/unit/run-index.test.ts test/unit/crew-contracts.test.ts test/unit/atomic-write.test.ts
npm test

More from this repository

same repository

iterative-audit

baphuongna/pi-crew

Iterative multi-round codebase audit with diminishing-returns detection. Run 5-20+ rounds, each focusing on one specific area. Built from 19 rounds of dogfooding pi-crew on itself.

2026-06-3038

widget-rendering

baphuongna/pi-crew

Pi TUI crew widget data sources, display priority, and rendering performance.

2026-06-3038

orchestration

baphuongna/pi-crew

Multi-phase orchestration for planners and executors.

2026-06-2238

council

baphuongna/pi-crew

Spawn 3 adversarial subagents (Skeptic, Pragmatist, Critic) to evaluate a decision, architecture choice, or plan. Anti-anchoring: each role receives ONLY the question, not conversation history. Aggregates votes into consensus recommendation with dissent tracking. Use when facing critical decisions, architecture choices, security tradeoffs, or plan reviews where single-perspective analysis is insufficient.

2026-06-0438

async-worker-recovery

baphuongna/pi-crew

Background worker, heartbeat, stale-run, crash-recovery, and deadletter workflow. Use when debugging stuck/dead workers or changing async run reliability.

2026-06-0338

child-pi-spawning

baphuongna/pi-crew

Child Pi worker spawning, lifecycle callbacks, and failure modes.

2026-06-0338

runtime-state-reader

Use this skill when debugging or auditing a pi-crew run.

Source patterns distilled

src/state/types.ts, src/state/contracts.ts, src/state/state-store.ts

src/state/event-log.ts, src/state/artifact-store.ts, src/runtime/crew-agent-records.ts

src/extension/run-index.ts, src/extension/team-tool/status.ts, src/extension/team-tool/inspect.ts

Rules

Prefer exported state APIs over direct file parsing: loadRunManifestById(cwd, runId), run index/list helpers, event readers, and agent readers.

Treat state as append-mostly/durable. For review and debugging, do not mutate manifests/tasks/events.

Validate run IDs and path-derived IDs; never concatenate untrusted path segments outside state helpers.

Read events as JSONL; expect partial/corrupt trailing lines in crash scenarios and handle gracefully.

Check status contracts before inferring behavior: terminal vs active run/task statuses matter.

Agent aggregate records (agents.json) and per-agent status files can disagree briefly; prefer the latest loaded run state plus event log for final conclusions.

Include exact paths inspected and distinguish direct evidence from inference.

Common inspection order

Load manifest/tasks.

Check run/task statuses and timestamps.

Read recent events.

Read agent records and per-agent output/status if needed.

Inspect artifacts/diagnostics only through contained paths.

Report root cause and smallest safe remediation.

Enforcement — Runtime State Reader Gate

Before inspecting or reporting on run state, verify:

Using exported state APIs (not direct file parsing where helpers exist)

State treated as append-mostly (no mutations during review/debugging)

runId validated before use (no untrusted path concatenation)

Corrupt JSONL handled gracefully (skip malformed lines)

Terminal vs active statuses distinguished (critical for conclusions)

Exact paths inspected reported with direct evidence vs inference labeled

If ANY answer is NO → Stop. Verify state access method before proceeding.

Verification

For code changes to state readers:

cd pi-crew npx tsc --noEmit node --experimental-strip-types --test test/unit/run-index.test.ts test/unit/crew-contracts.test.ts test/unit/atomic-write.test.ts npm test