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

@movecall/claw-esp-expert

v0.0.4

Published

ESP-IDF expert skill for OpenClaw with workspace-first installation and hardware-aware build tooling.

Readme

🦞 Claw-ESP-Expert

The definitive AI Agent Skill for ESP-IDF Developers.
懂硬件、懂网络、懂工程的专业级 ESP32 开发助理。

License: MIT Platform: OpenClaw Framework: ESP-IDF

Claw-ESP-Expert is a diagnostic-first skill for ESP32 + ESP-IDF workflows. It focuses on the highest-value pain points in embedded development: component lookup, pin safety, build failures, partition overflow, and panic decoding.

Install

npx @movecall/claw-esp-expert

Default behavior:

  • installs to ~/.openclaw/workspace/skills/claw-esp-expert
  • copies a self-contained skill/ bundle
  • does not silently edit SOUL.md
  • does not silently modify project files or system permissions

MVP highlights

  • Component guidance: query the official ESP Component Registry and generate idf_component.yml suggestions
  • Hardware-aware safety: audit risky GPIO assignments across multiple ESP32 chip families
  • Build diagnostics: classify common ESP-IDF build failures such as missing headers, component issues, partition overflow, and memory overflow
  • Runtime debugging: analyze monitor logs, decode panic backtraces with addr2line, and support a minimal flash + monitor loop

Current scope

Primary tools:

  • safe_build
  • resolve_component
  • analyze_partitions
  • decode_panic / analyze_monitor

Supporting tools:

  • manage_env
  • explore_demo
  • flash_and_monitor
  • execute_project

Supported chip families:

  • esp32
  • esp32s3
  • esp32c3
  • esp32c5
  • esp32c6
  • esp32h2
  • esp32p4

Common SKU names are normalized to family rules, for example:

  • ESP32-S3-PICO-1-N8R2 -> esp32s3
  • ESP32-C6FH4 -> esp32c6
  • ESP32-P4NRW32X -> esp32p4

Local development

git clone https://github.com/movecall/claw-esp-expert.git
cd claw-esp-expert
npm install
npm run build
npm test

Repo layout

claw-esp-expert/
├── bin/          # npx installer
├── skill/        # publishable skill bundle
├── src/          # runtime source
├── scripts/      # build helpers
├── tests/        # smoke tests
├── package.json
└── README.md

Notes

  • This is a usable MVP, not a full automation platform
  • It returns suggestions, diagnostics, and patch-style drafts before attempting deeper automation
  • HIL automation and full self-healing workflows are intentionally out of scope for the first release