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

@ear3/claude-plugin

v0.1.2

Published

Ear3 plugin for Claude Code — agent skills plus the bundled Ear3 MCP server to create, deploy, edit, and analyze AI voice interviews.

Readme

@ear3/claude-plugin

Claude Code plugin for Ear3 — agent skills plus the bundled @ear3/mcp server. The skills are the procedures (when to ask, what to report); the MCP server is the execution layer (typed ear3_* tools, auth kept out of the conversation). One install wires up both.

Install

/plugin marketplace add https://www.ear3.ai/claude/marketplace.json
/plugin install ear3@ear3

Skills are namespaced by the plugin — e.g. /ear3:create-interview ("create an interview about…"). Claude also invokes them on its own when a task matches a skill's description.

The marketplace catalog (hosted at https://www.ear3.ai/claude/marketplace.json and mirrored in this repo's .claude-plugin/marketplace.json) installs the plugin from npm — this package. Claude Code cannot install plugins via npm install directly; registering the marketplace is what makes the npm package reachable.

Skills

  • create-interview — from a plain-language topic to a deployed, shareable voice interview URL.
  • edit-interview — change, translate, reorder, or regenerate an existing interview's questions, persona, and branching.
  • integrate-interview — wire an interview into the user's app with the right SDK layer (@ear3/voice-interviewer widget by default, headless for custom UI, hosted URL for non-React sites).
  • analyze-interview — responses + AI insights turned into a grounded findings report (participation, themes, verbatim quotes).

Skills are procedures, not API references: they prefer the bundled MCP tools, fall back to the CLI, and defer to the AGENTS.md / llms.txt of the exact package version in use, so they stay correct across versions.

Bundled MCP server

.mcp.json starts @ear3/mcp (stdio, via npx) whenever the plugin is enabled. Authentication is resolved inside the server — a one-time npx @ear3/voice-config-cli login, or EAR3_CONFIG_CLI_KEY in the environment; the secret key never appears in the conversation. Without auth the tools still connect and return instructions on how to log in.

Versioning

This package is versioned with the rest of the ear3-sdk workspace via changesets. .claude-plugin/plugin.json mirrors package.json#version (npm run sync-version before publishing).