Pilot Event Replay

Record and replay event streams for debugging, testing, and audit purposes. Use this skill when: 1. You need to capture event streams for later analysis 2. Y...

Security Scan

The skill's requirements and runtime instructions match its stated purpose (recording and replaying Pilot protocol events); nothing requested is disproportionate, but replaying events can accidentally affect production or leak sensitive event data so exercise operational caution.

Purpose & Capability

Name/description ask for recording and replaying event streams and the SKILL.md only requires pilotctl and jq and a running daemon — these are exactly what a Pilot-protocol replay tool would need.

Instruction Scope

Runtime instructions are narrowly scoped to pilotctl and jq, using NDJSON files and simple shell loops. However the instructions allow publishing to arbitrary target-hostnames (which could be production systems) and thus carry operational risk (accidental replays, data leakage). Also the shell usage relies on proper quoting of event data (possible issues if event payloads contain newlines or special characters) — this is an operational safety concern, not an incoherence in purpose.

Install Mechanism

No install spec (instruction-only). That minimizes installer risk; the skill expects binaries to already be on PATH (pilotctl, jq).

Credentials

No environment variables, credentials, or config paths are requested. The lack of secrets is proportional to the stated functionality.

Persistence & Privilege

always is false and the skill does not request elevated or persistent platform privileges. Autonomous invocation is allowed by default but is not combined with other risky requests.

Assessment

This skill appears coherent for recording and replaying Pilot-protocol events, but before using/installing consider: 1) Ensure pilotctl is a trusted binary and the pilot daemon you connect to is authorized; 2) Never replay recordings to production hosts unless you intend to — use isolated test targets to avoid triggering downstream side effects; 3) Sanitize or redact recordings that contain sensitive data before storing or sharing; 4) Be careful with shell quoting when event payloads may include newlines or special characters — consider using safer publish APIs or tooling that handle binary/complex JSON payloads; 5) Confirm you have the companion pilot-protocol skill and that your operational policy allows capturing and re-publishing events (audit/privacy/legal considerations). If you need the skill to install binaries automatically or to restrict targets, request a version that includes explicit safety checks and install provenance.

Record event streams to NDJSON files and replay them for debugging and testing.

Commands

Record events to file

pilotctl --json subscribe <source-hostname> <topic> --timeout <seconds> | \
  jq -c '.data.events[]' >> <recording-file.ndjson>

Replay events from file

cat <recording-file.ndjson> | jq -c '.' | while IFS= read -r event; do
  topic=$(echo "$event" | jq -r '.topic')
  data=$(echo "$event" | jq -r '.data')

  pilotctl --json publish <target-hostname> "$topic" --data "$data"
  sleep <delay-seconds>
done

Workflow Example

Record debug session:

#!/bin/bash
SOURCE="buggy-worker"
DURATION=300
RECORDING="/tmp/debug-session-$(date +%Y%m%d-%H%M%S).ndjson"

pilotctl --json subscribe "$SOURCE" "*" --timeout "$DURATION" | \
  jq -c '.data.events[]' >> "$RECORDING"

event_count=$(wc -l < "$RECORDING")
echo "Recorded $event_count events"

Replay to test agent:

#!/bin/bash
RECORDING="$1"
TEST_TARGET="test-agent"

jq -c '.' "$RECORDING" | while IFS= read -r event; do
  topic=$(echo "$event" | jq -r '.topic')
  data=$(echo "$event" | jq -r '.data')

  pilotctl --json publish "$TEST_TARGET" "$topic" --data "$data"
  sleep 0.5
done

Dependencies

Requires pilot-protocol skill, jq, and a running daemon.