@quill-io/sensor-w2a-registry

A meta World2Agent sensor — emits a package.sensor.published signal whenever a new W2A sensor package (or any package matching a configurable npm keyword) is published or version-bumped on npm.

The pitch: if you're building in the W2A ecosystem, you probably want to know the moment someone else ships a sensor — for collaboration, for "we don't need to build that ourselves", or for competitive radar. Polling npm search keywords:w2a-sensor once an hour is cheap; this sensor turns it into a push channel.

Signal: package.sensor.published

| Field | What's in it | |---|---| | event.summary (new package) | 🆕 <name>@<version> — new W2A sensor by <publisher> · <date> — <description> | | event.summary (version bump) | ⬆ <name> <prev> → <new> by <publisher> · <date> — <description> | | source_event.data | keyword, package_name, scope, version, is_new_package, previous_version?, publisher, description?, keywords?, homepage?, repository?, npm_url, published_at | | attachments | description (inline), npm page (reference), source repo (reference, when set) |

The is_new_package boolean is the discriminator that lets the handler treat a brand-new sensor (interesting!) differently from a version bump on an existing one (incremental).

Configuration

| Parameter | Type | Default | Description | |---|---|---|---| | keyword | string | "w2a-sensor" | npm keyword to watch. Set to any other npm keyword to repurpose the sensor (e.g. mcp-server, claude-code-plugin). | | interval_seconds | number | 3600 | Poll interval. npm publishes are infrequent; faster polling rarely helps. | | page_size | number | 250 | Search result page size (npm caps at 250). | | cold_start_emit_latest | boolean | true | On first poll, emit one signal for the most-recently-published package as a "current state" snapshot. Set false to start completely silent. |

Install

In a Claude Code session with the @world2agent/claude-code-channel plugin installed:

/world2agent:sensor-add @quill-io/sensor-w2a-registry

The install flow reads SETUP.md, runs a 3-question Q&A (which keyword, polling interval, user context), writes the sensor entry to ~/.world2agent/config.json, and writes a per-user handler skill into your agent runtime's skills directory.

Notes

• npm's keyword index sometimes lags publishes by minutes-to-hours. Don't expect zero-second latency.
• Some packages tagged w2a-sensor may not appear under exact-keyword search if npm's tokenizer split the keyword differently — broaden to keywords:w2a if you want everything.
• This sensor itself appears under keywords:w2a-sensor, so on cold-start with cold_start_emit_latest: true you'll see a signal for one of the W2A sensors (possibly your own) — the handler skill should classify self differently from third-party.

License

MIT