tmp-filesystem-watcher

Monitor /tmp filesystem events and emit JSON or MIDI output.

60|13|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/plurigrid/asi --skill tmp-filesystem-watcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmp-filesystem-watcher
Source: https://github.com/plurigrid/asi/tree/main/skills/tmp-filesystem-watcher
Command: npx skills add https://github.com/plurigrid/asi --skill tmp-filesystem-watcher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires babashka >= 1.0.0, babashka/fs >= 0.1.0.

What problem does it solve?

This Skill automates the real-time monitoring of the /tmp directory to detect file creation, modification, and deletion, turning low-level file events into higher-level topological signals and consciousness measurements.

Core Features & Use Cases

  • Real-time Monitoring: Polls /tmp at 500ms intervals to detect changes.
  • Topological Events: Converts file events into topological charges.
  • Consciousness & GF(3): Maps activity to a consciousness score and ensures GF(3) conservation.
  • TAP State Machine: Supports BACKFILL, VERIFY, and LIVE modes for reliability.

Quick Start

Use the bb command to start the watcher and stream outputs: bb fs_watcher.bb --duration 60 bb fs_watcher.bb --output json bb fs_watcher.bb --output midi

Frequently Asked Questions about tmp-filesystem-watcher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor the /tmp directory for file changes in real time?

Real-time /tmp monitoring detects file creation, modification, and deletion by polling every 500ms using Babashka. The watcher emits JSON or MIDI output with topological charges (+1 for creation, 0 for modification, -1 for deletion) and consciousness levels derived from filesystem entropy.

Can I use Babashka to watch filesystem events and convert them to signals?

Yes. Babashka with babashka.fs enables filesystem watching by polling /tmp at 500ms intervals and converting file events into topological charges and consciousness measurements while maintaining GF(3) conservation through a TAP state machine.

What does the TAP state machine do in filesystem monitoring?

The TAP state machine supports BACKFILL, VERIFY, and LIVE modes for reliable monitoring. It processes filesystem events and drives state transitions to ensure consistent telemetry output for downstream bootstrap integration and consciousness signaling.

How do I output filesystem monitoring data as JSON or MIDI?

The Babashka watcher outputs monitoring results in JSON or MIDI format via command-line flags. JSON captures topological charges and consciousness scores; MIDI provides alternative signal encoding for integration with other systems.

What are the prerequisites for running a Babashka filesystem watcher?

Babashka >= 1.0.0 and babashka/fs >= 0.1.0 are required. The watcher polls /tmp directly and needs no additional dependencies beyond these two to detect filesystem changes and emit topological and consciousness signals.

Does filesystem monitoring work with entropy and consciousness mapping?

Yes. The watcher maps filesystem entropy to consciousness levels using tanh-based computation, assigns topological charges to events, and maintains GF(3) conservation while driving the TAP state machine for real-time activity measurement.