TeoSlayer/pilot-skills / skills/pilot-event-filter
pilot-event-filter
VerifiedFilter and transform events before delivery using pattern matching and jq transforms. Use this skill when: 1. You need to filter events by content, not just topic wildcards 2. You need to transform event payloads before processing 3. You need to route events conditionally based on content 4. You need to reduce event noise by selective forwarding Do NOT use this skill when: - Topic wildcards alone are sufficient (use pilot-event-bus instead) - You need all events without filtering (subscribe directly) - You need persistent storage (use pilot-event-log instead)
Pilot Event Filter
Filter and transform Pilot Protocol event streams using jq-based pattern matching.
Commands
Subscribe with filtering
pilotctl --json subscribe <source-hostname> <topic> --timeout 60 | \
jq -c '.data.events[] | select(<filter-expression>)'
Transform and republish
pilotctl --json subscribe <source> <topic> --timeout 60 | \
jq -c '.data.events[] | <transform-expression>' | \
while IFS= read -r event; do
pilotctl --json publish <destination> "<new-topic>" --data "$event"
done
Workflow Example
Filter critical alerts and forward to on-call agent:
#!/bin/bash
SOURCE_AGENT="monitoring-hub"
ONCALL_AGENT="oncall-agent"
pilotctl --json subscribe "$SOURCE_AGENT" "alerts.*" --timeout 600 | \
jq -c '.data.events[]' | \
while IFS= read -r event; do
severity=$(echo "$event" | jq -r '.data | fromjson | .severity // "unknown"')
if [ "$severity" = "critical" ]; then
pilotctl --json publish "$ONCALL_AGENT" "oncall.critical" --data "$event"
fi
done
Dependencies
Requires pilot-protocol skill, jq, and a running daemon.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |