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

clawkit-doctor

v3.0.0

Published

Guided OpenClaw diagnostic CLI with issue-first recovery flow

Downloads

587

Readme

ClawKit Doctor

Fast diagnostics and safe auto-repair for OpenClaw environments.

Maintainer: @branzoom

Usage

npx clawkit-doctor@latest

When run without arguments in an interactive terminal, Doctor now shows:

  1. language selector (en/zh/ja)
  2. welcome menu (quick diagnose / paste error / tutorial / exit)
  3. guided recovery loop (y/n solved confirmation)

Common modes

# Diagnose only
npx clawkit-doctor@latest

# Diagnose + safe auto-repair
npx clawkit-doctor@latest --fix

# Paste an error for instant recognition + fix steps
npx clawkit-doctor@latest --paste "Telegram getUpdates conflict 409"

# Continue to full environment checks after paste diagnosis
npx clawkit-doctor@latest --paste "token mismatch" --full

# Language selection
npx clawkit-doctor@latest --lang zh

# Skip 0/1 follow-up prompts
npx clawkit-doctor@latest --no-interactive

# Machine-readable output
npx clawkit-doctor@latest --json

Flags

  • --fix: auto-repair supported issues (missing config dir, stale locks, token alignment, permissions)
  • --paste "<error text>": detect known issues from pasted logs/errors and show steps
  • --full: with --paste, continue into full environment checks
  • --lang en|zh|ja: switch UI language
  • --no-interactive: disable the y/n resolution follow-up
  • --json: print full report JSON for CI/automation
  • --quiet: reduce console output
  • --no-report: skip shareable report URL
  • --help, --version

What it checks

  1. Node.js version (v22+ required)
  2. Git availability
  3. Docker availability
  4. OpenClaw config directory (~/.openclaw)
  5. Config file syntax (openclaw.json)
  6. Directory write permissions
  7. Gateway token alignment (auth, remote, env override)
  8. Stale lock files under ~/.openclaw/sessions
  9. Port 18789 (gateway)
  10. Port 3000 (agent)
  11. Port 18800 (browser CDP)

Resolution loop (best-practice UX)

When --paste is used in an interactive terminal, Doctor asks:

  1. y/n whether the issue is solved (also accepts 1/0 for compatibility)
  2. If not solved, reason selection (command, permission, timeout/network, not sure)
  3. Provides fallback steps and asks y/n again
  4. Only after repeated failure, shows escalation links (issue details, troubleshooting index, contact)

This avoids hard-sell behavior and keeps flow focused on incident recovery.

Built-in links (contextual)

Doctor links users naturally based on state:

  • Matched issue details page (/docs/troubleshooting/...)
  • Troubleshooting index: https://getclawkit.com/docs/troubleshooting
  • Prevention guide (post-resolution): https://getclawkit.com/docs/guides/stable-ops

Maintainer publish

cd packages/clawkit-doctor
npm publish --access public