npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@agentworkforce/persona-slack-relayfile-doctor

v0.1.2

Published

AgentWorkforce slack-relayfile-doctor persona pack — a debugging specialist for the Slack ↔ relayfile ↔ cloud sync/writeback stack. Localizes a symptom to the right layer, confirms root cause with concrete evidence (mount state, the ops API, logs), and pr

Readme

@agentworkforce/persona-slack-relayfile-doctor

A debugging-specialist AgentWorkforce persona for the Slack ↔ relayfile ↔ cloud sync/writeback stack. Where persona-slack-comms is comms-only, this persona is the engineer for the integration pipeline: it localizes a symptom to the right layer, confirms the root cause with concrete evidence, and prescribes the fix to the owning repo.

When to use it

Spin up slack-relayfile-doctor when an integration regression appears:

  • Inbound Slack messages stop reading down to disk (channel, thread, or DM).
  • An <integration-event> preview says Message: unavailable though the bytes may be on disk.
  • An outbound writeback (channel post, thread reply, or DM) silently doesn't deliver — no error, no dead-letter.
  • A mount wedges (context deadline exceeded, zero completed cycles).
  • Duplicate posts, or any "it worked yesterday" sync/writeback regression.

What it knows

The persona's playbook (personas/slack-relayfile-doctor.md) encodes:

  • Topology — the five layers (Slack → Nango → cloud TS worker → relayfile-mount daemon → local mount → pear) and which repo owns each.
  • Diagnostic toolkit — reading mount.log/state.json, the relayfile ops API recipe (GET …/ops/<opId>, with the required X-Correlation-Id) to read a writeback's lastError, the event-injection log, and which wrangler tail worker actually carries the error.
  • Symptom → root cause → fix decision trees — write-only-vs-mirror mounts, bare-vs-suffixed channel ids, the preview two-shape gap, mount wedges, the missing_scope/im:write 3-place fix, duplicate dispatch, and silent-send.
  • Fix-to-layer matching — never prescribe a Pear restart for a cloud-side bug, or a cloud deploy for a mount-topology bug.

Layout

personas/
  slack-relayfile-doctor.json   # persona spec (id, skills, harness, model, memory)
  slack-relayfile-doctor.md     # claudeMd playbook (source of truth for the knowledge)
index.js / index.d.ts           # compatibility export of the persona JSON

Trajectory memory is enabled via the persona's opt-in memory.trajectories facet; curated diagnostic trajectories live under the workspace .trajectories/ corpus so the persona can retrieve past decision arcs (the "why").

Install

agentworkforce install @agentworkforce/persona-slack-relayfile-doctor